From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.29 - Core Update 191 is available for testing
Date: Fri, 03 Jan 2025 21:42:17 +0100 [thread overview]
Message-ID: <6481f062-85a4-466d-8d5a-117c8bf1cc37@ipfire.org> (raw)
In-Reply-To: <173592151591.863732.14772567575799546562.ipfire@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
Hi All,
I have found that some things didn't get shipped in CU191.
I have looked through all the changes and I believe that the following 5 are the only things (but don't hold me to it). The list of updates was quite large so that a few got missed is not so surprising.
ipblocklists/sources - confirmed in the updated system by checking the sources file
wlanap.cgi - confirmed in the updated system with one of the changes
squid
dhcpcd - confirmed in the updated system by checking version
initscripts/functions - confirmed in the updated system by checking the functions file
Regards,
Adolf.
On 03/01/2025 17:37, IPFire Project wrote:
> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
>
>
>
> IPFire_
>
>
> IPFire 2.29 - Core Update 191 is available for testing
>
> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
>
> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-191-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>
> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>
> Unsubscribe <https://www.ipfire.org/unsubscribe>
>
next parent reply other threads:[~2025-01-03 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <173592151591.863732.14772567575799546562.ipfire@ipfire.org>
2025-01-03 20:42 ` Adolf Belka [this message]
2025-01-07 8:46 ` Arne Fitzenreiter
2025-01-07 11:15 ` Adolf Belka
2025-01-11 15:07 ` 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=6481f062-85a4-466d-8d5a-117c8bf1cc37@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