From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 177 is available for testing
Date: Fri, 28 Jul 2023 12:37:35 +0200 [thread overview]
Message-ID: <99fccbdb-15c1-1f28-00eb-154e25adadee@ipfire.org> (raw)
In-Reply-To: <62254023-df8f-bcae-00ae-e2f6dd072876@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]
Hi All,
I have found another bug.
When I did the Core Update 177 Testing update I was surprised to find that I got a failure message that /usr/sbin/rngd failed to find the libssl.so.1.1 file
Surprised as I did not have rng-tools installed as an addon.
After investigating I realised that when rng-tools was moved to an addon the existing rootfile files were not removed from users IPFire systems. So /usr/sbin/rngd and /usr/bin/rngtest still exist on the old systems.
I have raised a bug report for this.
https://bugzilla.ipfire.org/show_bug.cgi?id=13197
Regards,
Adolf
On 27/07/2023 22:13, Adolf Belka wrote:
> Hi All,
> When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.
>
> Bug raised for this.
> https://bugzilla.ipfire.org/show_bug.cgi?id=13195
>
> Regards,
> Adolf.
>
> On 27/07/2023 15:00, IPFire Project wrote:
>> IPFire Logo
>>
>> there is a new post from Michael Tremer on the IPFire Blog:
>>
>> *IPFire 2.27 - Core Update 177 is available for testing*
>>
>> The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
>>
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
>>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>
next prev parent reply other threads:[~2023-07-28 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169046280614.981793.9583920204145617344.ipfire@ipfire.org>
2023-07-27 20:13 ` Adolf Belka
2023-07-28 10:37 ` Adolf Belka [this message]
2023-07-28 10:47 ` Michael Tremer
2023-07-29 10:58 ` Adolf Belka
2023-08-02 9:59 ` Michael Tremer
2023-08-02 11:25 ` Adolf Belka
2023-08-11 12:20 ` 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=99fccbdb-15c1-1f28-00eb-154e25adadee@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