Pacman / Pamac update & keyring issues for nemesis 3.5

Arch based Porteus community project
Post Reply
User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Pacman / Pamac update & keyring issues for nemesis 3.5

Post#1 by istinnjazz » 19 Jun 2016, 15:19

Updated post, major rewrite, with more specific instructions on Pacman / Pamac update
(09/07/2016)


UPDATE TO PACMAN 5 and PAMAC 4.1 for NEMESIS 3.5

I have decided to boot again from a new totally clean system to see, what is going to happen during updates, so everyone can do it and maybe help developers isolate issues for their fixes.

So here is the solution (posted from the new clean system):

Boot totally clean.
Do not create savefile yet, if you want xzm from pman-setup. Pman-setup could save its contents in the savefile if found (a guess), but I have never tried it.
So on this solution I will create one xzm from pman and then I will update pacman at the savefile level.
There could be alternative ways but I want the xzm to be available for any other boot options, with different savefiles etc. No need to create it again. A personal choice.

Code: Select all

guest ~ $ su
Password: 
root /home/guest # pacman --version

 .--.                  Pacman v4.2.1 - libalpm v9.0.1
/ _.-' .-.  .-.  .-.   Copyright (C) 2006-2014 Pacman Development Team
\  '-. '-'  '-'  '-'   Copyright (C) 2002-2006 Judd Vinet
 '--'
                       This program may be freely redistributed under
                       the terms of the GNU General Public License.
This is the very first fundamental step, setup-pman script, it will create pacman-settings.xzm to your modules folder:

Code: Select all

root /home/guest # setup-pman
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 571B1ADE marked as ultimately trusted
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: Done
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from archlinux.gpg...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Locally signing trusted keys in keyring...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
  -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   5  signed:  64  trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2  valid:  64  signed:   5  trust: 64-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-10-19
==> Appending keys from manjaro.gpg...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   5  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   5  signed:  64  trust: 0-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2  valid:  64  signed:   5  trust: 64-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-10-19
==> Locally signing trusted keys in keyring...
  -> Locally signing key 7C89F4D439B2BFACF425107B62443D89B35859F8...
  -> Locally signing key 5A97ED6B72418199F0C22B23137C934B5DCB998E...
  -> Locally signing key B4663188A692DB1E45A98EE95BD96CC4247B52CC...
  -> Locally signing key 35B4FF23EA9477582C2A0AF12B80869C5C0102A6...
  -> Locally signing key 1E7908935AAB9A00D6B47503363DFFFD59152F77...
  -> Locally signing key 77DC01C9971AC3C39A0626F72C089F09AC97B894...
  -> Locally signing key 74C2F2CC05A0AB7D859839938934292D604F8BA2...
  -> Locally signing key 39F0EC1AE50B37E5F3196F09DAD3B211663CA268...
  -> Locally signing key E4CDFE50A2DA85D58C8A8C70CAA6A59611C7F07E...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabling key FAA6840E8C3FC7F89BEE0DC8AC7AB10BCB6CDD17...
  -> Disabling key 540DE7083B89314CF70EA6F0C1B1AD0DA80EBF3E...
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:  14  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  14  signed:  64  trust: 0-, 0q, 0n, 14m, 0f, 0u
gpg: depth: 2  valid:  64  signed:   5  trust: 64-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-10-19

 No package servers detected. 
 Please type the closest country:  

Africa	   Chile    Germany    Italy	    Portugal  Taiwan
Australia  China    Greece     Japan	    Romania   Turkey
Belgium    Ecuador  Indonesia  Netherlands  Russia    United_Kingdom
Brasil	   France   Ireland    Philippines  Sweden    United_States

> Greece
 Generating fastest mirror list ... 
:: Querying servers, this may take some time...
Greece
-> 0.607 http://ftp.cc.uoc.gr/mirrors/linux/manjaro/stable/$repo/$arch
:: Generated and saved '/etc/pacman.d/mirrorlist' mirrorlist.

 Updating database ... 

