Error required key missing from keyring

Hi,
  • Index
  • » Pacman & Package Upgrade Issues
  • » pacman required key missing from keyring

#1 2014-10-01 10:24:45

dkorzhevin
Member
From: Kiev, Ukraine
Registered: 2010-04-23
Posts: 61

pacman required key missing from keyring

Hi,

I’m trying to upgrade my system, and can’t proceed because of next errors:

:: Proceed with installation? [Y/n] y
(583/583) checking keys in keyring                                                                                  [#####################################################################] 100%
downloading required keys...
:: Import PGP key 1024D/, "Fabio Castelli <muflone@vbsimple.net>", created: 2009-07-04? [Y/n] Y
error: key "Fabio Castelli <muflone@vbsimple.net>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

#3 2014-10-01 17:50:09

dkorzhevin
Member
From: Kiev, Ukraine
Registered: 2010-04-23
Posts: 61

Re: pacman required key missing from keyring

Thank you. I reinstalled package archlinux-keyring and now my problem solved.

#4 2014-10-01 18:38:58

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 27,833
Website

Re: pacman required key missing from keyring

Please remember to mark the thread as SOLVED.

«UNIX is simple and coherent…» — Dennis Ritchie, «GNU’s Not UNIX» —  Richard Stallman

#5 2016-09-10 08:31:14

itxdm
Member
Registered: 2016-09-10
Posts: 1

Re: pacman required key missing from keyring

in fact , when u meet this queation..

just need check the error..forexpam,it say’s not meet keys..

pacman-key —init
pacman-key —populate
pacman-key —refresh-keys
pacman -Sy archlinux-keyring

do then…enough!

Источник

Arseny Zinchenko

A couple of days ago I got an additional laptop to take it on meetings.

As it will be used rarely and not as my main laptop – I decided to install Manjaro Linux there instead of usual Arch Linux – to take a look at the Manjaro itself and because don’t want to spend time with Arch configuration on a laptop, which be used even not each day.

After Manjaro installation (well – much easier than Arch, of course) I started the system upgrade, and…: 

[setevoy@setevoy-asus-laptop ~]$ sudo pacman -Syu
...
:: Proceed with installation? [Y/n]  
(413/413) checking keys in keyring                                                                                                             [] 100%
downloading required keys...
:: Import PGP key 256E/C7E7849466FE2358343588377258734B41C31549, "David Runge <dvzrv@archlinux.org>", created: 2019-10-01? [Y/n] y
error: key "David Runge <dvzrv@archlinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

Well… Okay.

The first upgrade on o system with outdated packages, expected issues – no problem at all.

Do not perform the actions described below until you’ll read the actual reason.

Update archlinux-keyring

The first idea was to upgrade the archlinux-keyring util and it will update its keys: 

$ sudo pacman -Sy archlinux-keyring
...
warning: archlinux-keyring-20191018-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) archlinux-keyring-20191018-1
...
-> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
==> Updating trust database...
gpg: next trustdb check due at 2020-01-22
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

But this didn’t help.

pacman-key --refresh-keys

Okay, let’s try update keys directly in the pacman-key‘s database: 

[setevoy@setevoy-asus-laptop ~]$ sudo pacman-key --refresh-keys
...
gpg: Total number processed: 133
gpg:              unchanged: 66
gpg:           new user IDs: 3
gpg:            new subkeys: 1
gpg:         new signatures: 1172
...
gpg: next trustdb check due at 2020-01-22

Nah, still something is wrong here: 

