Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#76854 - Installation from PXE makes PGP signature error.

Attached to Project: Arch Linux
Opened by Yongsub Chung (litdream) - Saturday, 17 December 2022, 02:07 GMT
Last edited by Toolybird (Toolybird) - Saturday, 17 December 2022, 21:16 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I have an old laptop, which doesn't boot with USB media. So, I set up PXE on another laptop following this wiki (https://wiki.archlinux.org/title/Preboot_Execution_Environment).

Boot into the arch prompt was successful, but `pacstrap -K ...` command first failed because it couldn't write to keying:
```
error: keyring is not writable
```

Then, I issued `pacman-key --init` as suggested from the output.
The output said, at least I interpreted, Successful.

But, then, the second `pacstrap -K ...` gives "invalid or corrupted package (PGP signature)" error.
I tried some remedy from google search, but none worked. Can someone take a look?
Output are captured in textile.

Thank you.



Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
   arch-pxe-sigerr.txt (59.3 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Saturday, 17 December 2022, 21:16 GMT
Reason for closing:  None
Additional comments about closing:  See comments
Comment by Yongsub Chung (litdream) - Saturday, 17 December 2022, 02:14 GMT
I used following downloaded images for setting up PXE:

% sha256sum archlinux-2022.11.01-x86_64.iso archlinux-2022.12.01-x86_64.iso
df6749df55b02cec98e5a9177c7957acfb96fe14d04553b6e4714100a4824f68 archlinux-2022.11.01-x86_64.iso
de301b9f18973e5902b47bb00380732af38d8ca70084b573ae7cf36a818eb84c archlinux-2022.12.01-x86_64.iso
Comment by Yongsub Chung (litdream) - Saturday, 17 December 2022, 15:20 GMT
Somehow, after reinitializing gpg, this problem was solved.

```
gpg --full-gen-key
pkill gpg-agent
pacman-key --init
pacman-key --populate
pacstrap -K /mnt base linux linux-firmware
```

Comment by Yongsub Chung (litdream) - Saturday, 17 December 2022, 15:20 GMT
This can be resolved. But, still wondering why this happened.

So, it started with `pacstrap` couldn't write to keyring.
keyring related configuration wasn't in the installation wiki.
Comment by nl6720 (nl6720) - Saturday, 17 December 2022, 17:19 GMT
I'm guessing it's because you run pacstrap while pacman-init.service was still running. You need to wait until pacman-init.service finishes before running pacman, pacstrap or archinstall.
Comment by Toolybird (Toolybird) - Saturday, 17 December 2022, 21:16 GMT
Yes, I believe @nl6720 is on the money. The situation is a lot better than it used to be after [1] was fixed, but there is still a delay, which is most noticeable on old, slow hardware.

[1] https://gitlab.archlinux.org/archlinux/archiso/-/issues/191

Loading...