Project

General

Profile

Bug #3166

Errors after pacman -Syuu

maddox - about 2 years ago - . Updated about 2 years ago.

Status:
not-a-bug
Priority:
bug
Category:
-
Assignee:
-
% Done:

0%


Description

downloading required keys...
:: Import PGP key C132293954BBE4AD, "Sergej Pupykin <spupykin@archlinux.org>"? [Y/n] 
(387/387) checking package integrity                         [################################] 100%
error: libp11-kit: signature from "bill-auger <bill-auger@peers.community>" is unknown trust
:: File /var/cache/pacman/pkg/libp11-kit-0.24.0-2.nonsystemd1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: p11-kit: signature from "bill-auger <bill-auger@peers.community>" is unknown trust
:: File /var/cache/pacman/pkg/p11-kit-0.24.0-2.nonsystemd1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: polkit: signature from "bill-auger <bill-auger@peers.community>" is unknown trust
:: File /var/cache/pacman/pkg/polkit-0.118-1.nonsystemd1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: perl: signature from "Levente Polyak (anthraxx) <levente@leventepolyak.net>" is unknown trust
:: File /var/cache/pacman/pkg/perl-5.34.0-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: pinentry: signature from "Levente Polyak (anthraxx) <levente@leventepolyak.net>" is unknown trust
:: File /var/cache/pacman/pkg/pinentry-1.2.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: libsynctex: signature from "bill-auger <bill-auger@peers.community>" is unknown trust
:: File /var/cache/pacman/pkg/libsynctex-2021.59745-1.parabola1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: netpbm: signature from "Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>" is unknown trust
:: File /var/cache/pacman/pkg/netpbm-10.73.36-1.parabola1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: iceweasel: signature from "bill-auger <bill-auger@peers.community>" is unknown trust
:: File /var/cache/pacman/pkg/iceweasel-1:95.0-1.parabola1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: libspeechd: signature from "Alexander Epaneshnikov <email@alex19ep.me>" is unknown trust
:: File /var/cache/pacman/pkg/libspeechd-0.11.1-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: mkinitcpio: signature from "bill-auger <bill-auger@peers.community>" is unknown trust
:: File /var/cache/pacman/pkg/mkinitcpio-30-2.nonsystemd1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: pacman-mirrorlist: signature from "bill-auger <bill-auger@peers.community>" is unknown trust
:: File /var/cache/pacman/pkg/pacman-mirrorlist-20211211-1.parabola1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

History

#1

Updated by bill-auger about 2 years ago

  • Status changed from unconfirmed to not-a-bug
  • Description updated (diff)

the problem there, is that you did not upgrade the keyrings first

... but ...

one should never run `pacman -Syu` on a LiveISO - there is never a need to do that, and LiveISOs are not designed for it

#2

Updated by maddox about 2 years ago

I do not know about LiveISO, but if you mean some DVD room or USB image, that is not what I use, I have installed Parabola long ago and then on various computers, I follow the instructions for upgrade.

When I have followed your instructions for upgrade that is what happened. For you that is not a bug, for me that is bug in the Parabola system, as it should not ever happen.

Or one shall clearly say in the manual that before any pacman -Syu one shall upgrade those keys, and how. However, whatever instructions were followed it did not work, until I have removed one of the packages in question.

Overall the upgrade system did not go well, that is reality. You can keep it in illusion that it is not a bug, but it is a bug. I cannot recommend system to friends as they would not know how to cope with it, how to upgrade it. I hope you get it.

#3

Updated by bill-auger about 2 years ago

i was not dismissing you predicament - you are misunderstanding
the situation - this bug was opened against the "installation
media" bug tracker; which is for issues related to using
parabola LiveISOs (DVD, USB stick, etc) - if this is about a
fully installed system, then the ticket (if valid) should be moved
to the "packages" bug tracker

but still, it is not a bug - those error messages are completely
normal and expected behavior - it can happen for example when
the system has not been upgraded for a long period of time - in
that case, i would actually expect it to happen - because it is
normal behavior, the ticket would have been closed as 'not-a-bug'
on the "packages" bug tracker also

the difference is, that it would have been more clear what the
grievance actually was; and the explanation would have been
different - the explanation given ("do not `pacman -Syu` on a
liveISO") is the best advice, WRT "installation media" - it was
not obvious, that you were referring to an installed parabola,
and not a LiveISO (installation media)

when an installed parabola system gives such signature errors,
usually one needs only to upgrade the keyrings before upgrading
other packages, then those error messages will go away - it is a
simple procedure; of which every parabola user will want to know,
and should try, before opening bug reports (section #6 of the
install guide states this (perhaps not clearly enough?)

it is always safe to upgrade the system; and it is recommended to do so at least once per month.
Before upgrading the system ... when a few months has past between upgrades, ensure that you have the current key-rings first:

# pacman -Sy archlinux-keyring parabola-keyring
# pacman -Syu

note that, i advised the same in my previous reply, although it
was not obviously pertinent at the time - i mentioned it anyways,
just in case, because it a common misconception, to see those
error messages as a bug, rather than a normal feature

FWIW, the pacman program could be "fixed" to hide that behavior
from users (install new keyrings automatically); but in all the
many years pacman has existed, its authors never saw that as a
valuable feature to add (and its absence was never seen as a bug) -
obviously, because they could have long ago, made it to behave
that way (aka: fixed the bug, if it were seen as such)

therefore, despite the confusion and minor nuisance it imposes,
it is normal expected behavior for the pacman program (hence: not-a-bug) -
every parabola user simply needs to learn about this caveat (often
called a "gotcha"); then it is not a problem for anyone

this ticket is a "support request" - it is not a "bug" - i trust that
the distinction has been better explained now:

  • a "bug" is some broken, unintentional, problem with the software, which must be corrected by the dev team
  • a "support request" is a user needing help, to understand or learn how to use parabola - there is nothing for anyone to do about it, other than to explain

if there is no work to be done, then the topic has no place on issue tracker - support requests belong on the mailing lists, IRC, or web forum - those are the reasons why this ticket was closed

#4

Updated by maddox about 2 years ago

I have not applied the advise to bash alias as following:

  1. Parabola upgrade
    alias upgrade-system='sudo pacman -Sy archlinux-keyring parabola-keyring && sudo pacman -Syu'

Regarding "bug" issue, the issue is definitely bugging me, and it is preventing system to be upgraded, so it is general 'pacman' design issue. If you have used other package managers then you should know what I am talking about.

If keys are to be upgraded regularly, than that routine with keys should be included in the upgrade options automatically, in general 'pacman' is not well integrated and thus also not enough user friendly. It is good for power users.

Another issue is your tracking system where it says:

  • Author: maddox
  • Status: not-a-bug
  • Priority: bug
  • Assignee:
  • Category:

Thus status being not a bug and priorit "bug" is confusing and unclear.

#5

Updated by bill-auger about 2 years ago

yes, it is a design choice - some distros try to do as much as possible automatically; and arch tries to do as little as necessary automatically

alias upgrade-system='sudo pacman -Sy archlinux-keyring parabola-keyring && sudo pacman -Syu'

that command would add a lot of time to each upgrade; because it re-installs the keyrings each time -
i think this is what you were trying for:

alias upgrade-system='sudo pacman -Sy archlinux-keyring parabola-keyring --needed ; sudo pacman -Su'

Also available in: Atom PDF