and this:
sudo pacman -Syvv
sudo pacman -Syyu
yes the command gives errors, but they should be ignored…
Sorry Brahma, the result is the same:
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
inxi-3.3.19.1-1-any 292.8 KiB 10.6 MiB/s 00:00 [############################################################################] 100%
uvesafb-dkms-1.0.4-1-x86_64 58.9 KiB 5.75 MiB/s 00:00 [############################################################################] 100%
Total (2/2) 351.7 KiB 6.02 MiB/s 00:00 [############################################################################] 100%
(228/228) checking keys in keyring [############################################################################] 100%
(228/228) checking package integrity [############################################################################] 100%
error: inxi: signature from "lilac (build machine) <lilac@build.archlinuxcn.org>" is unknown trust
:: File /var/cache/pacman/pkg/inxi-3.3.19.1-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: uvesafb-dkms: signature from "lilac (build machine) <lilac@build.archlinuxcn.org>" is unknown trust
:: File /var/cache/pacman/pkg/uvesafb-dkms-1.0.4-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.
and this:
sudo rm -rf /etc/pacman.d/gnupg
sudo rm -R /root/.gnupg/
sudo rm -f /var/lib/pacman/sync/*
sudo pacman-key --init
sudo pacman-key --populate archlinux manjaro
sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring
sudo pacman-key --refresh-keys
sudo pacman -Syyu
Sorry again Brahma: no difference, the output is the same.
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
inxi-3.3.19.1-1-any 292.8 KiB 11.0 MiB/s 00:00 [############################################################################] 100%
uvesafb-dkms-1.0.4-1-x86_64 58.9 KiB 5.75 MiB/s 00:00 [############################################################################] 100%
Total (2/2) 351.7 KiB 6.13 MiB/s 00:00 [############################################################################] 100%
(228/228) checking keys in keyring [############################################################################] 100%
(228/228) checking package integrity [############################################################################] 100%
error: inxi: signature from "lilac (build machine) <lilac@build.archlinuxcn.org>" is unknown trust
:: File /var/cache/pacman/pkg/inxi-3.3.19.1-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: uvesafb-dkms: signature from "lilac (build machine) <lilac@build.archlinuxcn.org>" is unknown trust
:: File /var/cache/pacman/pkg/uvesafb-dkms-1.0.4-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.
Any more tricks up your sleeve?
try this:
go to /etc/pacman.conf
, and locate the following section:
SigLevel = Required DatabaseOptional
and change the SigLevel
to:
SigLevel = Required DatabaseNever
and then run again these:
sudo rm -rf /etc/pacman.d/gnupg
sudo rm -R /root/.gnupg/
sudo rm -f /var/lib/pacman/sync/*
sudo pacman-key --init
sudo pacman-key --populate archlinux manjaro
sudo pacman -Sy gnupg archlinux-keyring manjaro-keyring
sudo pacman-key --refresh-keys
sudo pacman -Syyu
This took more time, pity, the result is the same.
I could paste the output, but it doesn’t give any new information.
Are we getting near a new installation?
ok so this:
so go open again /etc/pacman.conf
and edit the siglevel
to look like this:
SigLevel = Optional TrustAll
then run these:
sudo rm -f /var/lib/pacman/sync/*
sudo pacman-mirrors --continent
sudo pacman-mirrors --api --protocol https
sudo pacman -Scc
sudo pacman -Syyu
Hurray! You pulled it off!
My packetmanager says my system is up to date!
My friend, many many thanks. And thanks for your persistence.
UE
inxi
is in the Manjaro community repo, there’s no reason to install it from a third-party repo or AUR.
lilac is the archlinuxcn / Chaotic-AUR build bot. Remove the third-party repo(s) from your /etc/pacman.conf
the same way you added it/them.
Third party repos are not supported.
so nice that you have solved the problem. congrats
Just FYI: it’s “package” and “package manager”. The word “packet” is something else and used in a networking context.
Well, to be honest: it wasn’t me, it was Brahma.
There is no such line in my pacman.conf .
Could this have come right out of the upgrade package?
You’re right! Slip of the pen - that’s what you get when in a hurry…
Sorry Yochanan,
I merged two answers, only the second part about the pacman.conf was meant for you.
you should now revert the siglevel to:
SigLevel = Required DatabaseOptional
sudo pacman -Syu
then try to install something to check if you still got the issue
I did what you proposed - no problems so far.
It seems we’re not yet over the hill.
This morning I got a message about a new update, which I ran from the console using pamac update.
Here’s the output:
[ulbe@ulbe-aspire5 ~]$ LC_ALL=C pamac update
Preparing...
Bezig met synchroniseren van pakketdatabanken...
kan database niet vergrendelen
Het synchroniseren van de databanken is mislukt
Resolving dependencies...
Checking inter-conflicts...
To upgrade (1):
timeshift 22.06.3-1 (22.06.1-1) archlinuxcn 742.2 kB
Total download size: 742.2 kB
Total installed size: -110.9 kB
Apply transaction ? [y/N] y
timeshift (22.06.3-1) wordt gedownload
timeshift (22.06.3-1) is gedownload
Bezig met controleren van sleutelbos... [1/1]
Bezig met controleren van integriteit... [1/1]
Fout: timeshift: handtekening van "lilac (build machine) <lilac@build.archlinuxcn.org>" is onbekend vertrouwd
Removing invalid files and retrying...
Bezig met oplossen van afhankelijkheden...
Bezig met controleren van interne conflicten...
timeshift (22.06.3-1) wordt gedownload
timeshift (22.06.3-1) is gedownload
Bezig met controleren van sleutelbos... [1/1]
Bezig met controleren van integriteit... [1/1]
Fout: timeshift: handtekening van "lilac (build machine) <lilac@build.archlinuxcn.org>" is onbekend vertrouwd
Error: Het uitvoeren van de overdracht is mislukt: ongeldig of corrupt pakket (PGP handtekening):
copy output from:
cat /etc/pacman.conf
pamac list -qm
AUR and archlinuxcn repo (or whatever this is) are your responsibility and as said million times before, not supported by Manjaro nor Arch.
You’re just wasting everyone’s time by installing and adding some custom unsupported things and then not even mentioning that. If you want support, remove all unsupported packages and repos.