public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Scheduling of Core Update 173
Date: Mon, 23 Jan 2023 19:08:57 +0100	[thread overview]
Message-ID: <536756d8-4d39-cca9-0e33-d4d1bc0f6c38@ipfire.org> (raw)
In-Reply-To: <7701beb2-5a8f-9d57-76e2-ba4827c62f0a@ipfire.org>

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

Hi Matthias,

On 23/01/2023 18:37, Matthias Fischer wrote:
> Hi,
>
> just to keep you informed...
>
> In progress of being pushed:
> logwatch 7.7 => 7.8 (running here on Core 172, looking good)
>
> Working on:
> cmake 3.21.0 => 3.25.2
> lsof 4.95.0.linux => 4.98
Don't bother with lsof. I did an update in a previous CU but there was a 
bug which meant that the lsof patch had to be reverted.
https://bugzilla.ipfire.org/show_bug.cgi?id=13015
> nano 7.1 => 7.2
I had nano on my list. As you are working on it I will drop it from mine 
and leave it to you.

Regards,
Adolf.
> Should be ready by the end of the week.
>
> Best,
> Matthias
>
> On 23.01.2023 16:36, Peter Müller wrote:
>> Hello development folks,
>>
>> above all, sorry for me being rather absent recently due to the usual bunch
>> of things on my plate, and the day only having 24 hours, which is way too
>> little for me to get all of that done.
>>
>> [Insert a Monthy Python-style "anyway" here...]
>>
>> With regards to Core Update 173, we already have quite something in it, including
>> a brand new kernel (thanks, Arne!), the QMI feature developed by Michael, and
>> a lot of other things that I currently cannot recall, but will once I'm writing
>> the changelog.
>>
>> >From my side, updates for Tor, libloc and the Squid ASNBL helper are still
>> missing, and I will take care of that in due course. Aside from that, I'm working
>> through patchwork, and will get back to the authors of patches I have not merged
>> so far later, if necessary.
>>
>> Closing the Core Update by the end of this week seems sensible to me, so we can
>> give it an extended testing phase, given the plethora of changes in it - in case
>> of QMI, we suspect it will break IPTV, but none of the core developers is able
>> to test that.
>>
>> Please keep the patches coming (many thanks for them, as always), and let me
>> know if there are any questions/concerns/comments.
>>
>> Thanks, and best regards,
>> Peter Müller (back to the batcave :-)
>>

-- 
Sent from my laptop


  reply	other threads:[~2023-01-23 18:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 15:36 Peter Müller
2023-01-23 17:37 ` Matthias Fischer
2023-01-23 18:08   ` Adolf Belka [this message]
2023-01-23 19:48     ` Matthias Fischer
2023-01-26 10:37 ` 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=536756d8-4d39-cca9-0e33-d4d1bc0f6c38@ipfire.org \
    --to=adolf.belka@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