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!
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!
FS#77836 - Update keyrings prior to update everything else
Attached to Project:
Arch Linux
Opened by Michael Wyraz (mwyraz) - Monday, 13 March 2023, 06:04 GMT
Last edited by Toolybird (Toolybird) - Thursday, 13 April 2023, 22:11 GMT
Opened by Michael Wyraz (mwyraz) - Monday, 13 March 2023, 06:04 GMT
Last edited by Toolybird (Toolybird) - Thursday, 13 April 2023, 22:11 GMT
|
DetailsDescription:
When updating a system at larger intervals, it happens quite often that keys are expired and the update fails. In most situations, updating archlinux-keyring first, then re-run the system update solved this issue. Nevertheless, the forums are full of threads that are finally solved by exactly this procedure. The reason is probably, that from pacman's output it's not very obvious what the exact issue is and how to solve it. I think, this situation could be improved. 1. If an update fails due to missing key and an update to archlinux-keyring is available, pacman could suggest to update archlinux-keyring first and then re-try the installation 2. Pacman could generally suggest to update archlinux-keyring first, prior to verify subsequent packages 3. (might require a change to packet metadata) Pacman could indentify all installation keyring files and do as described in 1 or 2 for all of them |
This task depends upon
[1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/merge_requests/138