From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernhard Bitsch To: development@lists.ipfire.org Subject: Re: Pakfire reports errors during 'tmux 3.3' upgrade - but why? Date: Sat, 16 Jul 2022 11:14:05 +0200 Message-ID: In-Reply-To: <496753c0-6b29-a108-8991-7ba6fea81e17@leo-andres.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0575035729042320038==" List-Id: --===============0575035729042320038== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit 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 --===============0575035729042320038==--