From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Core-updates after the staging merge
Date: Mon, 17 Apr 2023 14:03:14 -0400 [thread overview]
Message-ID: <87ttxe4c9p.fsf@gmail.com> (raw)
In-Reply-To: <ZD0LXefP6X4TiYYF@jurong> (Andreas Enge's message of "Mon, 17 Apr 2023 11:03:25 +0200")
Hi,
Andreas Enge <andreas@enge.fr> writes:
> Hello,
>
> just a quick update after a night of building on CI.
> Things look generally quite good on x86_64; some things are being rebuilt
> due to the recent wget update, and that should hopefully also sort out
> i686 rather quickly.
>
> Am Sun, Apr 16, 2023 at 01:09:02PM +0200 schrieb Andreas Enge:
>> - python: It is mostly green, but with lots of red, including at least
>> one package that prevents icecat from building. I would call for careful
>> updates and bug fixes to move on; leaf packages can be updated to the
>> latest version, but for important intermediate packages please be
>> careful.
>
> Python probably is the place where work is needed most, the strip in the
> dashboard looks like it has measles. Fixing one package there could bring
> us a long way (or not - we are in plain hand resolution of dependency
> problems there, one update could also hide another one). Sometimes it is
> just a matter of trying an update to see whether a package and its
> dependents build, so even someone who knows nothing about Python, but
> has a web browser pointed at https://pypi.org/, can do some useful work
> (I am speaking from experience).
I think python is starting to look good here, after a few upgrades.
It'll cause a rebuild of at least GTK+, so I'll push it a bit later
today (during the European night).
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-04-17 18:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 11:09 Core-updates after the staging merge Andreas Enge
2023-04-16 11:59 ` [bug#62863] Openldap in core-updates Andreas Enge
2023-04-16 14:00 ` wget on i686 " Andreas Enge
2023-04-16 18:57 ` Andreas Enge
2023-04-17 8:06 ` Andreas Enge
2023-04-17 8:18 ` Core-updates after the staging merge Guillaume Le Vaillant
2023-04-17 8:33 ` Andreas Enge
2023-04-17 9:03 ` Andreas Enge
2023-04-17 9:56 ` Andreas Enge
2023-04-17 12:19 ` Simon Tournier
2023-04-17 12:38 ` Andreas Enge
2023-04-17 12:57 ` Simon Tournier
2023-04-17 14:12 ` Lars-Dominik Braun
2023-04-17 17:47 ` Simon Tournier
2023-04-17 18:07 ` Andreas Enge
2023-04-17 19:01 ` Lars-Dominik Braun
2023-04-18 17:16 ` Andreas Enge
2023-04-21 18:29 ` Lars-Dominik Braun
2023-04-17 12:57 ` Andreas Enge
2023-04-17 18:03 ` Maxim Cournoyer [this message]
2023-04-17 18:08 ` Andreas Enge
2023-04-18 5:04 ` John Kehayias
2023-04-18 17:38 ` Andreas Enge
2023-04-19 10:48 ` Latest news on core-updates Andreas Enge
2023-04-19 10:58 ` Christopher Baines
2023-04-19 12:41 ` Andreas Enge
2023-04-21 7:58 ` Andreas Enge
2023-04-21 13:01 ` Maxim Cournoyer
2023-04-20 13:56 ` Christopher Baines
2023-04-20 18:09 ` Andreas Enge
2023-04-21 8:20 ` Simon Tournier
2023-04-21 8:47 ` Andreas Enge
2023-04-21 11:31 ` Simon Tournier
2023-04-21 16:12 ` Katherine Cox-Buday
2023-04-21 16:12 ` Katherine Cox-Buday
2023-04-21 17:04 ` reza.housseini
2023-04-23 7:17 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 5:11 Core-updates after the staging merge John Kehayias
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=87ttxe4c9p.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=andreas@enge.fr \
--cc=guix-devel@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).