From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 151 testing feedback
Date: Fri, 09 Oct 2020 15:26:40 +0100 [thread overview]
Message-ID: <4B6E1456-49A5-4E9E-9D33-BF0A913FC3FC@ipfire.org> (raw)
In-Reply-To: <e6f7144ed6073fb7aeea2c34abfd2c271bfea33e.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
Hello,
Could you please open a ticket on BZ for both of them?
Best,
-Michael
> On 9 Oct 2020, at 12:46, ummeegge <ummeegge(a)ipfire.org> wrote:
>
> Hi all,
> i wanted to report a problem with SSH after updating to core 151
> testing.
>
> SSH runs regular on port 222 after updating SSH runs on port 22 and
> wasn´t reachable via the old settings. After pressing the save button
> in SSH section in the WUI everything worked again.
>
> May someone else have that too ?
>
> Also, /etc/os-release shows
>
> PRETTY_NAME="IPFire 2.25 (x86_64) - core145 Development Build: master/405c7326"
>
> but /var/ipfire/fireinfo/profile shows the correct version
>
> "release": "IPFire 2.25 (x86_64) - core151 Development Build: master/5e4126c3",
>
> but apart from that no further problems so far.
>
> Best,
>
> Erik
>
>
>
next prev parent reply other threads:[~2020-10-09 14:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 11:46 ummeegge
2020-10-09 14:26 ` Michael Tremer [this message]
2020-10-09 20:56 ` ummeegge
2020-10-10 11:52 ` Michael Tremer
2020-10-11 5:27 ` ummeegge
2020-10-11 7:52 ` ummeegge
2020-10-11 8:00 ` Matthias Fischer
2020-10-11 11:57 ` ummeegge
2020-10-11 16:29 ` Matthias Fischer
2020-10-09 19:31 ` Peter Müller
2020-10-11 11:18 ` Adolf Belka
2020-10-11 11:58 ` Adolf Belka
2020-10-11 11:29 Core 151 Testing feedback Adolf Belka
2020-10-12 10:14 ` Michael Tremer
2020-10-12 11:14 ` Adolf Belka
2020-10-12 13:10 ` 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=4B6E1456-49A5-4E9E-9D33-BF0A913FC3FC@ipfire.org \
--to=michael.tremer@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