You are not logged in.

#1 2020-05-20 01:53:52

amish
Member
Registered: 2014-05-10
Posts: 470

[Solved] error: evince: signature format error

So I did pacman -Syu just now

Although it printed error for evince package, it still went ahead and installed the package.

I am just curious what the error was for? And why did pacman go ahead in spite of that being an error?


Total Installed Size:  102.08 MiB
Net Upgrade Size:       -2.88 MiB

:: Proceed with installation? [Y/n]
(7/7) checking keys in keyring                                                                                     [#####################################################################] 100%
error: evince: signature format error
(7/7) checking package integrity                                                                                   [#####################################################################] 100%
(7/7) loading package files                                                                                        [#####################################################################] 100%
(7/7) checking for file conflicts                                                                                  [#####################################################################] 100%
(7/7) checking available disk space                                                                                [#####################################################################] 100%
:: Running pre-transaction hooks...
(1/1) Inhibiting system shutdown, reboot etc.
:: Processing package changes...
(1/7) upgrading python                                                                                             [#####################################################################] 100%
(2/7) upgrading bind-tools                                                                                         [#####################################################################] 100%
(3/7) upgrading bind                                                                                               [#####################################################################] 100%
(4/7) upgrading pcre2                                                                                              [#####################################################################] 100%
(5/7) upgrading evince                                                                                             [#####################################################################] 100%
(6/7) upgrading perl-timedate                                                                                      [#####################################################################] 100%
(7/7) upgrading python-packaging                                                                                   [#####################################################################] 100%
:: Running post-transaction hooks...
(1/9) Creating system user accounts...
(2/9) Reloading system manager configuration...
(3/9) Creating temporary files...
(4/9) Arming ConditionNeedsUpdate...
(5/9) Warn about old perl modules
(6/9) Compiling GSettings XML schema files...
(7/9) Updating icon theme caches...
(8/9) Updating the desktop file MIME type cache...
(9/9) Permitting system shutdown, reboot etc.

Last edited by amish (2020-05-21 00:57:12)

Offline

#2 2020-05-20 02:00:03

loqs
Member
Registered: 2014-03-06
Posts: 17,195

Re: [Solved] error: evince: signature format error

Offline

#3 2020-05-20 02:15:38

amish
Member
Registered: 2014-05-10
Posts: 470

Re: [Solved] error: evince: signature format error

Great! That was fast reply!

But I would still like to know why did pacman go ahead and install it even if there was some kind of error in signature?

Offline

#4 2020-05-20 15:36:17

eschwartz
Fellow
Registered: 2014-08-08
Posts: 4,097

Re: [Solved] error: evince: signature format error

amish wrote:

Great! That was fast reply!

But I would still like to know why did pacman go ahead and install it even if there was some kind of error in signature?

There was no error in the signature, the signature was fine.

There was, however, an error in "try to parse the signature and extract a key-id for use in offering a prompt to download missing keys". pacman failed to parse the signature and extract a key-id, and therefore would not be able to offer this prompt, fortunately the prompt was not needed because libgpgme was able to validate the signature by running /usr/bin/gpg with the existing keyring.

It should be fixed by https://lists.archlinux.org/pipermail/p … 24377.html


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

Board footer

Powered by FluxBB