public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 171
Date: Sat, 17 Sep 2022 19:31:51 +0000	[thread overview]
Message-ID: <7e66070f-0c3c-b295-8e1f-c8f21368aca3@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

Hello development folks,

on the given occasion, I'd like to share my thoughts regarding Core Update 171.

Currently, it contains a new toolchain, updated Perl (thanks again, Adolf!), as
well as updated linux-firmware, some bug fixes and package updates. The Core
Update itself currently has 39 MBytes in size.

Unless someone objects, I would like to squeeze a kernel into Core Update 171,
since the one we released in 170 contains a bug rendering apparently popular
ASIX USB3-to-LAN adapters unusable, which affects several users (none of them
tested, of course :-/ ).

Aside from that, there are a few bugs I'd like to see fixed before releasing
Core Update 171, such as repairing the creation of full ISO backups (no Bugzilla
ID assigned yet, AFAIK), as well as me finally fixing #12489.

To release a testing version of C171 more timely, I propose to close the update
in roughly a week, on September 25.

As always, comments/critics/thoughts are appreciated.

Thanks, and best regards,
Peter Müller

             reply	other threads:[~2022-09-17 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 19:31 Peter Müller [this message]
2022-09-17 21:27 ` Adolf Belka
2022-09-17 21:44 ` Paul Simmons
2022-09-18  9:30 ` Michael Tremer

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=7e66070f-0c3c-b295-8e1f-c8f21368aca3@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