unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: timflutre@gmail.com, 58526@debbugs.gnu.org
Subject: bug#58526: bug report upgrading Guix from 1.0.1 to 1.3
Date: Sat, 15 Oct 2022 13:44:23 +0200	[thread overview]
Message-ID: <86zgdx9uqw.fsf@gmail.com> (raw)
In-Reply-To: <CAGJVmuJFmaBHpHw7xD7HxnfErOY+0p_x6aUWRFnxQCan5b=6nA@mail.gmail.com>

Hi,

On Fri, 14 Oct 2022 at 20:08, Timothée Flutre <timflutre@gmail.com> wrote:

> I have a computer with Ubuntu 22.04.1 LTS". Some time ago, I installed Guix
> to try it out, which I finally did not for various reasons. But hearing the
> talk of K. Hinsen last month convinced me of giving it another try.

Cool!


> I hence started by upgrading Guix, like this:
> sudo -i guix pull >& output_guix_pull.txt

Well, the guix-daemon is probably too old.  Maybe you need something
like [1]:

   sudo -i guix package --bootstrap -r guix -i \
     /gnu/store/n8vdar2f60mvq62g7mngpqwykbm9rw1q-guix-1.2.0rc2-1.0d4b1af

1: <https://yhetil.org/guix/87wn9dnxsx.fsf@inria.fr>


> The whole report is attached in the file "output_guix_pull.txt".

Missing attachment.


Cheers,
simon




  parent reply	other threads:[~2022-10-15 11:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 18:08 bug#58526: bug report upgrading Guix from 1.0.1 to 1.3 Timothée Flutre
2022-10-14 20:01 ` Maxime Devos
2022-10-15 11:44 ` zimoun [this message]
2022-10-16 15:25   ` Timothée Flutre
2022-10-16 16:26     ` Maxime Devos
     [not found]       ` <handler.s.C.166593762226965.transcript@debbugs.gnu.org>
2022-10-16 16:58         ` bug#58149: " Maxime Devos
2022-10-17 18:25       ` Timothée Flutre
2022-10-17 18:56         ` Maxime Devos
2022-10-17  7:58     ` zimoun
2022-10-17 18:23       ` Timothée Flutre
2022-10-17 19:59         ` zimoun

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=86zgdx9uqw.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=58526@debbugs.gnu.org \
    --cc=timflutre@gmail.com \
    /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 public inbox

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

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).