If you can’t download pacman-static inside chroot, you could download it outside and copy it to the mounted location and use it then.
After the update, I would recommend reinstalling all your packages, something really bad happened during the update.
However, if this fails, you probably ran out of disk space or broken RAM or disk during the update and fixing it might take insufferable more time than a new install.
same here. tried the same steps of @shadowsofnoxus yesterday with no success. don’t know but the keyrings are corrupted.
What have to do, pacman-static, with the keyrings?
Nope: the hardware is sane.
Furthermore the mentioned issue has been encoutnered also by other people in this discussion.
I think today comes an update that solves this issue, can someone confirm?
In previous updates philm said:
You may have problems installing this update if the maintenance keys are missing
A possible solution could be:
sudo rm -r /etc/pacman.d/gnupg
sudo pacman-key --init
sudo pacman-key --populate manjaro
sudo pacman-key --populate archlinux
sudo pacman -Syvv manjaro-keyring # just to test for key-problems, as this would fail
However, we recommend to remove the signatures of the failed packages in /var/cache/pacman/pkg/ and get the replaced ones from Build-Server :
sudo rm -v /var/cache/pacman/pkg/*.sig
sudo pacman -Syvv
I had this error crop up, but didn’t fiddle with anything the last few days because I’ve been busy. When I ran this command it updated the keys and as far as I can tell everything is updating and working for me.
sudo pacman -Syvv manjaro-keyring
Problem started with (through GUI, did reinstall, no solution):
Preparing...
Warning: manjaro-keyring-20220421-1 is up to date -- reinstalling
Resolving dependencies...
Checking inter-conflicts...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Using system disk as snapshot device for creating snapshots in BTRFS mode
/dev/dm-0 is mounted at: /run/timeshift/backup, options: rw,relatime,ssd,space_cache=v2,subvolid=5,subvol=/
Creating new backup...(BTRFS)
Saving to device: /dev/dm-0, mounted at path: /run/timeshift/backup
Created directory: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-04-25_03-00-28
Created subvolume snapshot: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-04-25_03-00-28/@
Created subvolume snapshot: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-04-25_03-00-28/@home
Created control file: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-04-25_03-00-28/info.json
BTRFS Snapshot saved successfully (0s)
Tagged snapshot '2022-04-25_03-00-28': ondemand
------------------------------------------------------------------------------
/dev/dm-0 is mounted at: /run/timeshift/backup, options: rw,relatime,ssd,space_cache=v2,subvolid=5,subvol=/
------------------------------------------------------------------------------
Removing snapshot: 2022-04-17_03-05-18
Deleting subvolume: @home (Id:988)
Deleted subvolume: @home (Id:988)
Destroying qgroup: 0/988
Destroyed qgroup: 0/988
Deleting subvolume: @ (Id:987)
Deleted subvolume: @ (Id:987)
Destroying qgroup: 0/987
Destroyed qgroup: 0/987
Deleted directory: /run/timeshift/backup/timeshift-btrfs/snapshots/2022-04-17_03-05-18
Removed snapshot: 2022-04-17_03-05-18
------------------------------------------------------------------------------
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2022-04-25 03:00:29 | timeshift-btrfs/snapshots/2022-04-25_03-00-28/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-04-25 03:00:02 | timeshift-btrfs/snapshots/2022-04-25_03-00-02/@ | boot | N/A |
Found snapshot: 2022-04-25 02:53:52 | timeshift-btrfs/snapshots/2022-04-25_02-53-52/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-04-25 02:53:25 | timeshift-btrfs/snapshots/2022-04-25_02-53-25/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-04-24 22:00:01 | timeshift-btrfs/snapshots/2022-04-24_22-00-01/@ | daily | N/A |
Found snapshot: 2022-04-24 20:00:01 | timeshift-btrfs/snapshots/2022-04-24_20-00-01/@ | weekly | N/A |
Found snapshot: 2022-04-23 22:00:01 | timeshift-btrfs/snapshots/2022-04-23_22-00-01/@ | daily | N/A |
Found snapshot: 2022-04-23 15:48:56 | timeshift-btrfs/snapshots/2022-04-23_15-48-56/@ | boot | N/A |
Found snapshot: 2022-04-22 22:00:02 | timeshift-btrfs/snapshots/2022-04-22_22-00-02/@ | daily | N/A |
Found snapshot: 2022-04-22 14:59:36 | timeshift-btrfs/snapshots/2022-04-22_14-59-36/@ | boot | N/A |
Found snapshot: 2022-04-21 22:00:02 | timeshift-btrfs/snapshots/2022-04-21_22-00-02/@ | daily | N/A |
Found snapshot: 2022-04-21 15:31:34 | timeshift-btrfs/snapshots/2022-04-21_15-31-34/@ | boot | N/A |
Found snapshot: 2022-04-20 22:00:02 | timeshift-btrfs/snapshots/2022-04-20_22-00-02/@ | daily | N/A |
Found snapshot: 2022-04-17 20:00:01 | timeshift-btrfs/snapshots/2022-04-17_20-00-01/@ | weekly | N/A |
Found snapshot: 2022-04-17 11:37:02 | timeshift-btrfs/snapshots/2022-04-17_11-37-02/@ | boot | N/A |
Found snapshot: 2022-04-16 02:00:02 | timeshift-btrfs/snapshots/2022-04-16_02-00-02/@ | hourly | N/A |
Found snapshot: 2022-04-16 01:00:01 | timeshift-btrfs/snapshots/2022-04-16_01-00-01/@ | hourly | N/A |
Found snapshot: 2022-04-16 00:00:02 | timeshift-btrfs/snapshots/2022-04-16_00-00-02/@ | hourly | N/A |
Found snapshot: 2022-04-10 20:00:01 | timeshift-btrfs/snapshots/2022-04-10_20-00-01/@ | weekly | N/A |
Found snapshot: 2022-03-27 20:00:02 | timeshift-btrfs/snapshots/2022-03-27_20-00-01/@ | monthly | N/A |
Found 20 snapshot(s)
Unmount /tmp/grub-btrfs.vBQ7pxCcz0 .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
Reinstalling manjaro-keyring (20220421-1)...
==> Appending keys from manjaro.gpg...
gpg: error reading key: No public key
Error while configuring manjaro-keyring
gpg: error reading key: No public key
Error while configuring manjaro-keyring
==> Disabling revoked keys in keyring...
-> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-02
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Refreshing PackageKit...
Transaction successfully finished.
sudo pacman -Syvv manjaro-keyring outputs the same.
Tried @shadowsofnoxus solution, but
sudo pacman-key --populate archlinux manjaro
outputs:
sudo pacman-key --populate archlinux manjaro ✔
==> Appending keys from archlinux.gpg...
==> Appending keys from manjaro.gpg...
gpg: error reading key: No public key
gpg: error reading key: No public key
==> Disabling revoked keys in keyring...
-> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-02
Today I received an update of archlinux-keyring and went fine without errors.
The errors remains, however, for manjaro-keyring, which is packaged by philm, so I ping @philm: did you take a look on this package?
Are there any updates to fix this problem?
did you tried these commands:
sudo rm -v /var/cache/pacman/pkg/*.sig
sudo pacman -Syvv
sudo pacman -Syu
Do you actually have an error?
pamac reinstall manjaro-keyring archlinux-keyring should fix this. (Update your mirrors first.)
I am still getting the same error:
Reinstalling manjaro-keyring (20220421-1)... [1/2]
==> Appending keys from manjaro.gpg...
gpg: error reading key: No public key
Error while configuring manjaro-keyring
gpg: error reading key: No public key
Error while configuring manjaro-keyring
==> Disabling revoked keys in keyring...
-> Disabled 2 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-06
Reinstalling archlinux-keyring (20220424-1)... [2/2]
==> Appending keys from archlinux.gpg...
==> Updating trust database...
gpg: next trustdb check due at 2022-05-06
==> Updating trust database...
gpg: next trustdb check due at 2022-05-06
Running post-transaction hooks...
Arming ConditionNeedsUpdate... [1/2]
Refreshing PackageKit... [2/2]
Transaction successfully finished.
This did not work for me.
I think it was successful - it worked as it should have.
Feedback is important.
What responses did you get?
again: I think it worked and the
wasn’t needed
I posted the output above so there is nothing else to add.
The arch keyring reinstallation appears to work fine but there is still a gpg error for the manjaro keyring. There is nothing else for me to post other than what I pasted above when I tried to reinstall it.
yes, but the result is a successful transaction
IDK about the error messages in between.
It looks like the end result is fine.
That can be safely ignored. It just means there are two expired keys in the keyring. One is from a previous team member who’s very few remaining packages have been resigned and one is a current team member that currently has no packages in the repo.
Is it normal for it to continue disabling the two when syvv manjaro-keyring is ran?
The issue has been resolved with manjaro-keyring 20220503-1.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.