pacstrap complaining about corrupt package
Hi all,
Trying to install Arch on a new birthday/Christmas present. I'm manually copying this (abbreviated) because I can't figure out how to get the text off the new box:
# pacstrap /mnt linux linux-firmware base btrfs-progs intel-ucode nano iw [snipped the package list and stuff] :: Retrieving packages... openssl-3.0.7-4-x86_64 ... (126/126) checking keys in keyring (126/126) checking package integrity error: openssl: signature from "Pierre Schmitzpierre@archlinux.org" is marginal trust :: File /mnt/var/cache/pacman/pkg/openssl-3.0.7-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). [failure messages]
Things I've tried/checked: * clock on the new box has correct time * pacman -Syu from another machine. That pulled down a new archlinux-keyring and openssl-3.0.7-4 and it ran fine * new machine has same mirrorlist that worked with the pacman -Syu * commented out mirrorlist entries one-at-a-time to see if it was one mirror problem. 5 servers all give the same results.
The other 125 packages that were downloaded all passed the integrity check (I think).
Any suggestions?
TIA, Dave Murray
The keyring shipped in the 2022.12.01 ISO is outdated. You’ll need to update it using `pacman -Sy archlinux-keyring` first before pacstrap-ping :)
Hi all,
Trying to install Arch on a new birthday/Christmas present. I'm manually copying this (abbreviated) because I can't figure out how to get the text off the new box:
# pacstrap /mnt linux linux-firmware base btrfs-progs intel-ucode nano iw [snipped the package list and stuff] :: Retrieving packages... openssl-3.0.7-4-x86_64 ... (126/126) checking keys in keyring (126/126) checking package integrity error: openssl: signature from "Pierre Schmitz pierre@archlinux.org pierre@archlinux.org" is marginal trust :: File /mnt/var/cache/pacman/pkg/openssl-3.0.7-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). [failure messages]
Things I've tried/checked:
- clock on the new box has correct time
- pacman -Syu from another machine. That pulled down a new archlinux-keyring and openssl-3.0.7-4 and it ran fine
- new machine has same mirrorlist that worked with the pacman -Syu
- commented out mirrorlist entries one-at-a-time to see if it was one mirror problem. 5 servers all give the same results.
The other 125 packages that were downloaded all passed the integrity check (I think).
Any suggestions?
TIA, Dave Murray
Hello,
After several successful manual Arch installs, I tried to use the `archinstall` command from the Arch Linux ISO image.
I created just one EXT4 partition, and configured its mountpount to /mnt. Also made it bootable. (type: primary, start at 1024B (the default), size "100%") Hit save and exit.
When I start the installation it says "parted ended with bad exit code: 256". "The closest location we can manage is 1024B to 512MB..."
Usually you do not need a "boot" partition and you should be able to just go with one EXT4 partition. I did that in the manual install by just using fdisk and use the default values by hitting Enter.
Does someone know how to use a single EXT4 partition in the arch installer?
Regards Martin
On 12/25/22 00:17, Mike Yuan wrote:
The keyring shipped in the 2022.12.01 ISO is outdated. You’ll need to update it using `pacman -Sy archlinux-keyring` first before pacstrap-ping :)
Hi all, Trying to install Arch on a new birthday/Christmas present. I'm manually copying this (abbreviated) because I can't figure out how to get the text off the new box: # pacstrap /mnt linux linux-firmware base btrfs-progs intel-ucode nano iw [snipped the package list and stuff] :: Retrieving packages... openssl-3.0.7-4-x86_64 ... (126/126) checking keys in keyring (126/126) checking package integrity error: openssl: signature from "Pierre Schmitz<pierre@archlinux.org> <mailto:pierre@archlinux.org>" is marginal trust :: File /mnt/var/cache/pacman/pkg/openssl-3.0.7-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)). [failure messages] Things I've tried/checked: * clock on the new box has correct time * pacman -Syu from another machine. That pulled down a new archlinux-keyring and openssl-3.0.7-4 and it ran fine * new machine has same mirrorlist that worked with the pacman -Syu * commented out mirrorlist entries one-at-a-time to see if it was one mirror problem. 5 servers all give the same results. The other 125 packages that were downloaded all passed the integrity check (I think). Any suggestions? TIA, Dave Murray
That fixed it. Thanks Mike. I've never noticed that before, where the filename (version) didn't change, yet the file updated.
Dave
Hello,
This is a bug with pacman as far as I am aware, it is missing the gpg signing keys which the latest version of the archlinux-keyring package contains.
When pacman tries to verify the signature of the certificate, it fails as it is using the wrong certificate.
Simply update the package on its own and then you are all set.
Polarian
I meant package not certificate sowwy >~<
Polarian
participants (4)
-
bf
-
David N Murray
-
Mike Yuan
-
Polarian