all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jookia <166291@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: guix pull is shafted
Date: Sun, 6 Mar 2016 00:46:42 +1100	[thread overview]
Message-ID: <20160305134642.GA31782@novena-choice-citizen.lan> (raw)
In-Reply-To: <20160305122811.GA29898@thebird.nl>

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.

  reply	other threads:[~2016-03-05 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05  9:57 guix pull is shafted Pjotr Prins
2016-03-05 10:03 ` Pjotr Prins
2016-03-05 11:06   ` Andreas Enge
2016-03-05 11:08   ` Ricardo Wurmus
2016-03-05 12:28     ` Pjotr Prins
2016-03-05 13:46       ` Jookia [this message]
2016-03-05 11:01 ` Nils Gillmann
2016-03-06 10:32 ` Pjotr Prins
2016-03-06 14:06   ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160305134642.GA31782@novena-choice-citizen.lan \
    --to=166291@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.