From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 162 is available for testing
Date: Sun, 05 Dec 2021 13:26:29 +0100 [thread overview]
Message-ID: <1a941da1-a8b1-fb09-629e-322e248d0321@ipfire.org> (raw)
In-Reply-To: <163862430688.2620980.4991217917932970828.ipfire@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
Hi All,
I have updated to 162 testing in my vm testbed system.
The update went without any hitches. After the update and reboot everything that was operating beforehand was running afterwards.
I tested out my OpenVPN mobile client connection and that worked without problems, so no issues with the update to openvpn-2.5.4
I will continue reviewing the operation but first impression is that everything went very smoothly.
Regards,
Adolf.
On 04/12/2021 14:25, IPFire Project wrote:
> IPFire Logo
>
> there is a new post from Arne.F on the IPFire Blog:
>
> *IPFire 2.27 - Core Update 162 is available for testing*
>
> Another release is available for testing: IPFire 2.27 - Core Update 162. It comes with a brand-new kernel based on Linux 5.15, and it will be the last release supporting the i586 architecture.
>
> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-162-is-available-for-testing>
>
> The IPFire Project
> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>
parent reply other threads:[~2021-12-05 12:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <163862430688.2620980.4991217917932970828.ipfire@ipfire.org>]
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=1a941da1-a8b1-fb09-629e-322e248d0321@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