Pakfire reports errors during 'tmux 3.3' upgrade - but why?

Pakfire reports errors during 'tmux 3.3' upgrade - but why?

[Matthias Fischer]

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

Hi,

Pakfire likes to have a problem. ;-)

...not worried - just being curious...:

Today I stumbled upon a 'tmux' update. Pakfire reported that
'tmux-3.3-10.ipfire' was available.

CGI looked normal, installation went through.

But Pakfire didn't close, reporting: 'Pakfire has finished! Errors
occurred, please check the log output before proceeding.'

I looked through the log, but can't find anything critical (screen log
is attached).

What triggered this message!? 'tmux 3.3' was installed, everything seems
fine, but Pakfire complains.

Any hints are welcome.

Best,

Matthias



[-- Attachment #2: pakfire_log.txt --]
[-- Type: text/plain, Size: 2616 bytes --]

Jul 16 09:37:54 ipfire pakfire: PAKFIRE INFO: IPFire Pakfire 2.27-x86_64 started!
Jul 16 09:37:54 ipfire pakfire: CORE INFO: core-list.db is 21373 seconds old. - DEBUG: force
Jul 16 09:37:54 ipfire pakfire: DOWNLOAD STARTED: lists/core-list.db
Jul 16 09:37:54 ipfire pakfire: MIRROR INFO: 29 servers found in list
Jul 16 09:37:54 ipfire pakfire: DOWNLOAD INFO: Host: mirrors.up.pt (HTTPS) - File: pub/ipfire/pakfire2/2.27-x86_64/lists/core-list.db
Jul 16 09:37:55 ipfire pakfire: DOWNLOAD INFO: pub/ipfire/pakfire2/2.27-x86_64/lists/core-list.db has size of 903 bytes
Jul 16 09:37:55 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Jul 16 09:37:55 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Jul 16 09:37:55 ipfire pakfire: DOWNLOAD INFO: Signature of core-list.db is fine.
Jul 16 09:37:55 ipfire pakfire: DOWNLOAD FINISHED: pub/ipfire/pakfire2/2.27-x86_64/lists/core-list.db
Jul 16 09:37:55 ipfire pakfire: CORE ERROR: No new upgrades available. You are on release 169.
Jul 16 09:37:55 ipfire pakfire: CORE INFO: core-list.db is 0 seconds old. - DEBUG: noforce
Jul 16 09:37:55 ipfire pakfire: PAKFIRE RESV: tmux: Resolving dependencies...
Jul 16 09:37:55 ipfire pakfire: PAKFIRE UPGR: We are going to install all packages listed above.
Jul 16 09:37:55 ipfire pakfire: DOWNLOAD STARTED: paks/tmux-3.3-10.ipfire
Jul 16 09:37:55 ipfire pakfire: MIRROR INFO: 29 servers found in list
Jul 16 09:37:55 ipfire pakfire: DOWNLOAD INFO: Host: mirror2.sandyriver.net (HTTPS) - File: pub/ipfire/pakfire2/2.27-x86_64/paks/tmux-3.3-10.ipfire
Jul 16 09:37:56 ipfire pakfire: DOWNLOAD INFO: pub/ipfire/pakfire2/2.27-x86_64/paks/tmux-3.3-10.ipfire has size of 334218 bytes
Jul 16 09:37:57 ipfire pakfire: DOWNLOAD INFO: HTTP-Status-Code: 200 - 200 OK
Jul 16 09:37:57 ipfire pakfire: DOWNLOAD INFO: File received. Start checking signature...
Jul 16 09:37:57 ipfire pakfire: DOWNLOAD INFO: Signature of tmux-3.3-10.ipfire is fine.
Jul 16 09:37:57 ipfire pakfire: DOWNLOAD FINISHED: pub/ipfire/pakfire2/2.27-x86_64/paks/tmux-3.3-10.ipfire
Jul 16 09:37:57 ipfire pakfire: PAKFIRE UPGR: tmux: Decrypting...
Jul 16 09:37:57 ipfire pakfire: CLEANUP: tmp
Jul 16 09:37:57 ipfire pakfire: DECRYPT STARTED: tmux
Jul 16 09:37:57 ipfire pakfire: DECRYPT FINISHED: tmux - Status: 0
Jul 16 09:37:57 ipfire pakfire: PAKFIRE UPGR: tmux: Upgrading files and running post-upgrading scripts...
Jul 16 09:37:57 ipfire pakfire: CLEANUP: tmp
Jul 16 09:37:57 ipfire pakfire: PAKFIRE UPGR: tmux: Finished.
Jul 16 09:37:57 ipfire pakfire: PAKFIRE INFO: Pakfire has finished. Closing.

Re: Pakfire reports errors during 'tmux 3.3' upgrade - but why?

[Leo-Andres Hofmann]

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

Hi Matthias,

the pakfire.cgi simply looks for the keyword "error" in the logs, since 
there is no explicit return code or error flag available.

The message was probably triggered by this line: "Jul 16 09:37:55 ipfire 
pakfire: CORE ERROR: No new upgrades available. You are on release 169."

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:"?

Best regards
Leo

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

Re: Pakfire reports errors during 'tmux 3.3' upgrade - but why?

[Matthias Fischer]

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

On 16.07.2022 10:40, Leo-Andres Hofmann wrote:
> Hi Matthias,

Hi Leo,

> the pakfire.cgi simply looks for the keyword "error" in the logs, since 
> there is no explicit return code or error flag available.

Thanks for looking! It must have been somthing like that, but I didn't
know exactly where to search. ;-)

