From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 40535@debbugs.gnu.org
Subject: bug#40535: [core-updates]: Updating `guix' makes package-transitive-supported-systems test fail
Date: Fri, 10 Apr 2020 14:05:40 +0200 [thread overview]
Message-ID: <87imi7eeaz.fsf@gnu.org> (raw)
Hi,
On current core-updates
d523eb5c9c gnu: python-cython: The i686 python2 workaround is needed for 32-bit ARM too.
updating the guix package like so
make update-guix-package
leads to a test failure of package-transitive-supported-systems
make check TESTS=tests/packages
=>
test-name: package-transitive-supported-systems, implicit inputs
location: /home/janneke/src/guix/core-updates/tests/packages.scm:397
source:
+ (test-equal
+ "package-transitive-supported-systems, implicit inputs"
+ %supported-systems
+ (let ((p (dummy-package
+ "foo"
+ (build-system gnu-build-system)
+ (supported-systems
+ `("does-not-exist" "foobar" ,@%supported-systems)))))
+ (parameterize
+ ((%current-system "armhf-linux"))
+ (package-transitive-supported-systems p))))
expected-value: ("x86_64-linux" "i686-linux" "armhf-linux" "aarch64-linux" "mips64el-linux" "i586-gnu")
actual-value: ("x86_64-linux" "i686-linux")
result: FAIL
Last week, when core-updates was at
1808e64de0 gnu: coreutils: Typo: Use libcap only when supported.
it worked correctly.
This is unfortunate, as wip-hurd-vm (freshly rebased) depends on a guix
update.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next reply other threads:[~2020-04-10 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 12:05 Jan Nieuwenhuizen [this message]
2020-04-10 12:17 ` bug#40535: [core-updates]: Updating `guix' makes package-transitive-supported-systems test fail Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imi7eeaz.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=40535@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.