From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 160 available for testing
Date: Thu, 23 Sep 2021 14:44:13 +0200 [thread overview]
Message-ID: <0fcd80aa-926b-86ca-2871-9682699269e6@ipfire.org> (raw)
In-Reply-To: <163221510611.9091.14082336801876174058.ipfire@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
Hi All,
This morning upgraded a vm on my testbed to Core Update 160 and it has been running since then without any issues.
The upgrade occurred with no problems. After the reboot everything was running as before.
I have checked all menu items and as far as I can tell everything is working fine with no hiccups.
I will leave it running for some time to see if anything changes.
Regards,
Adolf
On 21/09/2021 11:05, IPFire Project wrote:
> IPFire Logo
>
> there is a new post from Arne.F on the IPFire Blog:
>
> *IPFire 2.27 - Core Update 160 available for testing*
>
> This is the announcement for IPFire 2.27 - Core Update 160 which is available for testing. It comes with a large number of bug fixes and package updates and prepare for removing Python 2 which has reached its end of life.
>
> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-160-available-for-testing>
>
> The IPFire Project
> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>
next parent reply other threads:[~2021-09-23 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <163221510611.9091.14082336801876174058.ipfire@ipfire.org>
2021-09-23 12:44 ` Adolf Belka [this message]
2021-09-25 8:32 ` Core Update 160 (testing) report Peter Müller
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=0fcd80aa-926b-86ca-2871-9682699269e6@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