FS#63271 - Missing dependencies
Attached to Project:
Pacman
Opened by Gaetan Bisson (vesath) - Wednesday, 24 July 2019, 21:35 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 24 July 2019, 22:12 GMT
Opened by Gaetan Bisson (vesath) - Wednesday, 24 July 2019, 21:35 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 24 July 2019, 22:12 GMT
|
Details
I'm getting a very disturbing behavior from pacman-5.1.3
running `makepkg --log --noconfirm --syncdeps` inside an
x86_64 qemu virtual machine. The virtual machine is a
run-of-the-mill Arch install so it should not matter.
What happens is that pacman identifies packages to be installed, never actually downloads them, and then fails when trying to verify their signature. See the attached log file. If you have any idea what might be causing this behavior I'd be happy to try your suggestions. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Wednesday, 24 July 2019, 22:12 GMT
Reason for closing: Not a bug
Additional comments about closing: Diagnosed as a mirror problem.
Wednesday, 24 July 2019, 22:12 GMT
Reason for closing: Not a bug
Additional comments about closing: Diagnosed as a mirror problem.
If you're checking after the fact to see what the files look like, it's too late since they were deleted... can you try checking there before running makepkg, and take a look if those files validate with pacman-key?
EDIT: oops, pacman-key won't work unless you also download the signatures which aren't in the db. pacman -Swdd --debug might have some interesting information about why pacman thinks they're bad, though.