FS#25812 - inconsistent SigLevel effects

Attached to Project: Pacman
Opened by Jakob Matthes (jakobm) - Monday, 29 August 2011, 16:39 GMT
Last edited by Dan McGee (toofishes) - Monday, 29 August 2011, 16:52 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version git
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

pacman-git f46db04 (2011-08-29)
SigLevel option not explicitly set

~# pacman -S testing/nspr
[...]
:: Retrieving packages from testing...
nspr-4.8.9-2-i686
:: File /var/cache/pacman/pkg/nspr-4.8.9-2-i686.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]

~# pacman -S core/bzip2
runs correctly

Sync databases are updated (mirror set to ftp.archlinux.org).
If I set SigLevel = Never, the installation of testing/* passes correctly.
It looks like pacman handles the testing repository differently. I am using the standard pacman.conf without modifications, but this really looks like a user/configuration error to me.

What could cause such behaviour?
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 29 August 2011, 16:52 GMT
Reason for closing:  Not a bug
Comment by Dan McGee (toofishes) - Monday, 29 August 2011, 16:52 GMT
SigLevel is Optional by default if left unset.
testing/nspr is signed.
core/bzip2 doesn't even have signatures.

Nothing inconsistent here.

Loading...