[setevoy@setevoy-asus-laptop ~]$ pacman-key --list-sigs | grep Runge
gpg: Note: trustdb not writable
gpg: key E5BB298470AD4E41 was created 53 days in the future (time warp or clock problem)
gpg: key 6D42BDD116E0068F was created 11 days in the future (time warp or clock problem)
gpg: key 6D42BDD116E0068F was created 11 days in the future (time warp or clock problem)
gpg: key E5BB298470AD4E41 was created 53 days in the future (time warp or clock problem)
sig          54C28F4FF5A1A949 2014-10-06  David Runge <dave@sleepmap.de>
uid          [  full  ] David Runge <dave@sleepmap.de>
sig 3        54C28F4FF5A1A949 2017-05-07  David Runge <dave@sleepmap.de>
sig 3        54C28F4FF5A1A949 2015-01-04  David Runge <dave@sleepmap.de>
uid           [  full  ] David Runge <dave@c-base.org>
sig 3        54C28F4FF5A1A949 2017-05-07  David Runge <dave@sleepmap.de>
sig 3        54C28F4FF5A1A949 2015-10-20  David Runge <dave@sleepmap.de>
uid           [  full  ] David Runge <runge@pool.math.tu-berlin.de>
sig 3        54C28F4FF5A1A949 2017-05-07  David Runge <dave@sleepmap.de>
sig 3        54C28F4FF5A1A949 2014-10-03  David Runge <dave@sleepmap.de>
uid           [  full  ] David Runge <david.runge@campus.tu-berlin.de>
sig 3        54C28F4FF5A1A949 2017-05-07  David Runge <dave@sleepmap.de>
sig 3        54C28F4FF5A1A949 2014-10-03  David Runge <dave@sleepmap.de>
sig          54C28F4FF5A1A949 2017-05-07  David Runge <dave@sleepmap.de>

At least – the developer’s mailbox is not the same as in the error.

there is a hint, but I didn’t notice it

Removing /etc/pacman.d/gnupg

The next thing I did a try – to fully drop (backup, of course, not just delete) pacman‘s GPG database to re-initial it from scratch: 

[setevoy@setevoy-asus-laptop ~]$ ls -l /etc/pacman.d/gnupg
total 6276
drwx------ 2 root root    4096 жов 21  2017 crls.d
-rw-r--r-- 1 root root      17 лис  8  2018 gpg-agent.conf
-rw-r--r-- 1 root root     114 жов 24  2015 gpg.conf
drwx------ 2 root root    4096 жов 24  2015 openpgp-revocs.d
...
-rw-r--r-- 1 root root   18920 сер 18 12:28 trustdb.gpg

Move it to backups: 

[setevoy@setevoy-asus-laptop ~]$ mkdir ~/Backups
[setevoy@setevoy-asus-laptop ~]$ sudo mv /etc/pacman.d/gnupg Backups/

Run initialization: 

[setevoy@setevoy-asus-laptop ~]$ sudo pacman-key --init
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 FBADB7D2586D4A2F 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/7F47A1EC7C894F56DD6F9E18FBADB7D2586D4A2F.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

Get keys: 

[setevoy@setevoy-asus-laptop ~]$ sudo pacman-key --populate
==> Appending keys from archlinux.gpg...
...

Let’s even update them: 

[setevoy@setevoy-asus-laptop ~]$ sudo pacman-key --refresh-keys
gpg: refreshing 132 keys from hkps://hkps.pool.sks-keyservers.net
...

Run the OS upgrade again: 

[setevoy@setevoy-asus-laptop ~]$ sudo pacman -Syu
...
downloading required keys...
:: Import PGP key 256E/C7E7849466FE2358343588377258734B41C31549, "David Runge <dvzrv@archlinux.org>", created: 2019-10-01? [Y/n]
error: key "David Runge <dvzrv@archlinux.org>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

sd78dfv:?%67sdc!!!

pacman-key --recv-keys – a direct key’s import

Then I went to look for the key directly in the https://www.archlinux.org/master-keys database:

| David Runge | 0x41C31549 | Yes |

And try to import it directly: 

[setevoy-asus-laptop setevoy]# pacman-key --recv-keys dvzrv@archlinux.org
gpg: key E5BB298470AD4E41 was created 53 days in the future (time warp or clock problem)
gpg: key 7258734B41C31549: 2 duplicate signatures removed
gpg: key 7258734B41C31549: 4 signatures not checked due to missing keys
gpg: key 7258734B41C31549: 2 signatures reordered
gpg: key 7258734B41C31549 was created 44 days in the future (time warp or clock problem)
gpg: key 7258734B41C31549 was created 44 days in the future (time warp or clock problem)
gpg: key 7258734B41C31549 was created 44 days in the future (time warp or clock problem)
gpg: key 7258734B41C31549 was created 44 days in the future (time warp or clock problem)
gpg: key 7258734B41C31549: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg:           w/o user IDs: 1
==> ERROR: Remote key not fetched correctly from keyserver.

Eeerrr….

gpg: key 7258734B41C31549 was created 44 days in the future (time warp or clock problem)

44 days in the future – WHAT?

The real cause and solution

Check the date on the operating system now: 

[setevoy-asus-laptop setevoy]# date
sun, 18 серпня 2019 12:47:28 +0300

