public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Feedback on Core Update 157 testing
Date: Fri, 21 May 2021 18:57:27 +0200	[thread overview]
Message-ID: <ca3c68b159ff17fb1d12439e87eda805217763c0.camel@ipfire.org> (raw)
In-Reply-To: <61B571E8-C905-48D4-9C11-A35E4391B800@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]

Hi Michael,

Am Freitag, dem 21.05.2021 um 14:08 +0100 schrieb Michael Tremer:
> Hello,
> 
> I ran into this, too, but I didn’t investigate it.
> 
> Does this only affect updates that ship a new version of OpenSSH or
> all of them?
It appears that sshd_config has been overwritten and SSH operates right
away (before a reboot) via default port 22 even 222 has been
configured. SSH have no entry in backup/includes and as far as i can
see it is also missing in the exclude file, may the configuration
directory has simply been renewed ?

> 
> > On 21 May 2021, at 13:14, ummeegge <ummeegge(a)ipfire.org> wrote:
> > 
> > Hi all,
> > the update went flawlessly. After the update, SSH doesn´t 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 “pakfire update” and see if it shows up?
Thanks, this was my fault :-) .

> 
> -Michael
> 
> > 
> > Some informations from here.
> > 
> > Best,
> > 
> > Erik
> > 
> 



  parent reply	other threads:[~2021-05-21 16:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 12:14 ummeegge
2021-05-21 12:29 ` Tom Rymes
2021-05-21 13:08 ` Michael Tremer
2021-05-21 13:19   ` Adolf Belka
2021-05-21 13:21   ` Peter Müller
2021-05-21 16:57   ` ummeegge [this message]
2021-05-25 11:17     ` Michael Tremer
2021-05-21 13:26 ` Adolf Belka
2021-05-25 10:18   ` Michael Tremer
2021-05-25 11:33     ` Adolf Belka
2021-05-25 11:35       ` Michael Tremer
2021-05-25 11:42         ` Adolf Belka
2021-05-25 11:49           ` Michael Tremer
2021-05-25 20:12             ` Adolf Belka
2021-05-23 16:15 ` Core Update 157 (testing) report Peter Müller
2021-05-25 10:25   ` Michael Tremer

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=ca3c68b159ff17fb1d12439e87eda805217763c0.camel@ipfire.org \
    --to=ummeegge@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