(new feature) Change guix pull to choose commits for which substitutes is already built by default

DoneSubmitted by swedebugia.
Details
7 participants
  • Alex Sassmannshausen
  • Nome Grey
  • Jan Nieuwenhuizen
  • Konrad Hinsen
  • Ludovic Courtès
  • Ricardo Wurmus
  • swedebugia
Owner
unassigned
Severity
normal
S
S
swedebugia wrote on 30 Jun 2018 21:06
(new feature) Change guix pull to choose commits for which substitutes is already built by default
(name . Bug-guix@gnu org)(address . Bug-guix@gnu.org)
4ED07131-9A81-456C-9BCE-658EB1C66545@riseup.net
Hi
I would like it to be easy for newcomers to do the right thing when pulling.
I suggest we by default give guix pullers a bit more information and interaction.Something like this:"Checking for newly built derivations of guix at hydra.gnu.org...(table)Date Commit Succeeded for x64?28/6 54d84d8 yes... ... ...
Pulling based on default commit selection scheme (see --help for details) Most recently built commit is x4678x85 built x hours ago. Continuing in 10 seconds...Press ctrl+c to abort. "
Guix pull gets a new argument " -d" allowing you to specify the days old commit you want to select. E. G. Guix pull -d 5 selects a commit build successfully 5 days ago by hydra.
Guix weather could show the table only, if the argument --guix-pull was given. -- Cheers Swedebugia
Attachment: file
L
L
Ludovic Courtès wrote on 2 Jul 2018 15:45
Re: bug#32022: (new feature) Change guix pull to choose commits for which substitutes is already built by default
(name . swedebugia)(address . swedebugia@riseup.net)(address . 32022@debbugs.gnu.org)
877emdhhtq.fsf@gnu.org
Hello swedebugia,
swedebugia <swedebugia@riseup.net> skribis:
Toggle quote (17 lines)> I would like it to be easy for newcomers to do the right thing when pulling.>> I suggest we by default give guix pullers a bit more information and interaction.> Something like this:> "Checking for newly built derivations of guix at hydra.gnu.org...> (table)> Date Commit Succeeded for x64?> 28/6 54d84d8 yes> ... > ... > ... >> Pulling based on default commit selection scheme (see --help for details) > Most recently built commit is x4678x85 built x hours ago. > Continuing in 10 seconds...> Press ctrl+c to abort. "
Any strategy that makes it easy to update to an “old” Guix revision isrisky: one could easily tweak the user into using an old revision thatlacks an important security fix. So that’s not an option to me.
Furthermore, note that people may choose not to use substitutes. Theproposed changes wouldn’t help them.
The problem we’re trying to address here is ‘guix pull’ slowness. Wecan address it in several ways:
1. Provide substitutes in a timely fashion. We do that on berlin.guixsd.org; hydra.gnu.org now provides substitutes, but not in a timely fashion. We should arrange to make them more reactive so that you’re unlikely to have to build things from source, though we can’t entirely eliminate situations where you do have to build part of the stuff from source.
2. Break up the build work that ‘guix pull’ does into reasonably-sized derivations. (guix self) is a step in that direction, but as you know there are still big derivations that have to compile a whole lot of package modules. We could split that further.
3. Make Guile’s compiler faster. I think there’s still room for improvement and that would benefit everyone.
IMO we should really work on these fronts rather than putting users atrisk just to paper over these performance issues.
Thanks,Ludo’.
L
L
Ludovic Courtès wrote on 31 Aug 2018 00:02
Re: bug#22629: “Stable” branch
(name . Alex Sassmannshausen)(address . alex@pompo.co)
878t4nqzqv.fsf@gnu.org
Hi Alex,
(Cc’ing https://bugs.gnu.org/32022 and https://bugs.gnu.org/26608 ,which are related.)
Alex Sassmannshausen <alex@pompo.co> skribis:
Toggle quote (5 lines)> I don't know if this is what Konrad desires, but from my perspective, a> desirable part of the definition of stable would be a that the build> farms have produced a set of binaries/substitutes for a given Guix> revision that is "good enough".
I just had a bright idea (yes!): this can be addressed by writingsomething like this in ~/.config/guix/channels.scm:
(map latest-commit-with-substitutes-available %default-channels)
The hypothetical ‘latest-commit-with-substitutes-available’ would use(git) and (guix ci) to find the latest commit for which substitutes ofinterest are available, and would return:
(channel ;; … (commit "cabbag3")) ;the ideal commit
This has to be done with great care to prevent a downgrade attack and tomake sure the user doesn’t miss out on security updates, but maybe wecould provide a procedure that makes reasonable choices.
Food for thought…
Ludo’.
K
K
Konrad Hinsen wrote on 31 Aug 2018 11:39
m1h8jaq3h0.fsf@fastmail.net
Hi Ludo,
Toggle quote (10 lines)> I just had a bright idea (yes!): this can be addressed by writing> something like this in ~/.config/guix/channels.scm:>> (map latest-commit-with-substitutes-available> %default-channels)>> The hypothetical ‘latest-commit-with-substitutes-available’ would use> (git) and (guix ci) to find the latest commit for which substitutes of> interest are available, and would return:
I really like that idea, but it's a pity to limit it to channels.Two scenarii I'd like to see covered are:
1) Find the latest commit with all substitutes required by a given manifest.
2) Find the latest commit with all substitutes required for updating a given profile.
This is in fact only one problem with two user interfaces.
Konrad.
L
L
Ludovic Courtès wrote on 31 Aug 2018 11:58
(name . Konrad Hinsen)(address . konrad.hinsen@fastmail.net)
874lfarh6w.fsf@gnu.org
Hi Konrad,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
Toggle quote (12 lines)>> I just had a bright idea (yes!): this can be addressed by writing>> something like this in ~/.config/guix/channels.scm:>>>> (map latest-commit-with-substitutes-available>> %default-channels)>>>> The hypothetical ‘latest-commit-with-substitutes-available’ would use>> (git) and (guix ci) to find the latest commit for which substitutes of>> interest are available, and would return:>> I really like that idea, but it's a pity to limit it to channels.
What do you mean by “limit it to channels”? ‘%default-channels’ is analias for the official Guix channel (IOW, Guix itself.)
Toggle quote (10 lines)> Two scenarii I'd like to see covered are:>> 1) Find the latest commit with all substitutes required by a given> manifest.>> 2) Find the latest commit with all substitutes required for updating a> given profile.>> This is in fact only one problem with two user interfaces.
Yes, we could do that, and even maybe more sophisticated things (e.g.,looking at the commit log to determine whether security fixes areavailable, and adjusting the strategy accordingly.)
What I find interesting is that we can provide the tools to support suchpolicies, and then users can choose or implement the policy they wantdirectly in ~/.config/guix/channels.scm.
Ludo’.
K
K
Konrad Hinsen wrote on 31 Aug 2018 12:33
(name . Ludovic Courtès)(address . ludo@gnu.org)
m1k1o6akr4.fsf@fastmail.net
Hi Ludo,
Toggle quote (3 lines)> What do you mean by “limit it to channels”? ‘%default-channels’ is an> alias for the official Guix channel (IOW, Guix itself.)
Fine, but I rarely care about all of Guix, or all of any other channel.I care about the small subset of packages that I actually use.
Better yet, with a per-manifest/profile approach, I could put my mostcritical packages in a special profile and get updates for them morequickly, while still working only with substitutes.
BTW, just out of curiosity: for how many commits in Guix history allpackages could be built successfully? Is that the rule of the exception?
Toggle quote (4 lines)> Yes, we could do that, and even maybe more sophisticated things (e.g.,> looking at the commit log to determine whether security fixes are> available, and adjusting the strategy accordingly.)
Nice!
Toggle quote (4 lines)> What I find interesting is that we can provide the tools to support such> policies, and then users can choose or implement the policy they want> directly in ~/.config/guix/channels.scm.
I agree, it's nice to give people the tools they need to implement theirown policy.
Konrad.
J
J
Jan Nieuwenhuizen wrote on 31 Aug 2018 13:24
(name . Ludovic Courtès)(address . ludo@gnu.org)
87mut2ok2e.fsf@gnu.org
Ludovic Courtès writes:
Toggle quote (6 lines)> I just had a bright idea (yes!): this can be addressed by writing> something like this in ~/.config/guix/channels.scm:>> (map latest-commit-with-substitutes-available> %default-channels)
This is a nice idea and it makes me remember that it would be useful toprovide a way to avoid installing something that is cricitally broken,like Debian's apt-listbugs package/facility(https://packages.debian.org/sid/apt-listbugs).
janneke
-- Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.orgFreelance IT http://JoyofSource.com| Avatar® http://AvatarAcademy.com
R
R
Ricardo Wurmus wrote on 31 Aug 2018 13:45
Re: bug#32022: bug#22629: “Stable” branch
(name . Ludovic Courtès)(address . ludo@gnu.org)
87lg8m2206.fsf@elephly.net
Ludovic Courtès <ludo@gnu.org> writes:
Toggle quote (18 lines)> I just had a bright idea (yes!): this can be addressed by writing> something like this in ~/.config/guix/channels.scm:>> (map latest-commit-with-substitutes-available> %default-channels)>> The hypothetical ‘latest-commit-with-substitutes-available’ would use> (git) and (guix ci) to find the latest commit for which substitutes of> interest are available, and would return:>> (channel> ;; …> (commit "cabbag3")) ;the ideal commit>> This has to be done with great care to prevent a downgrade attack and to> make sure the user doesn’t miss out on security updates, but maybe we> could provide a procedure that makes reasonable choices.
This is a great idea. Any kind of fetch policy could be implementedwith this, including one that considers the contents of a manifest.
This is another of these instances where having a general purposeprogramming language underpinning it all really pays off.
--Ricardo
L
L
Ludovic Courtès wrote on 31 Aug 2018 15:01
Re: bug#22629: “Stable” branch
(name . Konrad Hinsen)(address . konrad.hinsen@fastmail.net)
87k1o6pu4f.fsf@gnu.org
Hello,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
Toggle quote (10 lines)>> What do you mean by “limit it to channels”? ‘%default-channels’ is an>> alias for the official Guix channel (IOW, Guix itself.)>> Fine, but I rarely care about all of Guix, or all of any other channel.> I care about the small subset of packages that I actually use.>> Better yet, with a per-manifest/profile approach, I could put my most> critical packages in a special profile and get updates for them more> quickly, while still working only with substitutes.
Sure! The hypothetical procedure I gave can perform arbitrary checks;it could be passed a manifest.
Toggle quote (3 lines)> BTW, just out of curiosity: for how many commits in Guix history all> packages could be built successfully? Is that the rule of the exception?
We never have 100% of successful builds. Of course we do our best tokeep the failure rate low, but sometimes there are unpopular packagesthat remain broken for some time, or there are packages for which weforgot to exclude some systems via ‘supported-systems’, and of coursethere’s unintended breakage.
Ludo’.
A
A
Alex Sassmannshausen wrote on 3 Sep 2018 16:10
(name . Ludovic Courtès)(address . ludo@gnu.org)
87r2iau0wz.fsf@pompo.co
Hi Ludo,
Ludovic Courtès writes:
Toggle quote (26 lines)> Hi Alex,>> (Cc’ing <https://bugs.gnu.org/32022> and <https://bugs.gnu.org/26608>,> which are related.)>> Alex Sassmannshausen <alex@pompo.co> skribis:>>> I don't know if this is what Konrad desires, but from my perspective, a>> desirable part of the definition of stable would be a that the build>> farms have produced a set of binaries/substitutes for a given Guix>> revision that is "good enough".>> I just had a bright idea (yes!): this can be addressed by writing> something like this in ~/.config/guix/channels.scm:>> (map latest-commit-with-substitutes-available> %default-channels)>> The hypothetical ‘latest-commit-with-substitutes-available’ would use> (git) and (guix ci) to find the latest commit for which substitutes of> interest are available, and would return:>> (channel> ;; …> (commit "cabbag3")) ;the ideal commit
This sounds incredibly interesting — and it is testament once again tothe power of Guix that this kind of solution could be feasible!
Thinking this through in my head somewhat, I had the following thoughts:- This procedure is invoked client side, where the channel is defined- That means the git searching is done client side, on every invocationof guix (I guess this might be cacheable?)- So the downside vis-a-vis a maintained "stable branch" would be aprice in performance as experienced by the end user- The upside of course would be automatic curation of a stable branchthat saves a ton of volunteer effort and work
I have no idea what the performance cost would be. I guess you woulduse "guix weather" to turn the set of requested packages into a manifestwhich can then be checked with it.
So the cost would be one of the following scenarios:Option a)- fetch set of packages in a given commit- query guix weather for 100% substitutes- iterate until a match- then perform the appropriate guix pull
Option b)- perform a guix pull to the latest commit- query guix weather for 100% substitutes- until success, step back one step at a time through guix pull
(because of the cost of guix pull this seems unfeasible)
Option c)Implement some form of substitute cache set querying on build farms, aspart of guix weather, so the 100% match is done on the build farminstead of the client.
Dunno. There may be some things that already exist in Guix land thatI'm missing.
It's a super exciting approach for sure.
Toggle quote (4 lines)> This has to be done with great care to prevent a downgrade attack and to> make sure the user doesn’t miss out on security updates, but maybe we> could provide a procedure that makes reasonable choices.
Right — so at the very least it would have to prevent us going "back intime" from the guix pull commit we are currently at.
The question of security updates is tricky at the moment already — Iwould hazard a guess that many people bail out of upgrading when theycan't get substitutes for their entire profile / system right now, whichmeans they are not getting security upgrades for package (a) when asubstitute for (b) fails.
Thanks for your thoughts — super intriguing!
Alex
L
L
Ludovic Courtès wrote on 3 Sep 2018 21:52
(name . Alex Sassmannshausen)(address . alex@pompo.co)
87zhwywe8v.fsf@gnu.org
Hi Alex,
Alex Sassmannshausen <alex@pompo.co> skribis:
Toggle quote (2 lines)> Ludovic Courtès writes:
[...]
Toggle quote (17 lines)>> I just had a bright idea (yes!): this can be addressed by writing>> something like this in ~/.config/guix/channels.scm:>>>> (map latest-commit-with-substitutes-available>> %default-channels)>>>> The hypothetical ‘latest-commit-with-substitutes-available’ would use>> (git) and (guix ci) to find the latest commit for which substitutes of>> interest are available, and would return:>>>> (channel>> ;; …>> (commit "cabbag3")) ;the ideal commit>> This sounds incredibly interesting — and it is testament once again to> the power of Guix that this kind of solution could be feasible!
Just to be clear: I don’t think this would be a substitute for a“stable” branch; rather, I view as a way to have user-defined policiessuch as “pull up to the latest commit for which there’s a substitute forIceCat.”
Toggle quote (5 lines)> Thinking this through in my head somewhat, I had the following thoughts:> - This procedure is invoked client side, where the channel is defined> - That means the git searching is done client side, on every invocation> of guix (I guess this might be cacheable?)
On every invocation of ‘guix pull’ only.
Toggle quote (4 lines)> I have no idea what the performance cost would be. I guess you would> use "guix weather" to turn the set of requested packages into a manifest> which can then be checked with it.
As I imagine it, the cost would be a few HTTP queries to the CuirassAPI. I should try to come up with an example to better explain what Ihad in mind!
Toggle quote (6 lines)> The question of security updates is tricky at the moment already — I> would hazard a guess that many people bail out of upgrading when they> can't get substitutes for their entire profile / system right now, which> means they are not getting security upgrades for package (a) when a> substitute for (b) fails.
That’s probably true, and I agree it’s problematic.
What I typically do is “guix pull && guix package -n -u”. Then I lookat things that would be built; if, say, LibreOffice is among them, Iwait for a little while and try again later, until I can get enoughsubstitutes. That usually works okay, but it fails if it turns out thatone of the dependencies fails to build: substitutes never becomeavailable in that case.
Ludo’.
L
L
Ludovic Courtès wrote on 3 Sep 2018 22:27
(name . Alex Sassmannshausen)(address . alex@pompo.co)
87h8j6wclu.fsf@gnu.org
Alex Sassmannshausen <alex@pompo.co> skribis:
Toggle quote (2 lines)> Ludovic Courtès writes:
[...]
Toggle quote (14 lines)>> I just had a bright idea (yes!): this can be addressed by writing>> something like this in ~/.config/guix/channels.scm:>>>> (map latest-commit-with-substitutes-available>> %default-channels)>>>> The hypothetical ‘latest-commit-with-substitutes-available’ would use>> (git) and (guix ci) to find the latest commit for which substitutes of>> interest are available, and would return:>>>> (channel>> ;; …>> (commit "cabbag3")) ;the ideal commit
The code below is an illustration of that. If you install it as~/.config/guix/channels.scm, ‘guix pull’ will pull the latest committhat was fully built on berlin.guixsd.org (seehttps://berlin.guixsd.org/jobset/guix-modular-master), meaning thatsubstitutes for Guix itself should be available, unless ‘guix publish’hasn’t “baked” them yet.
It takes two GETs and ~1s to do that here.
Ludo’.
(use-modules (guix http-client) (json) (srfi srfi-1) (ice-9 match)) (define (latest-evaluations jobset) "Return the latest evaluations of JOBSET." (filter (lambda (json) (string=? (hash-ref json "specification") jobset)) (json->scm (http-fetch "https://berlin.guixsd.org/api/evaluations?nr=30")))) (define (evaluation-complete? number) "Return true if evaluation NUMBER completed and all its builds were successful." (let ((builds (json->scm (http-fetch (string-append "https://berlin.guixsd.org/api/latestbuilds?nr=30&evaluation=" (number->string number)))))) (every (lambda (build) ;; Zero means build success. (= (hash-ref build "buildstatus") 0)) builds))) (define (latest-commit-successfully-built) "Return the latest commit for which substitutes are (potentially) available." (let* ((evaluations (latest-evaluations "guix-modular-master")) (candidates (filter-map (lambda (json) (match (hash-ref json "checkouts") ((checkout) (cons (hash-ref json "id") (hash-ref checkout "commit"))) (_ #f))) evaluations))) (any (match-lambda ((evaluation . commit) (and (evaluation-complete? evaluation) commit))) candidates))) ;; Pull the latest commit fully built on berlin.guixsd.org. ;; WARNING: This could downgrade your system! (list (channel (name 'guix) (url "https://git.savannah.gnu.org/git/guix.git") (commit (pk 'commit (latest-commit-successfully-built)))))
A
A
Alex Sassmannshausen wrote on 4 Sep 2018 10:02
(name . Ludovic Courtès)(address . ludo@gnu.org)
87pnxtu1uw.fsf@pompo.co
Ludovic Courtès writes:
Toggle quote (30 lines)> Hi Alex,>> Alex Sassmannshausen <alex@pompo.co> skribis:>>> Ludovic Courtès writes:>> [...]>>>> I just had a bright idea (yes!): this can be addressed by writing>>> something like this in ~/.config/guix/channels.scm:>>>>>> (map latest-commit-with-substitutes-available>>> %default-channels)>>>>>> The hypothetical ‘latest-commit-with-substitutes-available’ would use>>> (git) and (guix ci) to find the latest commit for which substitutes of>>> interest are available, and would return:>>>>>> (channel>>> ;; …>>> (commit "cabbag3")) ;the ideal commit>>>> This sounds incredibly interesting — and it is testament once again to>> the power of Guix that this kind of solution could be feasible!>> Just to be clear: I don’t think this would be a substitute for a> “stable” branch; rather, I view as a way to have user-defined policies> such as “pull up to the latest commit for which there’s a substitute for> IceCat.”
Ah, I understand now.
So the example you provided is a user-defined policy to install thelatest version of Guix that is downloadable using substitutes (if guixpublish has published those already).
As you say, in a similar vein, the end user could for themselves definea policy that searches for a commit containing a specific successfulbuild, or a set of specific successful builds.
Toggle quote (7 lines)>> Thinking this through in my head somewhat, I had the following thoughts:>> - This procedure is invoked client side, where the channel is defined>> - That means the git searching is done client side, on every invocation>> of guix (I guess this might be cacheable?)>> On every invocation of ‘guix pull’ only.
That makes sense, and is way better than I feared :-)
Toggle quote (8 lines)>> I have no idea what the performance cost would be. I guess you would>> use "guix weather" to turn the set of requested packages into a manifest>> which can then be checked with it.>> As I imagine it, the cost would be a few HTTP queries to the Cuirass> API. I should try to come up with an example to better explain what I> had in mind!
Your example helps visualize this, thanks.
Your example depends on there being a jobset that comprises the set ofpackages you are interested in testing.
I imagine it is possible to do the same for an individual package / job.
The situation would be different if the end user wanted to perform asimilar operation for an arbitrary set of packages on their end.
It would probably involve something like this (probably naive):
(define (latest-commit-successfully-built-pkg pkg) "Return the latest commit for the pkg for which substitutes are(potentially) available." ;; Like your version, but magically performs query ;; for pkg, not the guix-modular-master evaluation (let* ((evaluations (latest-evaluations pkg)) (candidates (filter-map (lambda (json) (match (hash-ref json "checkouts") ((checkout) (cons (hash-ref json "id") (hash-ref checkout "commit"))) (_ #f))) evaluations))) (map (match-lambda ((evaluation . commit) (and (evaluation-complete? evaluation) commit))) candidates)))
(any (match-lambda ((evaluation . commit) commit) (apply lset-intersection equal? ;; Like latest-commit-successfully-built, but takes an ;; individual package name for which we return the ;; commit (map latest-commit-successfully-built-pkg %set-of-packages))))
Obviously the larger the set, the more requests are required, and thelower the chance of a commit being available / a downgrade occuring
Toggle quote (15 lines)>> The question of security updates is tricky at the moment already — I>> would hazard a guess that many people bail out of upgrading when they>> can't get substitutes for their entire profile / system right now, which>> means they are not getting security upgrades for package (a) when a>> substitute for (b) fails.>> That’s probably true, and I agree it’s problematic.>> What I typically do is “guix pull && guix package -n -u”. Then I look> at things that would be built; if, say, LibreOffice is among them, I> wait for a little while and try again later, until I can get enough> substitutes. That usually works okay, but it fails if it turns out that> one of the dependencies fails to build: substitutes never become> available in that case.
Interesting. Do you think this kind of thing might be useful to have inthe Guix manual? Like, in a section about a "typical" desktop end-usermight manage their system day to day?
Alex
L
L
Ludovic Courtès wrote on 4 Sep 2018 14:22
(name . Alex Sassmannshausen)(address . alex@pompo.co)
8736upcv04.fsf@gnu.org
Hi Alex,
Alex Sassmannshausen <alex@pompo.co> skribis:
Toggle quote (8 lines)> So the example you provided is a user-defined policy to install the> latest version of Guix that is downloadable using substitutes (if guix> publish has published those already).>> As you say, in a similar vein, the end user could for themselves define> a policy that searches for a commit containing a specific successful> build, or a set of specific successful builds.
Exactly.
Toggle quote (9 lines)>> As I imagine it, the cost would be a few HTTP queries to the Cuirass>> API. I should try to come up with an example to better explain what I>> had in mind!>> Your example helps visualize this, thanks.>> Your example depends on there being a jobset that comprises the set of> packages you are interested in testing.
Yes, and it’s hacky in that the substitute server and jobset names arehard-coded, but you get the idea.
Toggle quote (2 lines)> I imagine it is possible to do the same for an individual package / job.
Yes.
Toggle quote (3 lines)> The situation would be different if the end user wanted to perform a> similar operation for an arbitrary set of packages on their end.
It would be quite similar: you would query the set of builds of anevaluation of the “guix-modular” jobset and check whether the packagesof interest were built.
Toggle quote (11 lines)>> What I typically do is “guix pull && guix package -n -u”. Then I look>> at things that would be built; if, say, LibreOffice is among them, I>> wait for a little while and try again later, until I can get enough>> substitutes. That usually works okay, but it fails if it turns out that>> one of the dependencies fails to build: substitutes never become>> available in that case.>> Interesting. Do you think this kind of thing might be useful to have in> the Guix manual? Like, in a section about a "typical" desktop end-user> might manage their system day to day?
It would make sense to have such a section I guess. However, beforeteaching users how to work around deficiencies of our infrastructure ourprocesses ;-), I’d like us to improve them much as possible. I’m surewe have room for improvement for instance in Cuirass.
Thanks,Ludo’.
S
S
swedebugia wrote on 17 Dec 2018 11:53
bug#32022: (new feature) Change guix pull to choose commits for which substitutes is already built by default
(address . ludo@gnu.org)(address . 32022-done@debbugs.gnu.org)
d947442652dda47c2e275fe18fcb5289@riseup.net
Closed as we now have channels and ludo' had good arguments for why tonot implement my suggestion.
Closed
N
N
Nome Grey wrote on 5 Dec 2019 18:24
(address . control@debbugs.gnu.org)
CANUb+mXAQZvyYvdsABSucb3Z4nxDWjf1bgJfQbiWxs=5sLaSeA@mail.gmail.com
unarchive 32022
Attachment: file
N
N
Nome Grey wrote on 5 Dec 2019 21:30
(address . 32022@debbugs.gnu.org)
CANUb+mUQq25Dt4RncGf=ZkkbPAU0Btj7uJLvevj-31rQzs381w@mail.gmail.com
This bug is linked from a reddit discussion athttps://www.reddit.com/r/GUIX/comments/9un20j/question_about_guix_pullmentioning ludo's solution.
If anybody finds this needing it like I did, I've tried to upgrade his codeto work on a modern guix athttps://github.com/nomr72/guix-substitutes-channel. Changes in guile-jsonstopped the old code from working.
I'm very new to guile, but it's working now.
Once the build infrastructure is developed enough to provide substitutesvery reliably, this will be unneeded.
Attachment: file
L
L
Ludovic Courtès wrote on 10 Dec 2019 17:41
Re: bug#26608: channels.scm supporting substitutes
(name . Nome Grey)(address . greynome72@gmail.com)
87h828nne5.fsf@gnu.org
Hi,
Nome Grey <greynome72@gmail.com> skribis:
Toggle quote (9 lines)> Ludovic posted some channels.scm code in September 2018 supporting using> more substitutes. Unfortunately his code no longer functions due to an> upgrade of guile-json in guix.>> I've tried to learn enough guile to upgrade the code to the newer json> structures, and posted my changes to github at> https://github.com/nomr72/guix-substitutes-channel . It seems to run again> now.
Nice, thanks for sharing!
Ludo’.
?
Your comment

This issue is archived.

To comment on this conversation send email to 32022@debbugs.gnu.org