And by using hwclock to heck hardware’s time settings: 

[setevoy-asus-laptop setevoy]# hwclock --show
2019-08-18 12:47:55.575491+03:00
Set the real time at this moment:
[setevoy-asus-laptop setevoy]# timedatectl set-time "2019-11-24 09:56:00"
[setevoy-asus-laptop setevoy]# hwclock --show
2019-11-24 09:56:03.404766+02:00

Repeat upgrade: 

[setevoy@setevoy-asus-laptop ~]$ sudo pacman -Syu
...
(413/413) checking keys in keyring                                                                                                             [] 100%
downloading required keys...
:: Import PGP key 256E/C7E7849466FE2358343588377258734B41C31549, "David Runge <dvzrv@archlinux.org>", created: 2019-10-01? [Y/n]
(413/413) checking package integrity
...

And everything is working now.

Done.

Similar posts

  • 05/08/2017 Arch Linux: keyserver receive failed: No keyserver available и ручной импорт ключа
  • 05/06/2017 Arch Linux: запускаем Diablo 2
  • 03/29/2017 Arch: Skype – звук и микрофон
  • 03/16/2017 Arch: апплет батареи для ноутбука
Источник


0

1 

[user@arch ~]# pacman -Syy archlinux-keyring

error: key "6D42BDD116E0068F" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

[user@arch ~]# pacman-key --populate archlinux         
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C...
  -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F...
  -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
  -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
  -> Disabling key 5559BC1A32B8F76B3FCCD9555FA5E5544F010D48...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
  -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
  -> Disabling key 5A2257D19FF7E1E0E415968CE62F853100F0D0F0...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
  -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
  -> Disabling key 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A...
  -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
  -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
  -> Disabling key 5357F3B111688D88C1D88119FCF2CB179205AC90...
  -> Disabling key FB871F0131FEA4FB5A9192B4C8880A6406361833...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 40776A5221EF5AD468A4906D42A1DB15EC133BAD...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
==> Updating trust database...
gpg: next trustdb check due at 2021-10-23

[user@arch ~]# pacman-key --refresh-keys
gpg: refreshing 114 keys from hkps://hkps.pool.sks-keyservers.net
gpg: keyserver refresh failed: No name
==> ERROR: A specified local key could not be updated from a keyserver.
Источник

