Re: "guix deploy" is in git master

Hi, Chris + Ludovic! Ludovic Courtès writes: > Christopher Lemmer Webber skribis: > >> You can spawn a bunch of threads, then use Guile's channels to >> synchronize with the main thread. (Not to be confused with Guix's >> channels!) > > I think you mean Fibers channels, right? > > You could

Re: "guix deploy" is in git master

Hey! Christopher Lemmer Webber skribis: > Jakob L. Kreuze writes: > >> Hi Dave, >> >> "Thompson, David" writes: >> >>> Agreed. Also this should be done in parallel eventually because >>> updating 24 machines serially is silly. >> >> Good idea. Do we have a Guix-specific API for parallelism, or

Re: "guix deploy" is in git master

Jakob L. Kreuze writes: > Hi Dave, > > "Thompson, David" writes: > >> Agreed. Also this should be done in parallel eventually because >> updating 24 machines serially is silly. > > Good idea. Do we have a Guix-specific API for parallelism, or should I > look to the Guile manual section on

Re: "guix deploy" is in git master

Hi Dave, "Thompson, David" writes: > Agreed. Also this should be done in parallel eventually because > updating 24 machines serially is silly. Good idea. Do we have a Guix-specific API for parallelism, or should I look to the Guile manual section on Futures? > This does bring up the question

Re: "guix deploy" is in git master

On Mon, Jul 8, 2019 at 3:29 PM Ricardo Wurmus wrote: > > Similarly, it would be great if “guix deploy” would continue deploying > other machines in the list even if one of them couldn’t be deployed due > to an error. I have a list of 24 machines and a few of them fail with > the user-homes error

Re: "guix deploy" is in git master

Jakob L. Kreuze writes: > zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes: > >> Well, we can pick and choose which exceptions we continue on. For >> services not being started, we can probably carry on with the >> deployment. I think, ideally, in the situations where 'guix deploy' >>

Re: "guix deploy" is in git master

zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) writes: > Well, we can pick and choose which exceptions we continue on. For > services not being started, we can probably carry on with the > deployment. I think, ideally, in the situations where 'guix deploy' > should stop, we should try to

Re: "guix deploy" is in git master

Hi Ricardo, Ricardo Wurmus writes: > The remote’s Guix is pretty old, so it’s likely that Ludo is right. > So, I actually reconfigured these machines semi-successfully, eh? > Neat! Yeah! Neat for me, too. I find it mind-blowing that this tool I made is already seeing some use >

Re: "guix deploy" is in git master