==> Pre-4.2 database format detected - upgrading...
:: Synchronizing package databases...
 core                     135.5 KiB   243K/s 00:01 [######################] 100%
 extra                   1898.8 KiB  64.3K/s 00:30 [######################] 100%
 community                  3.8 MiB  1450K/s 00:03 [######################] 100%
 multilib                 187.5 KiB   852K/s 00:00 [######################] 100%
 Updating certificates /// 

df: ‘/porteus’: No such file or directory
 Changes are not on a real file system. 


 It seems you are not saving your changes. 

Would you like to create a module from your settings? [y/n]y
/tmp
Parallel mksquashfs: Using 2 processors
Creating 4.0 filesystem on /tmp/pacman-settings.xzm, block size 262144.
[=================================================================-] 35/35 100%

Exportable Squashfs 4.0 filesystem, xz compressed, data block size 262144
	compressed data, compressed metadata, compressed fragments, compressed xattrs
	duplicates are removed
Filesystem size 6657.65 Kbytes (6.50 Mbytes)
	99.41% of uncompressed filesystem size (6697.06 Kbytes)
Inode table size 374 bytes (0.37 Kbytes)
	41.65% of uncompressed inode table size (898 bytes)
Directory table size 462 bytes (0.45 Kbytes)
	75.00% of uncompressed directory table size (616 bytes)
Number of duplicate files found 2
Number of inodes 25
Number of files 13
Number of fragments 2
Number of symbolic links  0
Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 1
Number of directories 11
Number of ids (unique uids + gids) 1
Number of uids 1
	root (0)
Number of gids 1
	root (0)

6.6M	/tmp/pacman-settings.xzm

/tmp/pacman-settings.xzm was moved to your modules directory.
This means that changes will persist at next boot.

NOW IT IS TIME TO SETUP YOUR SAVEFILE:
Reboot with boot option for savefile activation

Code: Select all

pacman -Syy
if previous setup was executed e,g, a day ago, you have to re update databases. Pacman current databases are being saved by pman-setup anyway on execution and packed in xzm module. But new databases if any, will overlay pmac-setup again from now on, on the savefile level.

The first issue: pacman

Code: Select all

root /home/guest # pacman -S pacman
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...

Packages (2) archlinux-keyring-20160402-1  manjaro-keyring-20160527-1

Total Download Size:   0.62 MiB
Total Installed Size:  0.86 MiB
Net Upgrade Size:      0.11 MiB

:: Proceed with installation? [Y/n] n

resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<4.3
:: pamac: requires pacman<4.3
CAUTION: package-query belongs to an external repository

more info: https://bbs.archlinux.org/viewtopic.php?id=208306

Set a new unofficial repository to pacman configuration related to AUR helper "yaourt" https://afur.archlinux.fr/
This repository includes "package-query" witch is an unofficial package.
Only then pacman commands should work for the "package-query" package (you can alternatively install it from AUR if you can, I am not sure if it will work this way)

usefull links:
https://wiki.archlinux.org/index.php/Pa ... icial_keys
https://wiki.archlinux.org/index.php/Un ... positories
https://bbs.archlinux.org/viewtopic.php?id=144614

So, you have to edit etc/pacman.conf and add:

Code: Select all

[archlinuxfr]
#SigLevel = Optional TrustAll
SigLevel = PackageRequired
Server = http://repo.archlinux.fr/$arch
(uncomment and use SigLevel = Optional TrustAll if you have problems with keys)
Save it and update databases again:

Code: Select all

pacman -Syy
You will notice the new entry "archlinuxfr":

Code: Select all

root /home/guest # pacman -Syy
:: Synchronizing package databases...
 core                     135.5 KiB   316K/s 00:00 [######################] 100%
 extra                   1898.8 KiB  1316K/s 00:01 [######################] 100%
 community                  3.8 MiB   692K/s 00:06 [######################] 100%
 multilib                 187.5 KiB   445K/s 00:00 [######################] 100%
 archlinuxfr               11.3 KiB   365K/s 00:00 [######################] 100%
First attempt to update package-query:
CAUTION:This is where the keyring conflict might occur if executed with differences in timeline
Then you may have to delete conflicting packages as stated in keyring issues topic.
Next command will give you errors and probably trigger the keyring issue (RESOLVED @ 2nd post):

Code: Select all

pacman -S package-query
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...

Packages (2) archlinux-keyring-20160402-1  manjaro-keyring-20160527-1

Total Download Size:   0.62 MiB
Total Installed Size:  0.86 MiB
Net Upgrade Size:      0.11 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
 archlinux-keyring-2...   576.7 KiB   704K/s 00:01 [######################] 100%
 manjaro-keyring-201...    59.0 KiB   476K/s 00:00 [######################] 100%
(2/2) checking keys in keyring                     [######################] 100%
(2/2) checking package integrity                   [######################] 100%
(2/2) loading package files                        [######################] 100%
(2/2) checking for file conflicts                  [######################] 100%
(2/2) checking available disk space                [######################] 100%
(1/2) upgrading archlinux-keyring                  [######################] 100%
==> Appending keys from archlinux.gpg...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:  14  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  14  signed:  66  trust: 0-, 0q, 0n, 14m, 0f, 0u
gpg: depth: 2  valid:  66  signed:   7  trust: 66-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-10-19
==> Locally signing trusted keys in keyring...
  -> Locally signing key 0E8B644079F599DFC1DDC3973348882F6AC6A4C2...
  -> Locally signing key 684148BB25B49E986A4944C55184252D824B18E8...
  -> Locally signing key 91FFE0700E80619CEB73235CA88E23E377514E00...
  -> Locally signing key 44D4A033AC140143927397D47EFD567D4C7EA887...
  -> Locally signing key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0...
  -> Locally signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7...
==> Importing owner trust values...
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabling key F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6...
  -> Disabling key 7FA647CD89891DEDC060287BB9113D1ED21E1A55...
  -> Disabling key D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50...
  -> Disabling key BC1FBE4D2826A0B51E47ED62E2539214C6C11350...
  -> Disabling key 9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5...
  -> Disabling key 4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2...
  -> Disabling key 63F395DE2D6398BBE458F281F2DBB4931985A992...
  -> Disabling key 0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196...
  -> Disabling key 8F76BEEA0289F9E1D3E229C05F946DED983D4366...
  -> Disabling key 66BD74A036D522F51DD70A3C7F2A16726521E06D...
  -> Disabling key 81D7F8241DB38BC759C80FCE3A726C6170E80477...
  -> Disabling key E7210A59715F6940CF9A4E36A001876699AD6E84...
==> Updating trust database...
gpg: next trustdb check due at 2016-10-19
(2/2) upgrading manjaro-keyring                    [######################] 100%
==> Appending keys from manjaro.gpg...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:  15  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  15  signed:  68  trust: 0-, 0q, 0n, 15m, 0f, 0u
gpg: depth: 2  valid:  68  signed:   7  trust: 68-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-10-19
==> Locally signing trusted keys in keyring...
  -> Locally signing key 7C89F4D439B2BFACF425107B62443D89B35859F8...
  -> Locally signing key 22C903DE964E6FE321656E318DB9F8C18DF53602...
  -> Locally signing key 16DC688DF3EECC72323954237EC47C82A42D53A2...
  -> Locally signing key 5A97ED6B72418199F0C22B23137C934B5DCB998E...
  -> Locally signing key B4663188A692DB1E45A98EE95BD96CC4247B52CC...
  -> Locally signing key 2C688B52E3FC0144B7484BABE3B3F44AC45EE0AA...
  -> Locally signing key 35B4FF23EA9477582C2A0AF12B80869C5C0102A6...
  -> Locally signing key 1E7908935AAB9A00D6B47503363DFFFD59152F77...
  -> Locally signing key 77DC01C9971AC3C39A0626F72C089F09AC97B894...
  -> Locally signing key 74C2F2CC05A0AB7D859839938934292D604F8BA2...
  -> Locally signing key 39F0EC1AE50B37E5F3196F09DAD3B211663CA268...
  -> Locally signing key E4CDFE50A2DA85D58C8A8C70CAA6A59611C7F07E...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
  -> Disabling key FAA6840E8C3FC7F89BEE0DC8AC7AB10BCB6CDD17...
  -> Disabling key 540DE7083B89314CF70EA6F0C1B1AD0DA80EBF3E...
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:  18  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  18  signed:  66  trust: 0-, 0q, 0n, 18m, 0f, 0u
gpg: depth: 2  valid:  66  signed:   7  trust: 66-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2016-10-19

resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: pamac: requires pacman<4.3

The uninstall and reinstall solution:

package-query

Code: Select all

pacman -R package-query
checking dependencies...

Packages (1) package-query-1.6.2-1

Total Removed Size:  0.08 MiB

:: Do you want to remove these packages? [Y/n] y
(1/1) removing package-query                       [######################] 100%
pamac

Code: Select all

root /home/guest # pacman -R pamac
checking dependencies...

Packages (1) pamac-2.4.3-3

Total Removed Size:  2.93 MiB

:: Do you want to remove these packages? [Y/n] y
(1/1) removing pamac                               [######################] 100%
warning: /etc/pamac.conf saved as /etc/pamac.conf.pacsave
gtk-update-icon-cache: Cache file created successfully.
==> The polkit-gnome agent is no longer autostarted by default
    except in GNOME Flashback.
    For Xfce, LXDE etc., lxsession is the suggested lightweight alternative.
    See https://wiki.archlinux.org/index.php/Polkit#Authentication_agents
    for more details.

Install them all now:

Code: Select all

root /home/guest # pacman -S package-query pamac
resolving dependencies...
looking for conflicting packages...

Packages (3) pacman-5.0.1-4  package-query-1.8-1  pamac-4.1.0-2

Total Download Size:   1.06 MiB
Total Installed Size:  7.46 MiB
Net Upgrade Size:      3.09 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages ...
 pacman-5.0.1-4-x86_64    737.1 KiB   931K/s 00:01 [######################] 100%
 package-query-1.8-1...    26.1 KiB   395K/s 00:00 [######################] 100%
 pamac-4.1.0-2-x86_64     321.1 KiB   841K/s 00:00 [######################] 100%
(3/3) checking keys in keyring                     [######################] 100%
(3/3) checking package integrity                   [######################] 100%
(3/3) loading package files                        [######################] 100%
(3/3) checking for file conflicts                  [######################] 100%
(3/3) checking available disk space                [######################] 100%
(1/3) upgrading pacman                             [######################] 100%
warning: /etc/makepkg.conf installed as /etc/makepkg.conf.pacnew
warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew
warning: directory permissions differ on /var/cache/pacman/pkg/
filesystem: 777  package: 755
(2/3) installing package-query                     [######################] 100%
(3/3) installing pamac                             [######################] 100%
==> An authentication agent is required
    Cinnamon, Deepin, GNOME, GNOME Flashback, KDE, LXDE, LXQt, MATE and Xfce
    have an authentication agent already.
    See https://wiki.archlinux.org/index.php/Polkit#Authentication_agents
    for other desktop environments.
Optional dependencies for pamac
    yaourt: needed for AUR support
yaourt (AUR helper)

Code: Select all

root /home/guest # pacman -S yaourt
resolving dependencies...
looking for conflicting packages...

Packages (1) yaourt-1.8.1-1

Total Download Size:   0.10 MiB
Total Installed Size:  0.77 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 yaourt-1.8.1-1-any       105.8 KiB   275K/s 00:00 [######################] 100%
(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) installing yaourt                            [######################] 100%
Optional dependencies for yaourt
    aurvote: vote for favorite packages from AUR
    customizepkg: automatically modify PKGBUILD during install/upgrade
    rsync: retrieve PKGBUILD from official repositories [installed]
root /home/guest # 

Code: Select all

root /home/guest # pacman --version

 .--.                  Pacman v5.0.1 - libalpm v10.0.1
/ _.-' .-.  .-.  .-.   Copyright (C) 2006-2016 Pacman Development Team
\  '-. '-'  '-'  '-'   Copyright (C) 2002-2006 Judd Vinet
 '--'
                       This program may be freely redistributed under
                       the terms of the GNU General Public License.

root /home/guest # 
Alternative way, pamac:
This update could be done also from the original pamac alone, if you try to proceed for a full update (keep in mind you need more than 2GB free savefile to complete this without possible file system corruption (see bug reports on this)
This will lead to first time update screens for keyring, pamac itself and pacman. This could also trigger keyring issues. I have done this but I do not remember the steps, but I think you can update without forcing to proceed to a full update (you can cancel(?)) or you have to deselect all packages exept those mentioned (pretty hard on pamac as there is no way for now to deselect all found updates).

from pamac.log

Code: Select all

...
[2016-05-30 23:25] 
[2016-05-30 23:25] hint: use `pacman-mirrors` to generate and update your pacman mirrorlist.
[2016-05-30 23:25] Upgraded pacman-mirrorlist (20151220-1 -> 20160423-1)
[2016-05-30 23:25] Upgraded pacman (4.2.1-4.1 -> 5.0.1-4)
[2016-05-30 23:25] Upgraded package-query (1.6.2-1 -> 1.8-1)
[2016-05-30 23:25] Upgraded pamac (2.4.3-3 -> 4.1.0-1)
Reboot and you will have a valid system, a mix of a xzm module and some files saved @ savefile image level.

For a full update procedure there are a few additional possible conflicting files and some other issues you may care about
more issues on update:
viewtopic.php?f=137&t=5382&start=255#p46302
Last edited by istinnjazz on 10 Jul 2016, 20:38, edited 22 times in total.

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Manjaro / Arch keyring update issues for nemesis 3.5

Post#2 by istinnjazz » 09 Jul 2016, 14:35

Important edit: 09/07/1016: See 1st post for a full update to pacman 5.01 and pamac 4.1 and then check if there is a keyring issue.

There could be users unable to update.
This is a partial copy of a tutorial I had created in "tutorials" category, but I think it is more obvious and useful here:

Manjaro keyring

To update anything in arch/manjaro you have to update key signatures (security for package signing), and for AUR certificates also.
There are 2 possible needed keyring packages, but I am not sure why, maybe there has to be some kind of arch repository communication somewhere, or AUR certification, I am not sure.

Code: Select all

pacman -Syy

Code: Select all

root /home/guest #
pacman -S archlinux-keyring
warning: archlinux-keyring-20160402-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) archlinux-keyring-20160402-1

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

:: Proceed with installation? [Y/n]

Code: Select all

root /home/guest #
pacman -S manjaro-keyring
warning: manjaro-keyring-20160527-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) manjaro-keyring-20160527-1

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

:: Proceed with installation? [Y/n]
You can then update keys only if necessary (e.g. repositories changed the keys)

Code: Select all

pacman-key --populate
or

Code: Select all

pacman-key --refresh-keys
for an individual signing you may also try

Code: Select all

pacman-key --init
(you have to read: https://wiki.archlinux.org/index.php/Pa ... ge_signing)

If you will use the graphical update manager, before it will install any update, it will offer this individual manjaro-keyring package for installation.
Only after this you will be able to update anything else and use package manager.

There could be a keyring package conflict
possibly because of the transsition of pacman to version 5
https://wiki.archlinux.org/index.php/Pacman

There could be a pacman error message: duplicated database entry 'manjaro-keyring' or "archlinux-keyring" and any update or package installation will fail.
You have to delete the outdated packages that reside in pacman cache directory:

Code: Select all

 ls /var/lib/pacman/local/ | grep manjaro-keyring
or

Code: Select all

 ls /var/lib/pacman/local/ | grep archlinux-keyring
possible result:

Code: Select all

manjaro-keyring-20150809-1
manjaro-keyring-20160527-1
you have to delete the outdated one from /var/lib/pacman/local/

Code: Select all

rm -rf /var/lib/pacman/local/manjaro-keyring-20150809-1
same for archlinux-keyring

After this, to use AUR you have to update certificates:

Code: Select all

Code: Select all

trust extract-compat
The first essential package you will need to update is "pacman" to version 5
see 1st post

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#3 by francois » 17 Jul 2016, 12:31

0. created on vbox three partitions: sda1 fat32, sda3 ext4 and sda3 swap
1. clean system installed from nemesis iso.
2. booted always fresh (without changes), setup-pman and moved to modules folder on sda1
3. reboot
4. created nemesis folder on sda3 to store the changes on a linux file system. Modified porteus.cfg to store persistance with changes=/dev/sda3/nemesis
5. pacman -Syy asked for pacman-db-upgrade, did it
6. needed to refresh datatbases with pacman -Sy
7. installed archlinuxfr repo, it appears after pacman -Syy

It seems that I stuck here:
8. pacman -S package-query:
looking for conflicting packages
packages (2) pacman-5.0.1-4 package-query-1.8-1
error key F99FF0FEAE999BD could not be looked remotely
required key missing from keyring
failed to commit transaction
Voltaire: Le mieux est l'ennemi du bien.

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#4 by istinnjazz » 17 Jul 2016, 21:26

You probably have to update keys again. Do not ask me why. See 2nd post.
But I m sure you can search a bit deeper by yourself when such an error occurs. Do not stop in such a message, just look around the net. I suppose a solution for you is close.
There is enormous information about arch, and nemesis will probably respond to it.

so, except my 2nd post
google "could not be looked remotely required key missing from keyring"

results with possible solutions (keyring & pgp):
https://bbs.archlinux.org/viewtopic.php?id=193382
https://forum.manjaro.org/t/missing-key ... pgrade/776

maybe only this could do it:

Code: Select all

pacman-key --init
pacman-key --populate archlinux
pacman-key --populate manjaro
pacman-key –refresh-keys
and maybe:

Code: Select all

pacman -Syy archlinux-keyring manjaro-keyring
as suggested at 2nd post

and finally check:
https://wiki.archlinux.org/index.php/Pa ... icial_keys

archlinuxfr is an Unsigned repository, so there are no pgp keys there
but you could try edit pacman.conf again:
from: https://wiki.archlinux.org/index.php?ti ... Unsigned_2
Note: Users will need to add the following to these entries:

Code: Select all

SigLevel = PackageOptional
this command should present all installed keys:

Code: Select all

gpg --homedir /etc/pacman.d/gnupg --list-keys

but remember that you do not want to get a full update at this stage, so do not use -u for pacman database update -Syy command as some had used.
If you want a full system update, I suggest you at first, to backup your persistence partition or save.dat so you can restore to this step easily. This is the price you have to pay by using a rolling release in order not to end up... with a broken system. If you will respect this, you could use this release for years.

good luck

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#5 by francois » 18 Jul 2016, 10:51

Thanks a lot. I will try your strategies.
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#6 by francois » 19 Aug 2016, 23:56

Ok. Just booted from usb. There was a problem booting from virtualbox.

Firefox works now. It came standard with nemesis. No need to:

Code: Select all

pman -S firefox
or 
pacman -S firefox
Edit a few hours later:
There is a problem with openrc-eudev: OK. I have tried a little time later and it did sync openrc-eudev. :D

Code: Select all

root /home/guest # pman -Syy
:: Synchronizing package databases...
 core                     118.5 KiB   258K/s 00:00 [######################] 100%
 extra                   1760.6 KiB  1365K/s 00:01 [######################] 100%
 community                  3.6 MiB   764K/s 00:05 [######################] 100%
error: failed retrieving file 'openrc-eudev.db' from downloads.sourceforge.net : Connection timed out after 10657 milliseconds
error: failed to update openrc-eudev (download library error)
root /home/guest # 
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#7 by francois » 20 Aug 2016, 02:55

Firefox is sluggish, but it works. Chromium module will not work.

1.0 I get further and not the way you have experienced up to now:

Code: Select all

root /home/guest # pacman -S pacman
resolving dependencies...
looking for conflicting packages...

Packages (1) pacman-5.0.1-4

Total Download Size:   0.71 MiB
Total Installed Size:  4.42 MiB
Net Upgrade Size:      0.47 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages ...
 pacman-5.0.1-4-x86_64    732.0 KiB   131K/s 00:06 [######################] 100%
(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%
(1/1) upgrading pacman                             [######################] 100%
warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew
warning: /etc/makepkg.conf installed as /etc/makepkg.conf.pacnew
warning: directory permissions differ on /var/cache/pacman/pkg/
filesystem: 777  package: 755
root /home/guest # 
2.0 And pman will not make a package of pacman:

Code: Select all

root /home/guest # pman -S pacman
Thus I will have to keep the changes folder.

3.0 Trying to install pamac or octopi failed, so I proceeded to install package-query with the:

Code: Select all

[archlinuxfr]
SigLevel = Optional TrustAll
SigLevel = PackageRequired
Server = http://repo.archlinux.fr/$arch

Code: Select all

root /home/guest # pacman -S package-query
resolving dependencies...
looking for conflicting packages...

Packages (1) package-query-1.8-1

Total Installed Size:  0.09 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
error: package-query: missing required signature
error: failed to commit transaction (package missing required signature)
Errors occurred, no packages were upgraded.
root /home/guest #
I imagine that I will have to look to manjaro and archlinux keyrings.

The wife asked me to go to bed. I will look at it tomorrow. :wink:
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#8 by francois » 20 Aug 2016, 04:58

Or maybe just do what pacman told me to do:

Code: Select all

warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew
warning: /etc/makepkg.conf installed as /etc/makepkg.conf.pacnew
warning: directory permissions differ on /var/cache/pacman/pkg/
filesystem: 777  package: 755/code]

For pacman.conf, I should replace the new with the old including some specifications of the old, the same should apply to makepkg.conf
https://bbs.archlinux.org/viewtopic.php?id=81096
fanthom's kde diff utility would be handy, but I will presume that only the end of the pacman.conf has changed. And pacman -Syy will be needed to update.

Also pacman does not like that 777 with all permissions on /path/pkg/
https://bbs.archlinux.org/viewtopic.php?id=189403

Some say leave it and others change it to more restrictive.
Voltaire: Le mieux est l'ennemi du bien.

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#9 by francois » 20 Aug 2016, 12:45

Code: Select all

root /var/cache/pacman # pacman -S package-query
resolving dependencies...
looking for conflicting packages...

Packages (1) package-query-1.8-1

Total Installed Size:  0.09 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
error: package-query: missing required signature
error: failed to commit transaction (package missing required signature)
Errors occurred, no packages were upgraded.
root /var/cache/pacman # 
I tried post 2 for the keyring issue:

Code: Select all

root /var/cache/pacman # pacman -S manjaro-keyring
error: target not found: manjaro-keyring
root /var/cache/pacman # 
No manjaro-keyring in database.
Voltaire: Le mieux est l'ennemi du bien.

User avatar
istinnjazz
Samurai
Samurai
Posts: 114
Joined: 15 May 2016, 14:10
Distribution: Manjaro-OpenRC/Nemesis

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#10 by istinnjazz » 21 Aug 2016, 08:27

It seems you have destroyed or have not created correctly mirrors in your pacman configuration. Please follow my advice and if you make a step you cannot follow, use a backup until you have a working sysyem. I cannot follow every issue it will probably come out, so you have to go a bit deeper on your own, log and save your results, and post about your experience after your new extensive research.

Google. -> error: target not found: pacman

User avatar
francois
Contributor
Contributor
Posts: 4902
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Pacman / Pamac update & keyring issues for nemesis 3.5

Post#11 by francois » 22 Aug 2016, 16:12

Damn it! =@

I feel such a newcomer with linux (arch). :oops:
Voltaire: Le mieux est l'ennemi du bien.

Post Reply