From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: Efraim Flashner <efraim@flashner.co.il>,
Guix-devel <guix-devel@gnu.org>,
guix-maintainers@gnu.org, Julien Lepiller <julien@lepiller.eu>,
Marius Bakke <marius@gnu.org>
Subject: Re: Supported architectures
Date: Thu, 13 Oct 2022 17:06:53 +0200 [thread overview]
Message-ID: <87wn93oj8y.fsf@gnu.org> (raw)
In-Reply-To: <875ygokc7e.fsf@contorta> (Vagrant Cascadian's message of "Wed, 12 Oct 2022 13:40:21 -0700")
Howdy!
Vagrant Cascadian <vagrant@debian.org> skribis:
> FWIW, on Debian guix 1.3.0 is currently at risk due to armhf and
> i386/i686-linux missings builds due to test suite failures. It has been
> hard to keep up with Guix in Debian, especially supporting "obscure"
> platforms...
>
> Though I'm guessing there may be reluctance to drop support for
> i686-linux... I much more frequently encounter test suite failures when
> building it, at least on Debian. It is surely less well supported than
> x86_64-linux.
>
> But dropping armhf and i386 at the moment looks ... helpful from a
> Debian packaging perspective... :/
>
> I'll try to package a git snapshot of guix and see if that fares any
> better and hopefully find and fix issues before the next guix release!
That’d be great!
Please report test failures that you find; we may be seeing them as well
in Guix. :-)
Ludo’.
next prev parent reply other threads:[~2022-10-13 15:07 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 [this message]
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 ` Release progress, week 2 Christopher Baines
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=87wn93oj8y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=julien@lepiller.eu \
--cc=marius@gnu.org \
--cc=vagrant@debian.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).