On 2026-02-02, Rutherther wrote: > On February 1, 2026 11:19:01 PM GMT+01:00, Ian Eure <[email protected]> wrote: >>I just hit the following irksome case again. I cherry-picked a PR >>onto master, ran `make', built the package etc. When pushing the >>commit, authentication failed. This usually happens when master has a >>commit from a new contributor, but I haven’t pulled the keyring >>branch. >> >>So I check out the keyring branch and pull it, then switch back to >>master. > > Any reason you are using the local keyring branch for auth and not > origin/keyring? That eliminates the problem completely.
I routinely use "guix pull --url=/home/vagrant/src/guix ..." since it seems silly to have guix pull separately download it's own complete git repository history, when the git repository history is already present locally; the only minor downside I see is having to keep the local keyring branch up to date... which is pretty infrequent and not *that* hard. :) As others have noted, I also utilize git worktrees in various wways to reduce the frequency of having to re-run ./bootstrap && ./configure && make ... I typically have a worktree or two for branches I am essentially just following (e.g. the master branch and/or keyring updates) and another one or two for active development where I am working on package updates or reviewing pull requests and such... live well, vagrant
signature.asc
Description: PGP signature
