guix pull is shafted

guix pull is shafted

[Pjotr Prins]

Don't do a guix pull right now. There is a recursive grafts problem.

Pj.

Re: guix pull is shafted

[Pjotr Prins]

And then the question, how can we roll back on a pull ;)

On Sat, Mar 05, 2016 at 10:57:54AM +0100, Pjotr Prins wrote:
> Don't do a guix pull right now. There is a recursive grafts problem.
> 
> Pj.
> 

-- 

Re: guix pull is shafted

[Nils Gillmann]

Pjotr Prins <pjotr.public12@thebird.nl> writes:

> Don't do a guix pull right now. There is a recursive grafts problem.
>
> Pj.

Thanks, I think that might explain some problems.
Good to read this right after a guix pull.


-- 
ng
irc://loupsycedyglgamf.onion:67/~NiAsterisk
https://psyced.org:34443/NiAsterisk/
EDN: https://wiki.c3d2.de/Echt_Dezentrales_Netz/en

Re: guix pull is shafted

[Andreas Enge]

On Sat, Mar 05, 2016 at 11:03:07AM +0100, Pjotr Prins wrote:
> And then the question, how can we roll back on a pull ;)

Not automatically, I think, but you can always delete the directory containing
it inside .local and install from git, where you can choose any commit that
works for you.

Andreas

Re: guix pull is shafted

[Ricardo Wurmus]

Pjotr Prins <pjotr.public12@thebird.nl> writes:

> And then the question, how can we roll back on a pull ;)

“guix pull” just updates “~/.config/guix/latest” to point to a recent
version of Guix in the store.  If you have a git checkout (at a commit
before the one that broke things) you could point
“~/.config/guix/latest” to that directory.

I don’t think the needed code is in place for “guix pull” to be undone
in a more user-friendly fashion.

~~ Ricardo

Re: guix pull is shafted

[Pjotr Prins]

Thanks for that! Saved my day. Nice to understand what is happening
too.

On Sat, Mar 05, 2016 at 12:08:38PM +0100, Ricardo Wurmus wrote:
> “guix pull” just updates “~/.config/guix/latest” to point to a recent
> version of Guix in the store.  If you have a git checkout (at a commit
> before the one that broke things) you could point
> “~/.config/guix/latest” to that directory.
> 
> I don’t think the needed code is in place for “guix pull” to be undone
> in a more user-friendly fashion.
> 
> ~~ Ricardo
> 

-- 

Re: guix pull is shafted

[Jookia]

On Sat, Mar 05, 2016 at 01:28:11PM +0100, Pjotr Prins wrote:
> Thanks for that! Saved my day. Nice to understand what is happening
> too.
> 
> On Sat, Mar 05, 2016 at 12:08:38PM +0100, Ricardo Wurmus wrote:
> > “guix pull” just updates “~/.config/guix/latest” to point to a recent
> > version of Guix in the store.  If you have a git checkout (at a commit
> > before the one that broke things) you could point
> > “~/.config/guix/latest” to that directory.
> > 
> > I don’t think the needed code is in place for “guix pull” to be undone
> > in a more user-friendly fashion.
> > 
> > ~~ Ricardo
> > 

Just jumping in to this thread, I've helped two people in IRC run 'guix pull'
with a working git tarball I found. Perhaps some code should be added to pull
the latest build that's been built on Hydra?

In the end it'd still be great to have rollbacks, the ability to specify a git
commit, ping Hydra to see which commits have substitutes that I could upgrade
to, and allow rolling back as if it's a package in my profile.

It sounds like a lot, but I figure at least one of those ideas would ease
things for people.

Jookia.

Re: guix pull is shafted

[Pjotr Prins]

On Sat, Mar 05, 2016 at 10:57:54AM +0100, Pjotr Prins wrote:
> Don't do a guix pull right now. There is a recursive grafts problem.

It is fixed now. Everything hunky dory. Kudos.

Pj.
-- 

Re: guix pull is shafted

[Ludovic Courtès]

Pjotr Prins <pjotr.public12@thebird.nl> skribis:

> On Sat, Mar 05, 2016 at 10:57:54AM +0100, Pjotr Prins wrote:
>> Don't do a guix pull right now. There is a recursive grafts problem.
>
> It is fixed now. Everything hunky dory. Kudos.

Great, thanks for confirming!

This was also discussed in <http://bugs.gnu.org/22914>.

Ludo’.