Traceback (most recent call last): File «/usr/bin/archinstall», line 8, in <module> sys.exit(run_as_a_module()) File «/usr/lib/python3.10/site-packages/archinstall/init.py», line 281, in run_as_a_module File «/usr/lib/python3.10/site-packages/archinstall/lib/profiles.py», line 195, in execute script.execute() self.spec.loader.exec_module(sys.modules[self.namespace]) File «<frozen importlib._bootstrap_external>», line 883, in exec_module File «<frozen importlib._bootstrap>», line 241, in call_with_frames_removed File «/usr/lib/python3.10/site-packages/archinstall/examples/guided.py», line 286, in <module> if not archinstall.update_keyring(): line 46, in update_keyring File «/usr/lib/python3.18/site-packages/archinstall/lib/networking.py», if run_pacman («-Sy —noconfirm archlinux-keyring»). exit_code == 8: File «/usr/lib/python3.10/site-packages/archinstall/lib/pacman.py», return SysCommand (f’ (default_cmd) (args}’) line 28, in run_pacman File «/usr/lib/python3.10/site-packages/archinstall/lib/general.py», line 416, in init self.create_session() File «/usr/lib/python3. 18/site-packages/archinstall/lib/general.py», with SysCommandWorker ( line 467, in create_session File «/usr/lib/python3.18/site-packages/archinstall/lib/general.py», line 273, in exit__ archinstall.lib.exceptions. SysCallError: [‘/usr/bin/pacman’, ‘-Sy’, ‘—noconfirm’, ‘archlinux-keyring’] exited with abnormal exit code [256]: b’B/s 08:02 [###— raise SysCallError (f»(self.cmd) exited with abnormal exit code [(self.exit_code) 1: (self._trace_log[-588:1)», self.exit_code) 18%r archlinux-keyrin… 1181.8 KiB 2.18 MiB/s 88:88 [⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀##] 188Zrx1b[1E(8/1) checking keys in keyring ——] -] 8%r(1/1) checking keys in keyring keuring is not writablernerror: required key missing from keyringrnerror: failed to commit transaction (unexpected error)rnErrors occurred, no packages ere upgraded. rnx1b[?25h 1 root@archiso

[************##########] 188%rrndownloading required keys…rnerror: :(

Источник

Fix updating issue with missing PGP key on ArchLinux

  • Christophe Vanlancker

Jun 10, 2020
• 3 min read

Can't import PGP key ArchLinux

This morning I tried updating my ArchLinux server at home and stumbled into an issue where it wasn’t able to find the PGP public key of one of the developers:

[root@shuttle ~]# 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 (33) archlinux-keyring-20200603-1  bison-3.6.3-1  ca-certificates-mozilla-3.53-1  conmon-1:2.0.17-1  cryptsetup-2.3.3-1  dbus-1.12.18-1  device-mapper-2.02.187-3  git-2.27.0-1
              glib-networking-2.64.3-2  gnupg-2.2.20-4  gnutls-3.6.14-1  go-2:1.14.4-1  iana-etc-20200601-1  iproute2-5.7.0-1  iptables-1:1.8.5-2  libgpg-error-1.38-1  libksba-1.4.0-1  libnghttp2-1.41.0-1
              linux-5.6.15.arch1-1  linux-firmware-20200519.8ba6fa6-1  lvm2-2.02.187-3  openssh-8.3p1-1  pacman-mirrorlist-20200606-1  pciutils-3.7.0-1  perl-5.30.3-1  pkgconf-1.7.3-1
              python-setuptools-1:47.1.1-1  runc-1.0.0rc90-1  slirp4netns-1.1.1-1  sqlite-3.32.2-1  systemd-245.6-4  systemd-libs-245.6-4  systemd-sysvcompat-245.6-4

Total Installed Size:  1294.85 MiB
Net Upgrade Size:        28.49 MiB

:: Proceed with installation? [Y/n] Y
(33/33) checking keys in keyring                                                                                            [##########################################################################] 100%
downloading required keys...
:: Import PGP key 3B94A80E50A477C7, "Jan Alexander Steffens (heftig) <heftig@archlinux.org>"? [Y/n] Y
error: key "3B94A80E50A477C7" could not be looked up remotely
:: Import PGP key 3B94A80E50A477C7, "Jan Alexander Steffens (heftig) <heftig@archlinux.org>"? [Y/n] Y
error: key "3B94A80E50A477C7" could not be looked up remotely
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

The key 3B94A80E50A477C7 wasn’t found anywhere.

The fix is to first update the archlinux-keyring package first which contained the key, and then proceed with the normal update.

[root@shuttle ~]# pacman -S archlinux-keyring
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20200603-1

Total Installed Size:  1.23 MiB
Net Upgrade Size:      0.01 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%
(1/1) checking available disk space                                                                                         [##########################################################################] 100%
:: Processing package changes...
(1/1) upgrading archlinux-keyring                                                                                           [##########################################################################] 100%
==> Appending keys from archlinux.gpg...
==> Locally signing trusted keys in keyring...
  -> Locally signing key D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C...
  -> Locally signing key DDB867B92AA789C165EEFA799B729B06A680C281...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
==> Disabling revoked keys in keyring...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F...
  -> Disabling key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Disabling key 39F880E50E49A4D11341E8F939E4F17F295AFBF4...
  -> Disabling key 8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA...
  -> Disabling key 5559BC1A32B8F76B3FCCD9555FA5E5544F010D48...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 07DFD3A0BC213FA12EDC217559B3122E2FA915EC...
  -> Disabling key 4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD...
  -> Disabling key 5A2257D19FF7E1E0E415968CE62F853100F0D0F0...
  -> Disabling key D921CABED130A5690EF1896E81AF739EC0711BF1...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 5696C003B0854206450C8E5BE613C09CB4440678...
  -> Disabling key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Disabling key 8CF934E339CAD8ABF342E822E711306E3C4F88BC...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 5E7585ADFF106BFFBBA319DC654B877A0864983E...
  -> Disabling key 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A...
  -> Disabling key 40440DC037C05620984379A6761FAD69BA06C6A9...
  -> Disabling key 34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
  -> Disabling key 5357F3B111688D88C1D88119FCF2CB179205AC90...
  -> Disabling key 4D913AECD81726D9A6C74F0ADA6426DD215B37AD...
  -> Disabling key FB871F0131FEA4FB5A9192B4C8880A6406361833...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key B1F2C889CB2CCB2ADA36D963097D629E437520BD...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 76B4192E902C0A52642C63C273B8ED52F1D357C1...
  -> Disabling key 40776A5221EF5AD468A4906D42A1DB15EC133BAD...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key 44D4A033AC140143927397D47EFD567D4C7EA887...
==> Updating trust database...
gpg: next trustdb check due at 2020-10-17
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Источник

#
8 лет, 10 месяцев назад

AiNo07 avatar

Темы:

14

Сообщения:

79

Участник с: 15 марта 2014

Не получается установить систему! После скачки пакетов встаёт на ошибке вида:

downoading required keys...
:::Import PGP key 4096R/753E0F1F, ''Anatol Pomozov <[email protected]>'', created:2014-02-04? [Y/n]
error: key ''Anatol Pomozov <[email protected]>''
error: required key missing from keyring
error: failed to commit transaction (unexperted error)
Errors occyred? no packages were upgraded.
==> ERROR: Failed to install packages to new root

Salko

#
8 лет, 10 месяцев назад

Темы:

26

Сообщения:

138

Участник с: 05 февраля 2014

заблокирован

 https://wiki.archlinux.org/index.php/Pacman-key#Cannot_import_keys

AiNo07

#
8 лет, 10 месяцев назад

AiNo07 avatar

Темы:

14

Сообщения:

79

Участник с: 15 марта 2014

Прошу прощения ребят! Дата в bios была не верная 06м.03д.2014г. )…

AiNo07

#
8 лет, 10 месяцев назад

AiNo07 avatar

Темы:

14

Сообщения:

79

Участник с: 15 марта 2014

Система установилась, но вот grub что-то явно делает не так, сообщение вида: error such device: 

183bdb4c-8ead-4ca5-bd7d-fbc6a2efief5.
Enterind rescue mode...
grub rescue>

Если дать команду:

ls
(hd0)

,

set prefix=(hd0)/boot/grub
set root=(hd0)
error: unknown filesystem

что за???

Jisatsu

#
8 лет, 10 месяцев назад

Jisatsu avatar

Темы:

17

Сообщения:

389

Участник с: 14 июня 2013

В fstab диски прикручены по UUID? Перепишите на обычный /dev/sdXX.

Вот тут обсуждалась ошибка монтирования.

Keep it simple, stupid!

AiNo07

#
8 лет, 10 месяцев назад

AiNo07 avatar

Темы:

14

Сообщения:

79

Участник с: 15 марта 2014

Там ничего вразумительного не нашёл! Мне вообще не ясно почему такое произошло, ведь делалось-то всё по инструкции! (…

Salko

#
8 лет, 10 месяцев назад

Темы:

26

Сообщения:

138

Участник с: 05 февраля 2014

заблокирован

 Ну у меня тоже были некоторые расхождения с инструкцией..
У меня так:

#
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# UUID=[hide]
/dev/sda1       /               ext4            rw,relatime     0 1

# UUID=[hide]
/dev/sda2       none            swap            defaults        0 0

AiNo07

#
8 лет, 10 месяцев назад

AiNo07 avatar

Темы:

14

Сообщения:

79

Участник с: 15 марта 2014

Мне просто не ясно что теперь конкретно делать, инфы тьма — запутался! (
Сейчас при запмуске GRUB даёт такой выхлоп: 

GRUB loading.
Welcome to GRUB!
error: no such device: 183bdb4c-8ead-4ca5-bd7d-fbc6a2efief5.
Entering rescue mode...
grub rescue> ls
(hd0)

Что дальше?

Salko

#
8 лет, 10 месяцев назад

Темы:

26

Сообщения:

138

Участник с: 05 февраля 2014

заблокирован

 fstab изменил?

# grub-mkconfig -o /boot/grub/grub.cfg

сначала кажется придется поменять пару строк в самом конфиге grub, чтобы дальше смог загрузиться. у меня так было )

AiNo07

#
8 лет, 10 месяцев назад

AiNo07 avatar

Темы:

14

Сообщения:

79

Участник с: 15 марта 2014

На эту команду 

# grub-mkconfig -o /boot/grub/grub.cfg

Пишет 

Unknown command 'grub-mkconfig'
Источник

Понравилась статья? Поделить с друзьями:
  • Error required internal cmake variable not set cmake may not be built correctly
  • Error reported here must be corrected before the service can be started
  • Error reported by freeproxy перевод
  • Error report warface trunk has stopped working
  • Error report unknown command