unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Aiko Kyle <aikokyle@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 52908@debbugs.gnu.org
Subject: bug#52908: 'tests/guix-system.sh' fails on aarch64-linux
Date: Wed, 5 Jan 2022 10:34:11 -0700	[thread overview]
Message-ID: <CAPWcbYEnvU=104vcba+-2o6yxpZVg8Q28u41YOyC3ko584zrFQ@mail.gmail.com> (raw)
In-Reply-To: <878rvua4h8.fsf_-_@gmail.com>

On Wed, Jan 5, 2022 at 2:58 AM Chris Marusich <cmmarusich@gmail.com> wrote:
>
>
> > It would be great to get this upstreamed soon so I can start guix
> > pulling master. I think the guix commit and revision in
> > package-management.scm will also need to be bumped after applying this
> > fix.
>
> It shouldn't be necessary to update the guix commit and revision in
> package-management.scm.  My understanding is that "guix pull" will
> install Guix at the specified commit; it does not use the guix package
> to decide which version to install.  In other words, even if at the
> specified commit the "guix" package is defined to use an older version
> (I believe this is always the case, actually), it will not stop "guix
> pull" from installing Guix at the specified commit.
>
> If it's necessary to update the "guix" package, we can certainly do it.
> However, I don't recall that it's necessary for fixing "guix pull"
> problems like this.  If you still believe it's necessary, can you help
> me to understand why it's necessary?
>

I actually encountered this issue not doing a "guix pull" but in doing
a "guix system reconfigure" after a guix pull. I don't really
understand why, but I think guix system reconfigure will continue to
fail until the "guix" package is updated. I may be totally incorrect
here though as I'm still new to this.




  parent reply	other threads:[~2022-01-05 17:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 23:52 bug#52908: 'tests/guix-system.sh' fails on aarch64-linux Leo Famulari
2022-01-04  2:15 ` Chris Marusich
2022-01-04  3:43   ` Aiko Kyle
2022-01-04  4:53     ` Chris Marusich
2022-01-04  5:08       ` Aiko Kyle
2022-01-05  9:58         ` Chris Marusich
2022-01-05 10:47           ` Pierre Langlois
2022-01-06  7:28             ` Chris Marusich
2022-01-05 17:34           ` Aiko Kyle [this message]
2022-01-04 17:28     ` Leo Famulari
2022-01-06 16:39   ` Ludovic Courtès
2022-01-07  4:32     ` Chris Marusich
2022-01-07 10:48       ` Maxime Devos
2022-01-09  4:42         ` Chris Marusich
2022-01-08  1:26       ` Aiko Kyle
2022-01-08  2:18         ` 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='CAPWcbYEnvU=104vcba+-2o6yxpZVg8Q28u41YOyC3ko584zrFQ@mail.gmail.com' \
    --to=aikokyle@gmail.com \
    --cc=52908@debbugs.gnu.org \
    --cc=cmmarusich@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).