Bash 5.0.011 and pacman 5.2.0 are now available

Also available in Traditional Chinese.

dragons
The following updates are now available in the stable repository [core].

Name Version Release date Link to issue/epic
bash 5.0.011 2019-08-29 core#191
pacman 5.2.0 2019-10-21 core#239

Other packages that have been rebuilt are listed below.

Complete list of packages
# Moved to [core]
bash-5.0.011-2-x86_64.pkg.tar.xz
chakra-keyring-20190324-4-any.pkg.tar.xz
pacman-5.2.0-2-x86_64.pkg.tar.xz
pacman-contrib-1.2.0-2-x86_64.pkg.tar.xz

# Moved to [desktop]
alpm_octopi_utils-1.0.2-1-x86_64.pkg.tar.xz
octopi-0.10.0-2-x86_64.pkg.tar.xz
octopi-notifier-0.10.0-2-x86_64.pkg.tar.xz

Most of our mirrors synchronize with the central repositories on the origin server within 24 hours. Run sudo pacman -Syu to update and upgrade your system. If you have any issues updating or upgrading, reply to this topic with the complete input and output in English, i.e. run LC_ALL=C sudo pacman -Syu.

2 Likes

Hi there, The update does not work for me, it seems as if it is related to PGP-keys.
When checking the keyring I was asked to import PGP keys, what actually never happened before.
Then when checking the package integrity the keys for totte and Jeff Huang are not accepted.

If have attached the output of LC_ALL=C sudo pacman -Syu:
pacman-output.txt (25,0 KB)
All questions were answered with Yes.

I am getting similar issues to Michael Battenfeld
but it also asked me to try
sudo pacman-key --init
which I did but it did not help.

Hi @mille and welcome,

please try running this first:

$ sudo pacman-key --init
$ sudo pacman-key --populate chakra

I failed to mention this in Bash 5.0.011 and pacman 5.2.0 are now available – you can read more about it here.

pacman-key --populate chakra
gives
==> ERROR: The keyring file /usr/share/pacman/keyrings/chakra.gpg does not exist.

Please ensure that core/chakra-keyring is installed, then run the commands posted above:

$ sudo pacman-key --init
$ sudo pacman-key --populate chakra

If the issue persists, please post your /etc/pacman.conf file.

pacman.conf (2.7 KB)

What is the output of this command?

$ pacman -Qkk chakra-keyring

sudo pacman -Qkk chakra-keyring gives
package ‘chakra-keyring’ was not found

sudo pacman -S core/chakra-keyring
gives
error: chakra-keyring: signature from “Chaka Build Server (Automated Chakra Build System) staff@chakralinux.org” is unknown trust
:: File /var/cache/pacman/pkg/chakra-keyring-20190324-4-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).

Please format your posts to make output easier to read (there’s a button labelled “Pre-formatted text”). I suggest that you edit your /etc/pacman.conf from this:

SigLevel    = Required DatabaseNever

…to this:

SigLevel    = Never DatabaseNever

Then, install the keyring and follow the steps provided earlier:

$ sudo pacman -Syu
$ sudo pacman -S chakra-keyring
$ sudo pacman-key --init
$ sudo pacman-key --populate chakra

Finally, revert the edit of your /etc/pacman.conf.

2 Likes

Thanks, that did the trick.

Should I now edit my /etc/pacman.conf from this:

SigLevel = Never DatabaseNever

…to this:

SigLevel = Required DatabaseNever ?

Yes, revert the edit of your /etc/pacman.conf.

This approach worked for me, too. Thank you @totte!

core/chakra-keyring has been added as a dependency of core/pacman as per issue core#253. See merge request core!7 for more information. Issue core#169 is also relevant.

Further reading:

https://wiki.archlinux.org/index.php/Pacman/Package_signing
https://wiki.archlinux.org/index.php/DeveloperWiki:Keyring_Package
https://www.archlinux.org/master-keys/

