public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Leo-Andres Hofmann <hofmann@leo-andres.de>
To: development@lists.ipfire.org
Subject: Re: Pakfire reports errors during 'tmux 3.3' upgrade - but why?
Date: Sat, 16 Jul 2022 10:40:54 +0200	[thread overview]
Message-ID: <496753c0-6b29-a108-8991-7ba6fea81e17@leo-andres.de> (raw)
In-Reply-To: <0f2a2dd1-25ad-900e-88d5-24aed43b5129@ipfire.org>

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

  reply	other threads:[~2022-07-16  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16  7:56 Matthias Fischer
2022-07-16  8:40 ` Leo-Andres Hofmann [this message]
2022-07-16  8:52   ` Matthias Fischer
2022-07-16  9:14   ` Bernhard Bitsch
2022-07-17 18:31     ` Robin Roevens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496753c0-6b29-a108-8991-7ba6fea81e17@leo-andres.de \
    --to=hofmann@leo-andres.de \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox