From mboxrd@z Thu Jan  1 00:00:00 1970
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 151 testing feedback
Date: Fri, 09 Oct 2020 22:56:58 +0200
Message-ID: <4b1646fae3d27fba3fd9b9de8ff11f4399da8b55.camel@ipfire.org>
In-Reply-To: <4B6E1456-49A5-4E9E-9D33-BF0A913FC3FC@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1405674611924119712=="
List-Id: <development.lists.ipfire.org>

--===============1405674611924119712==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Hi all,

Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer:
> Hello,
> 
> Could you please open a ticket on BZ for both of them?
Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 
https://bugzilla.ipfire.org/show_bug.cgi?id=12494

apart from that my Prime has been smoked up with a read-only file
system and is gone into the "Ewige Jagd Gründe" after a reboot but this
might have other reasons but further testings/developments are
currently a little awkward.

Best from shit happens,

Erik


> 
> 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
> > 
> > 
> > 
> 
> 


--===============1405674611924119712==--