Bernhard Bitsch bbitsch@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