From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: Re: Pakfire reports errors during 'tmux 3.3' upgrade - but why?
Date: Sun, 17 Jul 2022 20:31:16 +0200
Message-ID: <E77413FB-00C0-44C5-8334-108BBD05530C@sicho.home>
In-Reply-To: <f97361c7-5892-e180-c32f-18dc0d88763d@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7126349451231635732=="
List-Id: <development.lists.ipfire.org>

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


Bernhard Bitsch <bbitsch(a)ipfire.org> schreef op 16 juli 2022 11:14:05 CEST:
>
>Am 16.07.2022 um 10:40 schrieb Leo-Andres Hofmann:
>> Hi Matthias,
>>=20
>> the pakfire.cgi simply looks for the keyword "error" in the logs, since th=
ere is no explicit return code or error flag available.
>>=20
>> The message was probably triggered by this line: "Jul 16 09:37:55 ipfire p=
akfire: CORE ERROR: No new upgrades available. You are on release 169."
>>=20
>> I think this message should be at "info" or "warning" level at most. Does =
anyone mind if I go ahead and change it to "CORE INFO:"?

If I remember correctly (from my remote vacation location without access to m=
y sources) I also changed this, I think, to CORE  WARNING as error sounded to=
o severe for that message.
I'll make sure to inherit your change in my submission somewhere at the end o=
f the month.

Robin=20
>>=20
>Ack.
>Bernhard
>> Best regards
>> Leo
>>=20
>> Am 16.07.2022 um 09:56 schrieb Matthias Fischer:
>>> Hi,
>>>=20
>>> Pakfire likes to have a problem. ;-)
>>>=20
>>> ...not worried - just being curious...:
>>>=20
>>> Today I stumbled upon a 'tmux' update. Pakfire reported that
>>> 'tmux-3.3-10.ipfire' was available.
>>>=20
>>> CGI looked normal, installation went through.
>>>=20
>>> But Pakfire didn't close, reporting: 'Pakfire has finished! Errors
>>> occurred, please check the log output before proceeding.'
>>>=20
>>> I looked through the log, but can't find anything critical (screen log
>>> is attached).
>>>=20
>>> What triggered this message!? 'tmux 3.3' was installed, everything seems
>>> fine, but Pakfire complains.
>>>=20
>>> Any hints are welcome.
>>>=20
>>> Best,
>>>=20
>>> Matthias
>

--=20
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.


--===============7126349451231635732==--