Hi Jakob, > Ricardo Wurmus writes: > >> I tried again and it started building things but then aborted like >this: […] >> guix/remote.scm:66:17: In procedure %remote-eval: >> Throw to key `srfi-34' with args `(#> [service: user-homes action: start key: match-error >> args: ("match" "no

Re: "guix deploy" is in git master

Ricardo Wurmus writes: > I tried again and it started building things but then aborted like this: > > … > offloading '/gnu/store/x1q848ra6lm3y0ma9n2i73k8ic1gfyz9-references.drv' to > '141.80.167.145'... > @ build-remote /gnu/store/x1q848ra6lm3y0ma9n2i73k8ic1gfyz9-references.drv >

Re: "guix deploy" is in git master

Mark H Weaver writes: > The problem is that (guix self) has its own logic, independent of the > *.am files, to determine the set of modules to be compiled and > installed. That logic needs to be updated when adding a new module > directory. > > I just pushed commit

Re: "guix deploy" is in git master

Hello, Ricardo Wurmus skribis: > In guix/remote.scm: >122:20 1 (_ _) > 66:17 0 (%remote-eval _ _) > > guix/remote.scm:66:17: In procedure %remote-eval: > Throw to key `srfi-34' with args `(# [service: user-homes action: start key: match-error > args: ("match" "no matching pattern"

Re: "guix deploy" is in git master

Ricardo Wurmus writes: > Hi Mark, > >> Ricardo Wurmus writes: >> >>> Christopher Lemmer Webber writes: >>> Ricardo, can you see if 834b8a4110 fixes the problem? >>> >>> It does not seem to fix this problem. >>> “gnu/machine/ssh.scm” still isn’t included. >> >> The problem is that (guix

Re: "guix deploy" is in git master

Hi Jakob, Ricardo Wurmus writes: >> Now who's going to be the first brave soul to use this for server >> deployment? ;) > > Me! I tried to use it on ci.guix.gnu.org to upgrade a node, but it > failed like this: […] This is now fixed with the inclusion of gnu/machine/ssh.scm. I tried again

Re: "guix deploy" is in git master

Hi Mark, > Ricardo Wurmus writes: > >> Christopher Lemmer Webber writes: >> >>> Ricardo, can you see if 834b8a4110 fixes the problem? >> >> It does not seem to fix this problem. >> “gnu/machine/ssh.scm” still isn’t included. > > The problem is that (guix self) has its own logic, independent

Re: "guix deploy" is in git master

Hi Ricardo, Ricardo Wurmus writes: > Christopher Lemmer Webber writes: > >> Ricardo, can you see if 834b8a4110 fixes the problem? > > It does not seem to fix this problem. > “gnu/machine/ssh.scm” still isn’t included. The problem is that (guix self) has its own logic, independent of the *.am

Re: "guix deploy" is in git master

Ricardo Wurmus writes: > Christopher Lemmer Webber writes: > >> Ricardo, can you see if 834b8a4110 fixes the problem? > > It does not seem to fix this problem. > “gnu/machine/ssh.scm” still isn’t included. Unfortunately my ability to debug autotools problems is... almost nonexistant. Any

Re: "guix deploy" is in git master

Christopher Lemmer Webber writes: > Ricardo, can you see if 834b8a4110 fixes the problem? It does not seem to fix this problem. “gnu/machine/ssh.scm” still isn’t included. -- Ricardo

Re: "guix deploy" is in git master

Ricardo, can you see if 834b8a4110 fixes the problem? Jakob L. Kreuze writes: > Hi, Ricardo! > > Ricardo Wurmus writes: > >> Me! I tried to use it on ci.guix.gnu.org to upgrade a node, but it >> failed like this: >> >> rekado@berlin /root/maintenance/hydra$ guix deploy deploy-berlin-node.scm

Re: "guix deploy" is in git master

Hi, Ricardo! Ricardo Wurmus writes: > Me! I tried to use it on ci.guix.gnu.org to upgrade a node, but it > failed like this: > > rekado@berlin /root/maintenance/hydra$ guix deploy deploy-berlin-node.scm > Backtrace: >8 (primitive-load "/home/rekado/.config/guix/current/bin/��") >

Re: "guix deploy" is in git master

Christopher Lemmer Webber writes: > Huge congratulations to Jakob in that "guix deploy" has just hit git > master! I second this. Thank you Jakob! > Now who's going to be the first brave soul to use this for server > deployment? ;) Me! I tried to use it on ci.g

Re: "guix deploy" is in git master

Christopher Lemmer Webber writes: > Huge congratulations to Jakob in that "guix deploy" has just hit git > master! There's a new section of the manual, "8.15 Invoking ‘guix > deploy’"; see that for details. > > Please play with it and let us know what yo

Re: "guix deploy" is in git master

Christopher Lemmer Webber writes: > Huge congratulations to Jakob in that "guix deploy" has just hit git > master! There's a new section of the manual, "8.15 Invoking ‘guix > deploy’"; see that for details. > > Please play with it and let us know what yo

"guix deploy" is in git master

Huge congratulations to Jakob in that "guix deploy" has just hit git master! There's a new section of the manual, "8.15 Invoking ‘guix deploy’"; see that for details. Please play with it and let us know what your experiences are! MANY THANKS and HUGE CONGRATS to Jakob for ge