> The message was probably triggered by this line: "Jul 16 09:37:55 ipfire 
> pakfire: CORE ERROR: No new upgrades available. You are on release 169."

'functions.pl', line 786...

> 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:"?

That's ok with me. Should be an INFO, not an ERROR.

JM2C.

Best,

Matthias

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

Re: Pakfire reports errors during 'tmux 3.3' upgrade - but why?

[Bernhard Bitsch]

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



Am 16.07.2022 um 10:40 schrieb Leo-Andres Hofmann:
> Hi Matthias,
> 
> the pakfire.cgi simply looks for the keyword "error" in the logs, since 
> there is no explicit return code or error flag available.
> 
> The message was probably triggered by this line: "Jul 16 09:37:55 ipfire 
> pakfire: CORE ERROR: No new upgrades available. You are on release 169."
> 
> 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:"?
> 
Ack.
Bernhard
> Best regards
> Leo
> 
> Am 16.07.2022 um 09:56 schrieb Matthias Fischer:
>> Hi,
>>
>> Pakfire likes to have a problem. ;-)
>>
>> ...not worried - just being curious...:
>>
>> Today I stumbled upon a 'tmux' update. Pakfire reported that
>> 'tmux-3.3-10.ipfire' was available.
>>
>> CGI looked normal, installation went through.
>>
>> But Pakfire didn't close, reporting: 'Pakfire has finished! Errors
>> occurred, please check the log output before proceeding.'
>>
>> I looked through the log, but can't find anything critical (screen log
>> is attached).
>>
>> What triggered this message!? 'tmux 3.3' was installed, everything seems
>> fine, but Pakfire complains.
>>
>> Any hints are welcome.
>>
>> Best,
>>
>> Matthias

Re: Pakfire reports errors during 'tmux 3.3' upgrade - but why?

[Robin Roevens]

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


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,
>> 
>> the pakfire.cgi simply looks for the keyword "error" in the logs, since there is no explicit return code or error flag available.
>> 
>> The message was probably triggered by this line: "Jul 16 09:37:55 ipfire pakfire: CORE ERROR: No new upgrades available. You are on release 169."
>> 
>> 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 my sources) I also changed this, I think, to CORE  WARNING as error sounded too severe for that message.
I'll make sure to inherit your change in my submission somewhere at the end of the month.

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

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