From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 179 is available for testing Date: Mon, 21 Aug 2023 11:46:03 +0200 Message-ID: <2807337d-a74e-4d83-9b2f-8d6f90931361@ipfire.org> In-Reply-To: <169260480644.231677.17708723675739620342.ipfire@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3180017624213869184==" List-Id: --===============3180017624213869184== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, Three days ago the OP from the request to update ppp to 2.5.0 had already tri= ed it out from CU179 Testing. He identified that there was a problem with the location for the run state di= rectory 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 Testi= ng. https://lists.ipfire.org/pipermail/development/2023-August/016337.html Regards, Adolf. On 21/08/2023 10:00, IPFire Project wrote: > IPFire Logo >=20 > there is a new post from Michael Tremer on the IPFire Blog: >=20 > *IPFire 2.27 - Core Update 179 is available for testing* >=20 > Just after releasing Core Update 178 which was added into our release c= ycle to address Intel's and AMD's latest CPU vulnerabilities, we are back on = track with our regular schedule. This release features Indirect Branch Tracki= ng for user space, a completely rewritten ExtraHD amongst a large number of p= ackage updates and the usual bunch of bug fixes. >=20 > Click Here To Read More >=20 > The IPFire Project > Don't like these emails? Unsubscribe . >=20 --===============3180017624213869184==--