OK, once more: I am beginning to understand your idea: you are fixing the guix core channel to a specific commit: "9edb3f66fd807b096b48283debdcddccfea34bad" here, i.e. from Saturday, Aug 28 2021
However when I use this (with my own channel): with or without the channel-with-substitutes-available part (here shorter: without): --8<---------------cut here---------------start------------->8--- (list (channel (name 'guix) (url "https://git.savannah.gnu.org/git/guix.git") ;; (branch "master") ;; commit as of Sat Aug 28 2021 (commit "a8dd285d5a0670abf124a721e6ba94da045b24ba") (introduction (make-channel-introduction "9edb3f66fd807b096b48283debdcddccfea34bad" (openpgp-fingerprint "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA")))) (channel (name 'my-stuff) (url "git://git.a-rx.info/channel") (introduction (make-channel-introduction "2526d032addf793521b9f717d411662db5166288" (openpgp-fingerprint "99BB E77D 73AE 07B9 D4B0 CA2E 3384 11E5 6E09 31B5") )) ) ) --8<---------------cut here---------------end--------------->8--- Then if I pull repeatedly: it always takes around 51s / 52s / 53s: --8<---------------cut here---------------start------------->8--- rx@dell ~/.config/guix$ time guix pull Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Updating channel 'my-stuff' from Git repository at 'git://git.a-rx.info/channel'... Building from these channels: my-stuff git://git.a-rx.info/channel 2526d03 guix https://git.savannah.gnu.org/git/guix.git a8dd285 Computing Guix derivation for 'x86_64-linux'... / nothing to be done real 0m51.820s user 1m7.150s sys 0m0.528s rx@dell ~/.config/guix$ --8<---------------cut here---------------end--------------->8--- --8<---------------cut here---------------start------------->8--- rx@dell ~/.config/guix$ time guix pull Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'... Updating channel 'my-stuff' from Git repository at 'git://git.a-rx.info/channel'... Building from these channels: my-stuff git://git.a-rx.info/channel 2526d03 guix https://git.savannah.gnu.org/git/guix.git a8dd285 Computing Guix derivation for 'x86_64-linux'... / nothing to be done real 0m50.882s user 1m6.199s sys 0m0.486s rx@dell ~/.config/guix$ --8<---------------cut here---------------end--------------->8--- and so on. Maybe it is not the pulling itself that is so expensive, but "Computing the Guix derivation..." (that is part of the pull command as well apparently) ? Is it necessary to always have a complete Guix derivation built, when I just want to update my system with some changes of my own? Summary line: I guess I am beginning to understand your idea, but it practice it does not make a difference, as each pull still takes more then 50sec. Is there anyone else (pulling frequently) annoyed by these 53 sec roughly each time ? -Andreas Andreas Reuleaux <r...@a-rx.info> writes: > Simon, > > well thanks as well, but sorry: > > Neither do I understand this: it still has a guix core channel [?]: > > >> (channel >> (name 'guix) >> (url "https://git.savannah.gnu.org/git/guix.git") >> ;; (branch "master") >> ... > > (which I wanted to avoid - as it takes ~ 53s), nor does it work > for me (there may be issues with the finterprint/commit ids > I don't want to dig any deeper here): > > rx@dell ~/.config/guix$ guix pull > Updating channel 'guix' from Git repository at > 'https://git.savannah.gnu.org/git/guix.git'... > guix pull: error: aborting update of channel 'guix' to commit > a8dd285d5a0670abf124a721e6ba94da045b24ba, which is not a descendant of > 95c29d2746943733cbe8df7013854d45bb0df413 > hint: Use `--allow-downgrades' to force this downgrade. > > rx@dell ~/.config/guix$ guix pull --allow-downgrades > Updating channel 'guix' from Git repository at > 'https://git.savannah.gnu.org/git/guix.git'... > guix pull: warning: rolling back channel 'guix' from > 95c29d2746943733cbe8df7013854d45bb0df413 to > a8dd285d5a0670abf124a721e6ba94da045b24ba > Updating channel 'hacks' from Git repository at > 'http://example.com/hacks.git'... > guix pull: error: Git error: unexpected http status code: 404 > rx@dell ~/.config/guix$ > > > I replying to the list, even thought I have received your mail only > privately. > > Thanks in any case. > -A > > > Simon Streit <li...@netpanic.org> writes: > >> Hi Andreas, >> >> Andreas Reuleaux <r...@a-rx.info> writes: >>> While working on those packages, I often do a >>> >>> guix pull >> >> Hey, do you just want to pull, say, from your own channel, but not Guix' >> default? This is something I just figured out a couple of days ago! >> >> One way, and this is only one possibility, is to modify your >> channels.scm in such a way that you directly pin your channels to the >> commit, or if necessary, a branch, and basically pull whatever you want >> to get your newest fix. >> >> This is how my channels.scm more or less looks like at the moment: >> >> (use-modules (guix ci)) >> (list (channel-with-substitutes-available >> %default-guix-channel >> "https://ci.guix.gnu.org")) >> (list >> (channel >> (name 'guix) >> (url "https://git.savannah.gnu.org/git/guix.git") >> ;; (branch "master") >> (commit "a8dd285d5a0670abf124a721e6ba94da045b24ba") >> (introduction >> (make-channel-introduction >> "9edb3f66fd807b096b48283debdcddccfea34bad" >> (openpgp-fingerprint >> "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA")))) >> (channel >> (name 'hacks) >> (url "http://example.com/hacks.git") >> (branch "master") >> (commit "e3fd7d9e4aa541f63133c4678f316b5239364c34"))) >> >> Be aware, that the downside is that anytime you want to go further, you >> have to comment things out again, or go back to the default definition. >> >> >> Kind regards >> Simon