unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Release progress, week 2
Date: Sat, 22 Oct 2022 13:18:17 +0100	[thread overview]
Message-ID: <87edv0gi74.fsf@cbaines.net> (raw)
In-Reply-To: <878rlaehbn.fsf_-_@gnu.org>

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


Ludovic Courtès <ludo@gnu.org> writes:

>   • Architectures:
>
>      - armhf-linux is disabled on ci.guix due to improper offloading
>        setup (probably along the lines of
>        <https://issues.guix.gnu.org/53463>).  Should we try and reenable
>        it, or should we drop it?
>
>      - powerpc64le-linux is disabled on ci.guix since today
>        (maintenance.git commit
>        d641115e20973731555b586985fa81fbe293aeca).  However it did work
>        until recently and we have one machine to offload to.  Should we
>        fix it or drop it?  Mathieu?

bordeaux.guix.gnu.org should have good substitute availability for both
of these architectures.

>      - i586-gnu is disabled due to <https://issues.guix.gnu.org/58320>.
>        No fix yet, so I may resort to installing the workdaround so we
>        can try and build things there.   I believe Chris didn’t hit this
>        bug when setting up childhurds on Intel hardware behind
>        bordeaux.guix, so substitutes should be coming there.

I've also got some childhurds running. I think there were some build
coordinator issues that meant some of the agents were getting stuck, but
I think I'm making progress with those now.

In terms of actually building things, I think there are some problems
building grep and coreutils. I've been looking at the hello package [1]
and the build for i586-gnu [2]. You can see the required failed builds
on the build page [2].

1: https://data.guix.gnu.org/repository/1/branch/master/latest-processed-revision/package/hello/2.12.1?locale=en_US.UTF-8
2: https://data.guix.gnu.org/build-server/2/build?build_server_build_id=b4b1ddb6-b2b2-454e-89b9-10d7ff61498c

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

  parent reply	other threads:[~2022-10-22 12:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:50 Planning for a release, for real Ludovic Courtès
2022-10-06 16:02 ` Julien Lepiller
2022-10-07  9:49   ` Ludovic Courtès
2022-10-07 10:14     ` Julien Lepiller
2022-10-06 16:07 ` Maxime Devos
2022-10-07  9:50   ` Ludovic Courtès
2022-10-07  9:53     ` Maxime Devos
2022-10-07  6:20 ` Supported architectures Efraim Flashner
2022-10-07 10:02   ` Ludovic Courtès
2022-10-10  7:57   ` Csepp
2022-10-12 20:40   ` Vagrant Cascadian
2022-10-13 15:06     ` Ludovic Courtès
2022-10-07  8:26 ` Planning for a release, for real Christopher Baines
2022-10-07 10:09   ` Ludovic Courtès
2022-10-10 10:33 ` zimoun
2022-10-13 15:19 ` Release progress, week 1 Ludovic Courtès
2022-10-13 15:33   ` Efraim Flashner
2022-10-13 15:42   ` Christopher Baines
2022-10-20 13:49   ` Release progress, week 2 Ludovic Courtès
2022-10-20 20:07     ` Efraim Flashner
2022-10-21  8:51       ` Rust on aarch64-linux Ludovic Courtès
2022-10-21 13:42         ` Efraim Flashner
2022-10-22 20:22         ` Efraim Flashner
2022-10-26  9:01           ` Efraim Flashner
     [not found]     ` <87h6zyo811.fsf@gnu.org>
2022-10-21  8:43       ` Status of armhf-linux and powerpc64le-linux Ludovic Courtès
2022-10-21  9:30         ` Mathieu Othacehe
2022-10-31 17:40         ` Tobias Platen
2022-10-22 12:18     ` Christopher Baines [this message]
2022-10-25  9:50     ` Release progress, week 2, release manifest, what builds are failing? Christopher Baines
2022-10-25 11:29       ` Release progress, week 2, release manifest, what builds are failing: gst-plugins-bad Christopher Baines

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=87edv0gi74.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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).