From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: IPFire 2.25 core141 build and put into new 2.25 pakfire trees Date: Wed, 05 Feb 2020 10:18:52 +0000 Message-ID: <442AF733-D208-4B8B-9169-B0259D4E3F16@ipfire.org> In-Reply-To: <65a5b7c3ee8d6fd012ac748901b5074d39757090.camel@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7369327130914934880==" List-Id: --===============7369327130914934880== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hello, I just installed the update on the firewall in my office. So far I cannot report any more bugs. Good work guys! When we are pushing this release to 2.23.1? -Michael > On 4 Feb 2020, at 18:15, Stefan Schantl wrote: > > Hello Arne, > > thanks for your hint. I've reinstalled core 141 for the latest changes > on my dad's IPFire with PPPoE dialin and so far everything runs smooth. > > No problems during reboot or any kind of DNS issue. > > Best regards, > > -Stefan >> Hi >> >> i have build IPFire core141 after some late changes and put the >> images >> in my people folder and >> the updates to pakfire 2.25 trees for testing. >> Because the critical dns changes i have not put into the 2.23.1 >> testing >> trees yet. I hope i can do this >> after some feedback. So please help testing. >> >> Make sure your installations are on core139 before change the tree >> from >> 2.23(.1) to 2.25 for updater testing! >> >> Arne >> >> --===============7369327130914934880==--