From: Marius Bakke <mbakke@fastmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>, 40535@debbugs.gnu.org
Subject: bug#40535: [core-updates]: Updating `guix' makes package-transitive-supported-systems test fail
Date: Fri, 10 Apr 2020 14:17:37 +0200 [thread overview]
Message-ID: <87blnzk00u.fsf@devup.no> (raw)
In-Reply-To: <87imi7eeaz.fsf@gnu.org>
merge 40535 40482
thanks
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> 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 a known problem: <https://bugs.gnu.org/40482>. I've merged the
reports. We decided on #guix to ignore it for now, you can try one of
the workarounds described in #40482 in the mean time.
Sorry for the inconvenience!
prev parent reply other threads:[~2020-04-10 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 12:05 bug#40535: [core-updates]: Updating `guix' makes package-transitive-supported-systems test fail Jan Nieuwenhuizen
2020-04-10 12:17 ` Marius Bakke [this message]
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=87blnzk00u.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=40535@debbugs.gnu.org \
--cc=janneke@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.