From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Feedback on Core Update 157 testing Date: Fri, 21 May 2021 15:19:33 +0200 Message-ID: In-Reply-To: <61B571E8-C905-48D4-9C11-A35E4391B800@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0213718973177866456==" List-Id: --===============0213718973177866456== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, On 21/05/2021 15:08, Michael Tremer wrote: > Hello, > > I ran into this, too, but I didn=E2=80=99t investigate it. > > Does this only affect updates that ship a new version of OpenSSH or all of = them? > >> On 21 May 2021, at 13:14, ummeegge wrote: >> >> Hi all, >> the update went flawlessly. After the update, SSH doesn=C2=B4t respond, >> needed to restart it via WUI to bring it back to life. >> Has Pmacct been merged for Core 157 so far ? If yes, it does not appear >> in Pakfire. > Pmacct has been merged and has been built: > > https://nightly.ipfire.org/master/2021-05-18%2012:51:59%20+0000-d267131b= /x86_64/packages/pmacct-1.7.6-1.ipfire > > Can you try running =E2=80=9Cpakfire update=E2=80=9D and see if it shows up? After updating and then rebooting as instructed, I found pmacct in the pakfir= e list and it successfully installed, is running and shows up in the addon-se= rvices section. Regards, Adolf. > -Michael > >> Some informations from here. >> >> Best, >> >> Erik >> --===============0213718973177866456==--