[SOLVED] Unable to upgrade libmicrohttpd

655321 · 2012-01-25 01:20:18

Here is pacman output:

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (1): libmicrohttpd-0.9.18-1

Total Installed Size:   0.37 MiB
Net Upgrade Size:       0.00 MiB

Proceed with installation? [Y/n] y
(1/1) checking package integrity                                                                                       [#######################################################################] 100%
error: libmicrohttpd: signature from "Sergej Pupykin <arch@sergej.pp.ru>" is marginal trust
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

All the keys are stored according to the pacman-key wiki page, so I did a "pacman-key --refresh-keys" in order to try and get the missing key, but nothing changed:

.
.
.
gpg: key EA433FC7: "Sergej Pupykin <arch@sergej.pp.ru>" not changed
gpg: key E62EB915: "Sven-Hendrik Haase <sh@lutzhaase.com>" not changed
gpg: key 0C84C0A5: "Thomas Dziedzic <gostrc@gmail.com>" not changed
gpg: key 295AFBF4: "Thorsten Töpper <atsutane@freethoughts.de>" not changed
gpg: key 3C4F88BC: "Timothy Redaelli <tredaelli@archlinux.info>" not changed
gpg: key C2E5C0D2: "Xyne. <xyne@archlinux.ca>" not changed

gpg: Total number processed: 57
gpg:              unchanged: 57

As you can see I have the signature on my keyring but it wont let me install the package.

thanks in advance for the help!

Last edited by 655321 (2012-02-01 23:24:41)

Thedemon007 · 2012-01-25 04:05:15

i have same problem

Here is pacman output:

Objetivos (7): freeglut-2.8.0-1  iproute2-3.2.0-2  linux-3.2.1-2
               linux-headers-3.2.1-2  package-query-1.0.1-1  sdl-1.2.15-1
               tmux-1.6-1

Tamaño instalado:       106,72 MiB
Tamaño a actualizar:    -2,79 MiB

¿Continuar con la instalación? [S/n] S
(7/7) verificando la integridad de los paquetes    [######################] 100%
error: tmux: signature from "Sergej Pupykin <arch@sergej.pp.ru>" is marginal trust
error: error al realizar la transacción (paquete no válido o dañado (firma PGP))
Ocurrieron errores, no se actualizaron paquetes

"pacman-key --refresh-keys" out:

.
.
.
gpg: clave C0711BF1: "Rashif Rahman (Ray) <schiv@archlinux.org>" sin cambios
gpg: clave 2072D77A: "Seblu <seblu@seblu.net>" sin cambios
gpg: clave EA433FC7: "Sergej Pupykin <arch@sergej.pp.ru>" sin cambios
gpg: clave E62EB915: "Sven-Hendrik Haase <sh@lutzhaase.com>" sin cambios
gpg: clave 0C84C0A5: "Thomas Dziedzic <gostrc@gmail.com>" sin cambios


gpg: Cantidad total procesada: 41
gpg:              sin cambios: 39
gpg:               nuevas firmas: 6
gpg: 3 dudosa(s) necesarias, 1 completa(s) necesarias,

brandnewmath · 2012-01-25 18:40:33

I too am having this problem, but with the tmux and maven packages.

TeoBigusDickus · 2012-01-25 23:45:24

I had this problem as well with tmux.
Try this

sudo pacman -Syu --ignore tmux

as a temporary measure.

brandnewmath · 2012-01-26 00:08:19

Indeed, I did so. Thanks for posting the tip here.

While it's good to have the other updates that were pending, I'd also like to know how to solve the problem, of course. Given that the error is "... is marginal trust", it seems like it would be possible to simply mark the key trusted, but that also seems shady somehow.

TeoBigusDickus · 2012-01-26 10:03:47

I think the problem is that Mr. Sergej Pupykin hasn't been around to create a valid key.
But, as you said, I won't risk it.

brandnewmath · 2012-01-26 22:56:05

Also noteworthy is the fact that other systems of mine have Sergej Pupykin's key and packages signed by it, and are upgrading without a problem. Here's some relevant output from my laptop for example, showing that tmux is at the latest version and I have the relevant key:

1059 james@stringer% pacman -Qs tmux                                             ~ 4:53PM
local/tmux 1.6-1
    A terminal multiplexer
1060 james@stringer% pacman-key -l 2>/dev/null |grep Sergej                      ~ 4:54PM
uid                  Sergej Pupykin <arch@sergej.pp.ru>
uid                  Sergej Pupykin <ml@sergej.pp.ru>
uid                  Sergej Pupykin <sergej@p5n.pp.ru>
uid                  Sergej Pupykin <pupykin.s@gmail.com>

Might it be a bug of some kind? Should we file a bug report just in case?

TeoBigusDickus · 2012-01-27 11:53:32

brandnewmath wrote:

Might it be a bug of some kind? Should we file a bug report just in case?

Done - I think...
http://i.imgur.com/RpmIi.jpg

mod edit: Hello, I've replaced your large image with a link. Please read Forum Etiquette: Pasting Pictures and Code. Thanks. --fsckd

Last edited by fsckd (2012-01-30 15:15:46)

TeoBigusDickus · 2012-01-30 10:36:39

Never got an answer, so I've reported the issue on sourceforge:
http://sourceforge.net/tracker/?group_i … tid=973262
(see ID 3481590)

TeoBigusDickus · 2012-01-30 11:07:08

...and had it immediately closed
http://i.imgur.com/HZCim.jpg
Bugger...

tomk · 2012-01-30 11:12:41

... because it's an Arch issue. Use the Arch bugtracker, this has nothing to with tmux, or any of the other applications that Sergej packages.

TeoBigusDickus · 2012-01-30 11:28:38

tomk wrote:

... because it's an Arch issue. Use the Arch bugtracker, this has nothing to with tmux, or any of the other applications that Sergej packages.

Done!
https://bugs.archlinux.org/task/28172

TeoBigusDickus · 2012-01-30 11:35:49

I got an aswer already and it works:

this is a bug in pacman-key and fixed in a future pacman release.
do pacman-key -r EA433FC7
then pacman -Syu

Flawless victory - thanks Ionut Biru (wonder).

Allan · 2012-01-30 12:28:26

Well, to be specific, it is a "bug" in that keyservers can not retrieve a subkey when using a 16 digit ID (which pacman passes via gpgme). gpg (and thus pacman-key) actually shortens the ID to 8 digits which works. In the next pacman update, it will try with 16 digits first, then 8 if that fails.

TeoBigusDickus · 2012-01-30 13:31:57

Allan wrote:

Well, to be specific, it is a "bug" in that keyservers can not retrieve a subkey when using a 16 digit ID (which pacman passes via gpgme). gpg (and thus pacman-key) actually shortens the ID to 8 digits which works. In the next pacman update, it will try with 16 digits first, then 8 if that fails.

Thanks for the clarification, appreciated.

655321 · 2012-01-31 04:15:23

Its cool to see that the issue has being fix already I will also try this tonight and come back to report if this fixes the issue with libmicrohttpd. It's very likely that it will work but just to be sure and have it documented.

cheers

655321 · 2012-02-01 23:24:18

Fixed! thanks for the help, marking as solved!

Arch Linux

#1 2012-01-25 01:20:18

[SOLVED] Unable to upgrade libmicrohttpd

#2 2012-01-25 04:05:15

Re: [SOLVED] Unable to upgrade libmicrohttpd

#3 2012-01-25 18:40:33

Re: [SOLVED] Unable to upgrade libmicrohttpd

#4 2012-01-25 23:45:24

Re: [SOLVED] Unable to upgrade libmicrohttpd

#5 2012-01-26 00:08:19

Re: [SOLVED] Unable to upgrade libmicrohttpd

#6 2012-01-26 10:03:47

Re: [SOLVED] Unable to upgrade libmicrohttpd

#7 2012-01-26 22:56:05

Re: [SOLVED] Unable to upgrade libmicrohttpd

#8 2012-01-27 11:53:32

Re: [SOLVED] Unable to upgrade libmicrohttpd

#9 2012-01-30 10:36:39

Re: [SOLVED] Unable to upgrade libmicrohttpd

#10 2012-01-30 11:07:08

Re: [SOLVED] Unable to upgrade libmicrohttpd

#11 2012-01-30 11:12:41

Re: [SOLVED] Unable to upgrade libmicrohttpd

#12 2012-01-30 11:28:38

Re: [SOLVED] Unable to upgrade libmicrohttpd

#13 2012-01-30 11:35:49

Re: [SOLVED] Unable to upgrade libmicrohttpd

#14 2012-01-30 12:28:26

Re: [SOLVED] Unable to upgrade libmicrohttpd

#15 2012-01-30 13:31:57

Re: [SOLVED] Unable to upgrade libmicrohttpd

#16 2012-01-31 04:15:23

Re: [SOLVED] Unable to upgrade libmicrohttpd

#17 2012-02-01 23:24:18

Re: [SOLVED] Unable to upgrade libmicrohttpd

Board footer