From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 54934@debbugs.gnu.org
Subject: [bug#54934] [PATCH 0/4] Fix broken packages by PyYAML upgrade.
Date: Thu, 14 Apr 2022 16:00:49 +0200 [thread overview]
Message-ID: <87fsmfvk5n.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ1nLfZRuy3GKaRDnZEY9suKMi4WJ54vA2samxw_zbjWKA@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> On Thu, 14 Apr 2022 at 15:20, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> > Note that the package orange is still broken. Because
>> > python-orange-canvas-core is broken.
>>
>> I don’t understand. It builds just fine here. I tested on commit
>> b0dd06bd0caea46a852248ab48ab2e6aaff57752.
>
> I have not tested on this one since it is very recent ;-)
>
> CommitDate: Thu Apr 14 14:53:17 2022 +0200
>
> but it fails with 7d990e775e76c0a898c7d4b53691d1932fc0e6eb.
>
>
>> How is it broken?
>
> Like this <https://ci.guix.gnu.org/build/644998/details>
I cannot reproduce this. I also ran “guix build
/gnu/store/aj4xvw8shwjq9qpyfbswb71jk7axf26h-python-orange-canvas-core-0.1.24.drv” on ci.guix.gnu.org to
see if I can reproduce the failure there, but it succeeded.
--
Ricardo
next prev parent reply other threads:[~2022-04-14 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 11:08 [bug#54934] [PATCH 0/4] Fix broken packages by PyYAML upgrade zimoun
2022-04-14 11:10 ` [bug#54934] [PATCH 1/4] gnu: python-pyyaml-for-awscli: Rename and hide zimoun
2022-04-14 11:10 ` [bug#54934] [PATCH 2/4] gnu: docker-compose: Use python-pyyaml@5 zimoun
2022-04-14 11:10 ` [bug#54934] [PATCH 3/4] gnu: conan: " zimoun
2022-04-14 11:10 ` [bug#54934] [PATCH 4/4] gnu: ganeti: " zimoun
2022-04-14 13:19 ` [bug#54934] [PATCH 0/4] Fix broken packages by PyYAML upgrade Ricardo Wurmus
2022-04-14 13:28 ` zimoun
2022-04-14 14:00 ` Ricardo Wurmus [this message]
2022-04-14 15:07 ` zimoun
2022-04-27 22:11 ` bug#54934: " Ludovic Courtès
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=87fsmfvk5n.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=54934@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).