Open rafnov opened 2 weeks ago
i see from the log that the last command which causing this error is:
pikspect => pacman --color=always --sync --sysupgrade
does the error persists if run that pacman command directly without pikaur?
No, it finished fine. Log from translator as I run with my locale:
:: Starting full system upgrade....
warning: linux: ignoring package upgrade (6.11.2.arch1-1 => 6.11.6.arch1-1)
resolving dependencies...
looking for conflicting packages...
Packages (1) hwdata-0.389-1
To install: 9.28 MiB
Change after update: 0.02 MiB
:: Continue installation? [T/n]
(1/1) checking keys in the database [##############################################] 100%
(1/1) checking package integrity [##############################################] 100%
(1/1) loading file list [##############################################] 100%
(1/1) checking file conflicts [##############################################] 100%
(1/1) checking available disk space [##############################################] 100%
:: Processing package changes....
(1/1) updating hwdata [##############################################] 100%
:: Running post-transaction...
(1/1) Arming ConditionNeedsUpdate...```
this doesn't make any sense
and what happens if you run it again in the pikaur?
GPGME error again:
:: Retrieving packages...
curl-8.11.0-1-x86_64 1136.8 KiB 1612 KiB/s 00:01 [##############################################] 100%
libheif-1.19.2-1-x86_64 516.6 KiB 2.29 MiB/s 00:00 [##############################################] 100%
gpgme-1.24.0-1-x86_64 462.2 KiB 2010 KiB/s 00:00 [##############################################] 100%
Total (3/3) 2.1 MiB 1590 KiB/s 00:01 [##############################################] 100%
(3/3) checking keys in keyring [##############################################] 100%
(3/3) checking package integrity [##############################################] 100%
error: GPGME error: General error
error: GPGME error: General error
error: GPGME error: General error
error: curl: missing required signature
:: File /var/cache/pacman/pkg/curl-8.11.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: gpgme: missing required signature
:: File /var/cache/pacman/pkg/gpgme-1.24.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: libheif: missing required signature
:: File /var/cache/pacman/pkg/libheif-1.19.2-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Again pacman upgraded those packages successfully. Maybe that was something wrong with gpgme? I will check again later as now it says "there is nothing to do".
then make sure you don't have this option set in pikaur's config:
https://github.com/actionless/pikaur?tab=readme-ov-file#gpgdir-default--root-default-etcpacmandgnupg
(or better try with the empty config, so it would just use defaults)
That one is not set in ~/.config/pikaur.conf. https://0x0.st/XDp4.conf
@actionless , what more info do you need? The problem persists. Pikaur never bothered me about missing keys before. On the other hand: it always warned working on root account - now it does not. Pikaur just calls pacman and elevates priviledges when needed, right? So what do I miss? I can install package fine on root account with pikaur, I can't via user account.
since you have close-to-default pikaur config, and the problem not happens in general with default arch setup but happens to you during privilege escalation only - then some of your custom settings (for example related to gpg keys, pacman or smth else in the middle) is not passing correctly during user escalation:
mb it's this thing: https://github.com/actionless/pikaur?tab=readme-ov-file#preserveenv-default-pkgdestvisualeditorhttp_proxyhttps_proxyftp_proxyhttp_proxyhttps_proxyftp_proxyall_proxy
mb smth else, but the only way to figure it out - you could try running up a docker container or VM with a clean arch install - and next porting there you setting there one by one until it breaks
Description:
I have this problem since more than 24 hours with any file I try to update with pikaur -Syu, while pacman installs them fine, without any issue.
Attached log: