unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Aiko Kyle <aikokyle@gmail.com>, Leo Famulari <leo@famulari.name>
Cc: 52908@debbugs.gnu.org
Subject: bug#52908: 'tests/guix-system.sh' fails on aarch64-linux
Date: Wed, 05 Jan 2022 01:58:43 -0800	[thread overview]
Message-ID: <878rvua4h8.fsf_-_@gmail.com> (raw)
In-Reply-To: <CAPWcbYHPT2Z+FBqcJmKm+E6TRZdRQx=RK2QzqkNQzRZbuf0HOg@mail.gmail.com> (Aiko Kyle's message of "Mon, 3 Jan 2022 22:08:55 -0700, Tue, 4 Jan 2022 12:28:45 -0500")

[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]

Hi Aiko and Leo,

Aiko Kyle <aikokyle@gmail.com> writes:

> 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?

Leo Famulari <leo@famulari.name> writes:

> On Mon, Jan 03, 2022 at 08:43:27PM -0700, Aiko Kyle wrote:
>> I'll defer to you and Leo for that judgment!
>
> I defer to you and Chris! And I agree, let's push the fix ASAP :)

OK.  I want to give people time to comment on the patch, but I also want
to help fix "guix pull" on master sooner rather than later.  I will
commit my patch in about 48 hours to the master branch if nobody has any
further feedback.

I don't think my patch will trigger many rebuilds.  To verify this, I
tried building coreutils on powerpc64le-linux before and after applying
my patch.  It did not trigger a rebuild of coreutils, so I don't think
it will trigger many rebuilds.  It's conceivable that some derivation
that uses the (gnu services xorg) or (gnu services sddm) modules might
change (maybe something related to Guix System?), but I don't know of an
easy way to check that.

-- 
Chris

PGP: https://savannah.gnu.org/people/viewgpg.php?user_id=106836

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2022-01-05 10:01 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 [this message]
2022-01-05 10:47           ` Pierre Langlois
2022-01-06  7:28             ` Chris Marusich
2022-01-05 17:34           ` Aiko Kyle
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=878rvua4h8.fsf_-_@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=52908@debbugs.gnu.org \
    --cc=aikokyle@gmail.com \
    --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.
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).