From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Feedback on Core Update 157 testing
Date: Fri, 21 May 2021 14:08:47 +0100
Message-ID: <61B571E8-C905-48D4-9C11-A35E4391B800@ipfire.org>
In-Reply-To: <d41430f7209add42ecb934ae4b79373c3f535ef7.camel@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0099053224077131593=="
List-Id: <development.lists.ipfire.org>

--===============0099053224077131593==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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 th=
em?

> On 21 May 2021, at 13:14, ummeegge <ummeegge(a)ipfire.org> wrote:
>=20
> 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/x8=
6_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?

-Michael

>=20
> Some informations from here.
>=20
> Best,
>=20
> Erik
>=20


--===============0099053224077131593==--