(solved)Keyring problem after install

Please report any bugs you find in AL here.

One bug per thread please.

Moderator: Founder

(solved)Keyring problem after install

PostPosted by blaze » Sun Apr 09, 2017 6:25 pm

This have happened after several installs with abif. When trying to upgrade first time after install pacman complains about missing signing keys.

Code: Select all
[blaze@blabz ~]$ sudo pacman -Syy
[sudo] password for blaze:
:: Synchronising package databases...
 core                     124.3 KiB   547K/s 00:00 [----------------------] 100%
 extra                   1680.1 KiB   596K/s 00:03 [----------------------] 100%
 community                  3.8 MiB   596K/s 00:07 [----------------------] 100%
 multilib                 176.2 KiB   539K/s 00:00 [----------------------] 100%
 archlabs_repo             10.2 KiB   256K/s 00:00 [----------------------] 100%
[blaze@blabz ~]$ sudo pacman -Syu
:: Synchronising package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 archlabs_repo is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) libdrm-2.4.77-1

Total Download Size:   0.22 MiB
Total Installed Size:  0.79 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 libdrm-2.4.77-1-x86_64   225.4 KiB   573K/s 00:00 [----------------------] 100%
(1/1) checking keys in keyring                     [----------------------] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: key "06096A6AD1CEDDAC" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (could not find or read file)
Errors occurred, no packages were upgraded.
Last edited by blaze on Mon Apr 10, 2017 7:43 pm, edited 2 times in total.
Duck & Cover!!! ARCHLabs is blazing!
User avatar
blaze
 
Posts: 210
Joined: Sat Mar 04, 2017 3:27 am
Running Release: 4.1

Re: keyring problem after install

PostPosted by blaze » Sun Apr 09, 2017 6:36 pm

Okay, since I do not know what I am doing I went ahead after some reading of the Arch wiki. The result is presented here;

Code: Select all
[blaze@blabz ~]$ sudo pacman-key --init
[sudo] password for blaze:
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
gpg: Generating pacman keyring master key...
gpg: key EF9EC25B9BBA87D1 marked as ultimately trusted
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/9EB9218F312EAE6F01B3513BEF9EC25B9BBA87D1.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
[blaze@blabz ~]$ sudo pacman-key --populate archlinux
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   5  signed:  72  trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2  valid:  70  signed:  10  trust: 70-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2017-09-07
[blaze@blabz ~]$ sudo pacman -Syy
:: Synchronising package databases...
 core                     124.3 KiB   555K/s 00:00 [----------------------] 100%
 extra                   1680.1 KiB   595K/s 00:03 [----------------------] 100%
 community                  3.8 MiB   583K/s 00:07 [----------------------] 100%
 multilib                 176.2 KiB   222K/s 00:01 [----------------------] 100%
 archlabs_repo             10.2 KiB   603K/s 00:00 [----------------------] 100%
[blaze@blabz ~]$ sudo pacman -Syu
:: Synchronising package databases...
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
 archlabs_repo is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) libdrm-2.4.77-1

Total Installed Size:  0.79 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
(1/1) loading package files                        [----------------------] 100%
(1/1) checking for file conflicts                  [----------------------] 100%
:: Processing package changes...
(1/1) upgrading libdrm                             [----------------------] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[blaze@blabz ~]$ sudo pacman -S geany
resolving dependencies...
looking for conflicting packages...

Packages (1) geany-1.30-1

Total Installed Size:  11.97 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                     [----------------------] 100%
(1/1) checking package integrity                   [----------------------] 100%
(1/1) loading package files                        [----------------------] 100%
(1/1) checking for file conflicts                  [----------------------] 100%
:: Processing package changes...
(1/1) installing geany                             [----------------------] 100%
Optional dependencies for geany
    geany-plugins: various extra features
    vte: terminal support [installed]
    python2 [installed]
:: Running post-transaction hooks...
(1/3) Updating icon theme caches...
(2/3) Arming ConditionNeedsUpdate...
(3/3) Updating the desktop file MIME type cache...


It seems that I got it working. Can someone of you who know what you are doing please make a quality check of it, so hopfully I can mark it as solved. :)
Duck & Cover!!! ARCHLabs is blazing!
User avatar
blaze
 
Posts: 210
Joined: Sat Mar 04, 2017 3:27 am
Running Release: 4.1


Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 0 guests