1 Like

Hi,

I had to install Chakra on a new system and am experiencing problems like this. I took all the steps mentioned/suggested, and read through all the given information… still the problem didn’t resolve…
I have reinstalled chakra-keyring as it had been installed all the time, I have had edited pacman.conf (SigLevel) and reverted to the proper value… nothing seems to help…

It’s only certain packages that are of ‘marginal trust’…

The funny thing is, when I install the same packages after a clean installation - before updating the system (pacman -Syu) there is no problem at all…
The problems with marginal untrusted packages come after a system wide update…

My questions…

  1. Can it just be that there are some packages which are signed incorrectly? What is the proper place to make report of that?
  2. Is there anything else to this problem that could have occured, but wasn’t mentioned as a solution… (I haven’t edited any configuration apart from the above, it’s a blank install of Goedel 2017.03)

I would like to give an example terminal output… (sorry it’s in Dutch)

[cyberfloater@home-desktop ~]$ sudo pacman -S gimp
[sudo] wachtwoord voor cyberfloater:
afhankelijkheden oplossen…
zoeken naar conflicterende pakketten…

Pakketten (19) babl-0.1.72-1 gegl-0.4.16-1 gsfonts-20170829-1 gtk2-2.24.32-2
lensfun-0.3.2-4 libde265-1.0.3-1 libgexiv2-0.10.8-2
libglade-2.6.4-4 libheif-1.3.2-1 libmypaint-1.3.0-1
libspiro-20190731-1 libwmf-0.2.8.4-14 mypaint-brushes-1.3.0-1
poppler-data-0.4.8-2 pygobject2-devel-2.28.6-1 pygtk-2.24.0-3
python2-gobject2-2.28.6-1 suitesparse-4.4.1-3 gimp-2.10.12-1

Totale Download Grootte: 1,74 MiB
Totale Geïnstalleerde Grootte: 194,96 MiB

:: Doorgaan met de installatie? [J/n] j
:: Pakketten ophalen…
libglade-2.6.4-4… 84,5 KiB 2,06 MiB/s 00:00 [########################] 100%
pygtk-2.24.0-3-x… 1697,7 KiB 8,29 MiB/s 00:00 [########################] 100%
(19/19) sleutels in sleutelbos controleren [########################] 100%
(19/19) pakketintegriteit controleren [########################] 100%
fout:libglade: handtekening van “Luca Giambonini gluca86@gmail.com” is onbekend vertrouwd
:: Bestand /var/cache/pacman/pkg/libglade-2.6.4-4-x86_64.pkg.tar.xz is corrupt (ongeldig of corrupt pakket (PGP handtekening)).
Wilt u dit bestand verwijderen? [J/n] j
fout:pygtk: handtekening van “Luca Giambonini gluca86@gmail.com” is onbekend vertrouwd
:: Bestand /var/cache/pacman/pkg/pygtk-2.24.0-3-x86_64.pkg.tar.xz is corrupt (ongeldig of corrupt pakket (PGP handtekening)).
Wilt u dit bestand verwijderen? [J/n] j
fout:fout bij het uitvoeren van de transactie (ongeldig of corrupt pakket)
Er zijn fouten opgetreden, geen enkel pakket geüpgraded.

Please format output using the button labelled “Preformatted text” (and not the “Blockquote” one) as it makes output easier to read. To troubleshoot the upgrade to bash 5.0.011 and pacman 5.2.0, please reply as per the opening post:

To report issues with packages, see this #help:faq entry:

I picked the wrong one… :frowning:

Didn’t know that was possible, I learned something!

I have further looked into it, and feel stupid for not noticing that chakra-keyring was only installed by the update process, because it’s dependency was fixed…

Setting up the system must be a breeze now, and I apologize for ‘commenting outside the guidelines’ - I will definately do some reading up when having set up this system.

Thanks

This topic was automatically closed after 23 days. New replies are no longer allowed.