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: The Upcoming Core Update(s)
Date: Tue, 21 Nov 2023 21:50:14 +0100	[thread overview]
Message-ID: <14f9200b-e15a-4b9a-8864-6bc0259f216f@ipfire.org> (raw)
In-Reply-To: <76bf3e38-f21e-4ff7-86a0-0801b0067bca@ipfire.org>

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

Hi Peter,

On 21/11/2023 21:39, Peter Müller wrote:
> Hello *,
>
> being in charge of mastering Core Update 182, I've just created the new update,
> and added most of the pending patches from Patchwork. The latter is not quite
> complete yet; I strive to be up to speed by the end of this week.
>
> As far as package updates are concerned, I'd like to update the following ones,
> unless someone else is already working on them:
>
> - OpenSSH
> - strongSwan
I have already built the updated version of strongswan and will submit 
the patch later this evening.

Regards,

Adolf
> - Tor
>
> In C182, we have a linux-firmware update, which already takes quite some breathing
> room in terms of file size. Unless something urgent comes up, it might be sensible
> to close this update sooner rather than later, so it can go into testing once
> Core Update 181 is released.
>
> Thoughts/comments?
>
> Thanks, and best regards,
> Peter Müller
>
>> Michael,
>>
>> I am back from my holiday trip visiting my family and friends in the UK.
>>
>> I will be working again on the OpenVPN package but that won't be ready for CU182.
>>
>> I am currently working through about 20 package updates which should get submitted over the next couple of days.
>>
>> I have some minor bug fixes that may get submitted in time for CU182.
>>
>> Overall, for CU182, there is nothing critical that I am working on beyond normal package updates, so you can decide form the patches I submit what to use and what to leave for a following CU.
>>
>>
>> Regards,
>>
>> Adolf.
>>
>>
>> On 07/11/2023 19:22, Peter Müller wrote:
>>> Hello Michael,
>>> hello *,
>>>
>>>> Hello everyone,
>>>>
>>>> Since this month’s video conference has been canceled, here is a couple of updates from my side:
>>>>
>>>> * Core Update 181 has been branched yesterday. I have this running in my office for a little while and it seems to be a solid update. It also has a lot of security fixes, so please give it a good test that we can hopefully release this in two weeks.
>>> indeed, Core Update 181 seems to work fine without any hiccups whatsoever. :-)
>>>
>>>> * For the following update(s): what do we have in the pipeline? Just to coordinate that we don’t have too much in one update :)
>>> Unless we have more pressing things on our agenda, I remember Adolf saying
>>> that there are still a couple of packages, particularly libraries, which he
>>> did not had the resources to work through. At some point, it might be sensible
>>> to have something like a distributed mini-hackathon to ensure that everything
>>> we include is at least roughly up to date, and if it's just by slicing the
>>> package list and distribute the shares. :-)
>>>
>>> At some point, I had the idea to keep an eye on various security advisories
>>> published by other distributions to identify non-prolific packages with
>>> important updates that might otherwise have flown under our radar, but this
>>> approach never worked well...
>>>
>>> Aside from updating, I recall Stefan working on porting firewall groups to
>>> ipset a while ago. Perhaps this is something we can then focus on to push
>>> out of the door next?
>>>
>>> Just my two cents. I currently do not have anything major on my docket list
>>> for IPFire 2.x. :-)
>>>
>>> All the best,
>>> Peter Müller

-- 
Sent from my laptop


  reply	other threads:[~2023-11-21 20:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05 13:15 Michael Tremer
2023-11-07 18:22 ` Peter Müller
2023-11-07 21:10   ` Adolf Belka
2023-11-21 20:39     ` Peter Müller
2023-11-21 20:50       ` Adolf Belka [this message]
2023-11-23  8:22 ` Arne Fitzenreiter
2023-11-23 15:45   ` Michael Tremer
2023-11-24 13:31     ` Peter Müller
2024-01-16 15:10       ` 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=14f9200b-e15a-4b9a-8864-6bc0259f216f@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