FS#28172 - Can't upgrade to tmux 1.6.1 due to failure in PGP signature

Attached to Project: Arch Linux
Opened by Teo Emmanouilidis (TeoBigusGeekus) - Monday, 30 January 2012, 11:27 GMT
Last edited by Ionut Biru (wonder) - Monday, 30 January 2012, 11:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

[[Time:13:23 Location:~/Desktop]]
$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (1): tmux-1.6-1

Total Installed Size: 0.40 MiB
Net Upgrade Size: 0.02 MiB

Proceed with installation? [Y/n] y
(1/1) checking package integrity [##################################] 100%
error: tmux: 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.
[[Time:13:27 Location:~/Desktop]]
$

When trying to upgrade tmux from 1.5.1 to 1.6.1 I receive this message.
See also this thread in Arch Linux forums:
https://bbs.archlinux.org/viewtopic.php?id=134318

I reported this to sourceforge
http://sourceforge.net/tracker/?func=detail&aid=3481590&group_id=200378&atid=973262
and it was immediately closed.

Pacman conf file signature option: SigLevel = Optional TrustedOnly

Steps to reproduce: try to upgrade tmux.
This task depends upon

Closed by  Ionut Biru (wonder)
Monday, 30 January 2012, 11:35 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#27612 
Comment by Ionut Biru (wonder) - Monday, 30 January 2012, 11:31 GMT
this is a bug in pacman-key and fixed in a future pacman release.

do pacman-key -r EA433FC7

then pacman -Syu
Comment by Teo Emmanouilidis (TeoBigusGeekus) - Monday, 30 January 2012, 11:34 GMT
Thank you very much, it worked perfectly.
You can close the report now.

Loading...