From: Niall Dooley <dooleyn@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <Help-Guix@gnu.org>
Subject: Re: Unable to upgrade packages
Date: Wed, 24 May 2017 20:05:52 +0100 [thread overview]
Message-ID: <CADS3Lq5mwFnu-iUW1yFxKFuSobpN7oAoBB+yAzC6vX4vZ4_+kQ@mail.gmail.com> (raw)
In-Reply-To: <20170507192709.GC1314@jasmine>
Putting this back on the list as I mistakenly only hit reply in my last mail. I
hope this okay.
On 14 May 2017 at 17:42, Leo Famulari <leo@famulari.name> wrote:
> On Sun, May 14, 2017 at 05:15:03PM +0100, Niall Dooley wrote:
>> Hi Leo,
>>
>> Attached is the output when I try to run 'guix pull'. You'll see there
>> is a 404 response.
>> Thanks for your time.
>
> This substitute still returns 404 (checked with wget), so there are two
> options:
>
> guix pull --fallback (requires a recent Guix)
>
> guix build --fallback /gnu/store/db91i1ahr08b9n7hcjj2mmr4a1648ggz-guix-latest.drv
>
> I picked that derivation file out of your log after "The following
> derivations will be built:".
>
> In either case, you'll build the missing package from source.
>
> I hope that helps!
So as I'm running Guix 20170414.08 I don't believe I have a recent enough
version for option 1. In any case, option 2 is still unsuccessful for
me too though
I didn't record the output on this occasion. I suspect at this point I
did something wrong
in my use of Guix. Is there a way to cleanly remove and re-install
Guix. I don't mind as I
only have a handful of packages installed. I raised this query on a
separate thread as well
so apologies for the noise particularly if this is not best practice
on a mailing list.
Thanks as always for your time.
Niall
next prev parent reply other threads:[~2017-05-24 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 13:16 Unable to upgrade packages Niall Dooley
2017-05-07 19:27 ` Leo Famulari
2017-05-09 21:34 ` Ludovic Courtès
2017-05-24 19:05 ` Niall Dooley [this message]
2017-05-24 21:55 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADS3Lq5mwFnu-iUW1yFxKFuSobpN7oAoBB+yAzC6vX4vZ4_+kQ@mail.gmail.com \
--to=dooleyn@gmail.com \
--cc=Help-Guix@gnu.org \
--cc=leo@famulari.name \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).