You are not logged in.
During the usual
# pacman -Syuthe operation couldn't complete.
"vmaf" resulted "corrupted or unable to verify PGP".
I tried removing it and reinstalling "vmaf" but it didn't work either because the dependency is required from ffmpeg.
What can I try here?
Thanks in advance for the support.
Last edited by ordinary.schreiber (2022-02-19 11:10:46)
Offline
Offline
Ok, I looked for the .part file but couldn't find any.
The only vmaf- files in that directory are:
$ ls /var/cache/pacman/pkg
vmaf-1.5.3-1-x86_64.pkg.tar.zst
vmaf-1.5.3-1-x86_64.pkg.tar.zst.sigShould I just delete them and reinstall the package?
How important is the dependency for ffmpeg?
Offline
You can try to delete the package from the cache, but if you're conducting partial/late updates and the problem is a missing key in your keyring, that's not gonna help you.
=> post the actual and complete pacman output.
vmaf is linked by avfilter - it's a pretty important dependency.
Edit: I should not rephrase sentences mid-through…
Last edited by seth (2022-02-18 14:45:13)
Offline
Here is the full output:
# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (23) alsa-card-profiles-1:0.3.47-1 aom-3.3.0-1
btrfs-progs-5.16.2-1 cups-filters-1.28.12-1 ffmpeg-2:5.0-4
ffmpeg4.4-4.4.1-3 firefox-97.0.1-1
gst-plugins-base-1.20.0-2 gst-plugins-base-libs-1.20.0-2
gst-plugins-good-1.20.0-2 gstreamer-1.20.0-2
libde265-1.0.8-2 libreoffice-fresh-7.3.0-5
librsvg-2:2.52.6-1 libwnck3-40.1-1 linux-5.16.10.arch1-1
nodejs-17.5.0-1 pipewire-1:0.3.47-1
pipewire-pulse-1:0.3.47-1 qt5-base-5.15.2+kde+r301-1
vlc-3.0.16-8 vmaf-2.3.0-1 x264-3:0.164.r3081.19856cc-1
Total Download Size: 9.75 MiB
Total Installed Size: 1088.86 MiB
Net Upgrade Size: 28.32 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
nodejs-17.5.0-1-... 9.4 MiB 1804 KiB/s 00:05 [#################] 100%
vmaf-2.3.0-1-x86_64 405.4 KiB 1621 KiB/s 00:00 [#################] 100%
Total (2/2) 9.7 MiB 1764 KiB/s 00:06 [#################] 100%
(23/23) checking keys in keyring [#################] 100%
(23/23) checking package integrity [#################] 100%
error: vmaf: signature from "Daniel Bermond <dbermond@archlinux.org>" is marginal trust
:: File /var/cache/pacman/pkg/vmaf-2.3.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.Offline
Well archlinux-keyring isn't in the update list. When did you install this system? If it was recently, what ISO did you use?
Offline
Scimmia noticed that archlinux-keyring is indeed not in the list.
By hiding that pacman complained about signature you just made it harder to provide help.
It seems the system is outdated, which should not be the case. To resolve that first upgrade archlinux-keyring and then the rest of the system. If that fails, and only if that fails, reset the keyring.
Last edited by mpan (2022-02-18 14:34:51)
Offline
Yep, we need more info before making a recommendataion.
Last edited by Scimmia (2022-02-18 14:36:27)
Offline
pacman -Qi archlinux-keyring
pacman-key --list-keys dbermondOffline
Here is the output of those two commands:
# pacman -Qi archlinux-keyring
Name : archlinux-keyring
Version : 20220125-1
Description : Arch Linux PGP keyring
Architecture : any
URL : https://gitlab.archlinux.org/archlinux/archlinux-keyring/
Licenses : GPL3
Groups : None
Provides : None
Depends On : None
Optional Deps : None
Required By : pacman
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 1469.27 KiB
Packager : Christian Hesse <eworm@archlinux.org>
Build Date : Wed 26 Jan 2022 08:30:20 AM UTC
Install Date : Tue 15 Feb 2022 10:53:49 PM UTC
Install Reason : Installed as a dependency for another package
Install Script : Yes
Validated By : Signature
# pacman-key --list-keys dbermond
pub rsa2048 2016-06-27 [SC]
3FFA6AB7B69AAE6CCA263DDE019A7474297D8577
uid [ full ] Daniel Bermond <danielbermond@gmail.com>
uid [ unknown] Daniel Bermond <dbermond@archlinux.org>
sub rsa2048 2016-06-27 [E]
pub ed25519 2021-10-30 [SC] [expires: 2026-10-29]
80247D99EABD3A4D1E3A1836E85B8683EB48BC95
uid [marginal] Daniel Bermond <dbermond@archlinux.org>
sub cv25519 2021-10-30 [E] [expires: 2026-10-29]When did you install this system? If it was recently, what ISO did you use?
I installed my system using the 2022.01 release and following the official installation instructions from the wiki.
After system installation I installed the following packages
xfce4 xfce4-goodies xdg-user-dirs lightdm lightdm-gtk-greeterand after that I've been using the system efficiently for the last couple of weeks until now.
Offline
OK, so you used the January ISO, but *when* did you install the system. If it was after the last keyring package release, you probably hit the bug where the actual keyring doesn't get updated and you end up with the one from the ISO.
When people ask questions, it's for a reason. I asked 2 things, you answered 1.
Last edited by Scimmia (2022-02-18 23:26:21)
Offline
Right, I'm sorry.
I used the January ISO but installed the system literally two weeks ago.
Is that where the problem is? Any way to fix it?
Thanks in advance.
Offline
"pacman-key --keyserver hkps://keyserver.ubuntu.com --refresh-keys" will likely do - in doubt, re-install archlinux-keyring
Offline
Thank you a lot, that solved it.
Offline