FS#75321 - [archlinux-keyring] Archinstall crashes when run due to a corrupted package (VBox only?)

Attached to Project: Arch Linux
Opened by Theo Campbell (TheoCGaming) - Thursday, 14 July 2022, 17:26 GMT
Last edited by Jonas Witschel (diabonas) - Friday, 15 July 2022, 20:50 GMT
Task Type Bug Report
Category Mirrors
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: ArchInstall command in ArchISO crashes in VirtualBox while trying to update archlinux-keyring.


Additional info:
* package version(s) | All are latest up to 07/01/2022 (MM/DD/YYYY)
* config and/or log files etc. | Only log resources I am given are in the screenshots I sent.

Steps to reproduce:
have virtualbox
use version 07/01/22 of archiso
try to install it to a raw vmdk pointing to a usb drive (or you could test it on a real vmdk file)
This task depends upon

Closed by  Jonas Witschel (diabonas)
Friday, 15 July 2022, 20:50 GMT
Reason for closing:  Works for me
Comment by Jonas Witschel (diabonas) - Thursday, 14 July 2022, 20:36 GMT
I cannot reproduce this. Is your system time set correctly?
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 01:11 GMT
It is automatically set to my main PC's time, which according to time.org itself is completely exact.
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 01:13 GMT
However, what may help is that I am using a Cruzer Glide, as the Cruzer Spark I was using began developing drive errors and it is no longer being sold at my nearby retailers.
Comment by Jonas Witschel (diabonas) - Friday, 15 July 2022, 07:02 GMT
Please post the output of the following command:

pacman-key --verify /var/cache/pacman/pkg/archlinux-keyring-20220713-1-any.pkg.tar.zst.sig
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 19:57 GMT
```
==> Checking /var/cache/pacman/pkg/archlinux-keyring-20220713-1-any.pkg.tar.zst.sig... (embedded)
grep: /var/cache/pacman/pkg/archlinux-keyring-20220713-1-any.pkg.tar.zst.sig: No such file or directory
gpg: can't open '/var/cache/pacman/pkg/archlinux-keyring-20220713-1-any.pkg.tar.zst.sig': No such file or directory
gpg: verify signatures failed: No such file or directory
==> ERROR: The signature identified by /var/cache/pacman/pkg/archlinux-keyring-20220713-1-any.pkg.tar.zst.sig could not be verified.
1 root@archiso ~ # pacman-key --verify /var/cache/pacman/pkg/arch [<-- pressed tab here]
No matches for: `file'
```
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 19:58 GMT
Even searching for just "arch", nothing pops up...
Comment by Jonas Witschel (diabonas) - Friday, 15 July 2022, 20:13 GMT
Did you try updating archlinux-keyring this time around (either by running "archinstall" or by using "pacman -Sy archlinux-keyring")? The screenshots you posted clearly show that the problem is with /var/cache/pacman/pkg/archlinux-keyring-20220713-1-any.pkg.tar.zst, so at least that file must be there (otherwise the error message would be different).
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:16 GMT
It could be that it's not meant to be in the ISO and something got it as a dependency
Comment by Jonas Witschel (diabonas) - Friday, 15 July 2022, 20:21 GMT
That does not answer my question... /var/cache/pacman/pkg/archlinux-keyring-20220713-1-any.pkg.tar.zst gets downloaded when you run something like "archinstall" or "pacman -Sy archlinux-keyring", it is not part of the ISO from the beginning. Your error message shows that the downloaded file cannot be validated, hence me asking you to download it first using on of these commands, then running "pacman-key --verify" to check what is wrong with it.
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:27 GMT
"error: keyring is not writable"
"error: required key missing from keyring"
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:28 GMT
It can't write to the ISO.
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:30 GMT
"You do not have sufficient permissions to read the pacman keyring"
Hmm, okay...
Comment by Jonas Witschel (diabonas) - Friday, 15 July 2022, 20:31 GMT
That is not an error message that pacman-key is able to produce. You *need* to post which commands you are running and their *full* output, not just some random snippets.
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:32 GMT
Entire thing, posted as an attachment
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:36 GMT
Here it is- apparently it was too big
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:36 GMT
aA
Comment by Jonas Witschel (diabonas) - Friday, 15 July 2022, 20:45 GMT
If you initialise the keyring manually, you also need to run "pacman-key --populate archlinux" before running "pacman-key --verify ...", otherwise the necessary keys will not be available. Doing this manually should not be necessary in the first place, so I suspect either your virtual machine has not enough memory to be able to install the keyring to RAM, or you already did something weird to the keyring directory before.
Comment by Theo Campbell (TheoCGaming) - Friday, 15 July 2022, 20:47 GMT
it has 4gb allocated, so it shouldn't be too much of an issue right?

I can't do anything to the keyring directory on the iso, so idk
Comment by Jonas Witschel (diabonas) - Friday, 15 July 2022, 20:49 GMT
Clearly you can, otherwise "pacman-key --init" would have failed. Anyway, this is not an issue with the archlinux-keyring package, and I am pretty sure it is not an issue with archiso either. Please use the support channels if you need further assistance.

Loading...