From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 179 is available for testing
Date: Mon, 21 Aug 2023 11:00:32 +0100 [thread overview]
Message-ID: <D3AD54E0-16EE-4B12-B48D-55A87E0C51DB@ipfire.org> (raw)
In-Reply-To: <2807337d-a74e-4d83-9b2f-8d6f90931361@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]
Oh, sorry. I just merged this into core 180.
I will fix this...
> On 21 Aug 2023, at 10:46, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> Three days ago the OP from the request to update ppp to 2.5.0 had already tried it out from CU179 Testing.
>
> He identified that there was a problem with the location for the run state directory for the pid files.
>
> /usr/var/run/ was being used rather than /var/run so the directories did not exist when trying to run ppp.
>
> I submitted a patch to correct this which needs to be merged into CU179 Testing.
> https://lists.ipfire.org/pipermail/development/2023-August/016337.html
>
> Regards,
> Adolf.
>
>
> On 21/08/2023 10:00, IPFire Project wrote:
>> IPFire Logo
>> there is a new post from Michael Tremer on the IPFire Blog:
>> *IPFire 2.27 - Core Update 179 is available for testing*
>> Just after releasing Core Update 178 which was added into our release cycle to address Intel's and AMD's latest CPU vulnerabilities, we are back on track with our regular schedule. This release features Indirect Branch Tracking for user space, a completely rewritten ExtraHD amongst a large number of package updates and the usual bunch of bug fixes.
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-179-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-08-21 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169260480644.231677.17708723675739620342.ipfire@ipfire.org>
2023-08-21 9:46 ` Adolf Belka
2023-08-21 10:00 ` Michael Tremer [this message]
2023-08-21 15:29 ` Adolf Belka
2023-08-23 14:45 ` Peter Müller
2023-08-23 17:25 ` 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=D3AD54E0-16EE-4B12-B48D-55A87E0C51DB@ipfire.org \
--to=michael.tremer@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