Re: [Cannot install 2.5.7 in noble] (was: Problem with gpgsm --import and p12 files issued from a Spanish government agency)

Meik Michalke via Gnupg-users <[email protected]> Thu, 19 Feb 2026 09:46:59 +0100

Newsgroups	gmane.comp.encryption.gpg.user
Message-ID	<2029627.JfuecHORi0@kasidy>

hi,

Am Mittwoch, 18. Februar 2026, 15:02:36 CET schrieb Uwe Brauer via Gnupg-
users:
> I followed the instructions https://repos.gnupg.org/deb/gnupg/noble/
> 
> But the last step
> 
> sudo apt-get install gnupg2
> 
> Returns:

that is actually not quite what's suggested by the instructions:

  Now you should be able to install/upgrade our packages:

  sudo apt update
  sudo apt upgrade
  sudo apt install gnupg2

we're following the recommendation for using apt instead of apt-get for 
interactive use (since the use of apt-get outside of scripts was discouraged 
years ago). AFAIK apt does a better job when it comes to dependency handling, 
in that it is better equipped to determine the optimal order of package 
replacements.

Am Donnerstag, 19. Februar 2026, 08:29:07 CET schrieb Uwe Brauer via Gnupg-
users:
> It seems that the following worked:
> 
> 
>   sudo apt-get install libgcrypt20
>   sudo apt-get install libgpg-error0
>   sudo apt-get install gpgconf
>   sudo apt-get install gpgsm

this looks to me like you had to find out a working order for yourself with 
apt-get in this case.

depending on your specific package selection, even apt may fail in finding a 
solution when multiple packages with interdependencies are to be replaced in 
one go. but it should at least return an insightful error message on why it is 
not able to satisfy the dependency tree.

there's also a blog article with some information on how to use 'apt policy' 
to look at the current package preferences when multiple versions are 
available:

https://gnupg.org/blog/20250827-new-repository.html


viele grüße :: m.eik

_______________________________________________
Gnupg-users mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-users

signature.asc (application/pgp-signature, 265 B)