From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Some packages in need of an update
Date: Wed, 10 Aug 2022 20:27:58 +0000 [thread overview]
Message-ID: <66efb5a9-edf6-1b52-c30b-b2ddae21bf56@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
Hello Adolf,
hello * (to keep anybody else working on package updates in the loop),
for good measure, I just wanted to let you know that ...
(a) Michael is working on a glibc update, which includes binutils, so please do not
worry about these, should they already have appeared on your radar.
(b) if you have time and capacity, curl, elfutils and udev are in need of an update.
As for the latter, its source code can be retrieved from https://github.com/eudev-project/eudev/releases/tag/v3.2.11,
which is more straight-forward than extracting udev from systemd (which is a bit
of a mess).
None of these are pressing though, so there is no rush whatsoever. :-)
Thanks to a plethora of non-IPFire commitments I have in the following weeks, I won't
have time to work on package updates, and would rather focus on fixing some bugs that
have been assigned to me quite a while ago. Feel free to coordinate package updates
with the usual suspects (Matthias?), however.
As always, thanks for all the work, and have a nice rest of the weekend!
All the best,
Peter Müller
P.S.: The only exception to my promise above is probably linux-firmware, but I am not
sure if it will fit into Core Update 171, given that this update comes with a new
toolchain and something larger such as Perl, so there probably won't be sufficient space
left.
next reply other threads:[~2022-08-10 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 20:27 Peter Müller [this message]
2022-08-10 21:14 ` Adolf Belka
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=66efb5a9-edf6-1b52-c30b-b2ddae21bf56@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox