You are not logged in.

#1 2017-09-19 01:40:29

Barkester
Member
Registered: 2017-07-01
Posts: 28

bad keys stopping my update. Easy fix?

Been trying to update a week or so, but Pomozov's keys are unknown for the ninja compiler and I can't really think of many other worse places to accept a bad key security-wise than a compiler... so i'm just not updating anymore for now.

Here's my latest outpt :

:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
archlinuxfr is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (358)  #Lots of packages I won't bother you with.

Total Download Size:      3.71 MiB
Total Installed Size:  2490.10 MiB
Net Upgrade Size:         4.64 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
fuse-common-3.2.0-1-x86_64     10.3 KiB  0.00B/s 00:00 [#############################] 100%
fuse2-2.9.7-4-x86_64          103.1 KiB  2.52M/s 00:00 [#############################] 100%
gdb-common-8.0.1-1-x86_64      62.4 KiB  2.03M/s 00:00 [#############################] 100%
gdb-8.0.1-1-x86_64              3.5 MiB  5.75M/s 00:01 [#############################] 100%
ninja-1.8.2-1-x86_64           92.2 KiB  1844K/s 00:00 [#############################] 100%
(358/358) checking keys in keyring                      [#############################] 100%
(358/358) checking package integrity                    [#############################] 100%

Here's the important bit. Usta only be three keyless Pomozovs. They seem to be breeding. 5 keyless Pomozovs today.

error: fuse-common: signature from "Anatol Pomozov <anatol.pomozov@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/fuse-common-3.2.0-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: fuse2: signature from "Anatol Pomozov <anatol.pomozov@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/fuse2-2.9.7-4-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: gdb-common: signature from "Anatol Pomozov <anatol.pomozov@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/gdb-common-8.0.1-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: gdb: signature from "Anatol Pomozov <anatol.pomozov@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/gdb-8.0.1-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: ninja: signature from "Anatol Pomozov <anatol.pomozov@gmail.com>" is unknown trust
:: File /var/cache/pacman/pkg/ninja-1.8.2-1-x86_64.pkg.tar.xz 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.

How can I bypass Pomozov? Uninstall ninja and move on? I can wait that extra few seconds for a slower compiler if I must. Or maybe theres a setting in pacman to just not list keyless Pomozovs.

I don't think pacman or anything else need it and am guessing the gdb update is only for it's usage with ninja so would disappear as well, but as there's no major hurry, I can wait just to be sure. Best plan is to ask my stupid question.and get them updates in a day or two. Might even learn something.

Thanx for suggestions.

Offline

#2 2017-09-19 01:54:34

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: bad keys stopping my update. Easy fix?

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code and update your keyring.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2017-09-19 02:32:30

circleface
Member
Registered: 2012-05-26
Posts: 639

Re: bad keys stopping my update. Easy fix?

See https://bbs.archlinux.org/viewtopic.php?id=230062 for the same problem, and do what Jason said here.  Updating the keyring should pull in the proper key.

Offline

#4 2017-09-19 03:23:39

Barkester
Member
Registered: 2017-07-01
Posts: 28

Re: bad keys stopping my update. Easy fix?

Sorry 'bout the code tag thing. Never knew such an app existed.

Thanx for the fix. The Pomozovs are gone.

Too bad I hadn't searched  Pomozov as I woulda saved you the trouble. Was in a world of ninja results. I'm searching the email name first next time. The other post is better.

Offline

Board footer

Powered by FluxBB