Great, that answers all my questions thank you very much!
Just need to wait for the package build process to run again (the last
status for 122amd64-default was stoped: crashed:) so that I can test
properly.
On 10/04/2021 1:20 am, Mark Millard via freebsd-ports wrote:
Simon Wright simon.wright
> On Apr 8, 2021, at 11:48 PM, Simon Wright wrote:
> (…)
> My reading seems to say that this is *only* this one commit which is not my
> need. Can anyone confirm this please?
Unlike subversion that has a central repository, git is a distributed VCS which
means that first one has to close, that is
Simon Wright simon.wright at gmx.net wrote on
Fri Apr 9 10:12:04 UTC 2021 :
> Excellent Mark, thank you, then that is exactly what I need, the git
> equivilent of svn up -r xx ${portsdir}.
>
> And is there a need to do git-commit or git-merge to deal with the
> 'detached HEAD' message or can
Excellent Mark, thank you, then that is exactly what I need, the git
equivilent of svn up -r xx ${portsdir}.
And is there a need to do git-commit or git-merge to deal with the
'detached HEAD' message or can I just suppress this? Any local
modifications live in an overlay for poudriere to use
Simon Wright simon.wright at gmx.net wrote on
Fri Apr 9 02:48:47 UTC 2021 :
> I'm still not clear though whether checking out this commit brings in
> all the commits from git clone to this one or only this commit. My
> reading seems to say that this is *only* this one commit which is not my
> need
Thanks for this Dewayne. I have worked out the outlines of how the new
process works, it's the specifics of how it will impact my personal
process that I'm not clear about :).
With Masachika's help I now know how to link the build number as
reported by Poudriere to the git commit. That is trivial
On 4/04/2021 12:30 pm, Simon Wright wrote:
> Hi all,
>
> I've been following the discussion about the git upgrade to the ports
> repro but am not clear about how it impacts my use case.
>
> At the moment I track ports on the revision that the Freebsd build
> cluster uses to build the "latest" pac
Thank you. I had to delete and recreate the repro as non-shallow to get
the commit history but once done then I could find the commit and update
to it.
Follow-up:
I'm still not clear though whether checking out this commit brings in
all the commits from git clone to this one or only this commit.
> [/share/freebsd_ports] # git pull c3c627b06563
> fatal: 'c3c627b06563' does not appear to be a git repository
> fatal: Could not read from remote repository.
First, check the commit.
% git log| grep c3c627b06563
commit c3c627b06563cd0c7bcc4f491cd9c6f50716033b
Then checkout it.
% git checkout c3
Update:
From beefy6.nyi.freebsd.org I can now see the poudriere build status.
This shows the last build as being c3c627b06563 (with status stopped:
crashed:). My issue now is: is it possible to relate this build number
to a specific git revision? Or am I looking in the wrong place? I want
to find
Hi all,
I've been following the discussion about the git upgrade to the ports
repro but am not clear about how it impacts my use case.
At the moment I track ports on the revision that the Freebsd build
cluster uses to build the "latest" package set. I take the currently
reported latest build rev
11 matches
Mail list logo
