On Thu, Jul 12, 2018 at 01:04:38PM +0200, Pjotr Prins wrote:
> On Thu, Jul 12, 2018 at 02:35:13AM -0700, Chris Marusich wrote:
> > l...@gnu.org (Ludovic Courtès) writes:
> > 
> > > I have just pushed a new ‘guix pull’.
> > >
> > > Feedback welcome!
> > 
> > The biggest hiccup for me was that I didn't realize at first that I had
> > to run "guix pull" twice to upgrade from the old style "guix pull".
> > Anyway, after I finally did it, things have been working well.
> Yes. The other thing is that guix pull did not update my profile. So,
> I had to figure out which guix was installed in the store! One has to
> capture the git commit when running guix pull and look for that in the
> store path, e.g.
>   ecba50bb79a49b317c4b1e718f4732b36438227f
> mapped to 
>   /gnu/store/a5cixasz02ynhppna33zxymxahp3vl13-guix-ecba50bb7/bin/guix
> Next restart the daemon with the new path and all should be well.

Another weirdness wash when using above guix daemon and client:

  /gnu/store/a5cixasz02ynhppna33zxymxahp3vl13-guix-ecba50bb7/bin/guix pull
 line 8: /root/.config/current/bin/guix: No such file or directory
  guix pull: error: build failed: unexpected EOF reading a line

now where did that come from ;). This got not cleaned up by Ricardo's suggestion

  guix gc --verify=repair,contents

and it was probably caused by some manual copy of the binary tar installation - 
you know I try things, it is evil.

  ln -s /gnu/store/a5cixasz02ynhppna33zxymxahp3vl13-guix-ecba50bb7/  

got it going again. For posterity.


Reply via email to