From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Pakfire reports errors during 'tmux 3.3' upgrade - but why?
Date: Sat, 16 Jul 2022 09:56:46 +0200 [thread overview]
Message-ID: <0f2a2dd1-25ad-900e-88d5-24aed43b5129@ipfire.org> (raw)
[-- 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.
next reply other threads:[~2022-07-16 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 7:56 Matthias Fischer [this message]
2022-07-16 8:40 ` Leo-Andres Hofmann
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=0f2a2dd1-25ad-900e-88d5-24aed43b5129@ipfire.org \
--to=matthias.fischer@ipfire.org \
--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