echo "Types: deb deb-src
URIs: https://repos.gnupg.org/deb/gnupg/noble/
Suites: noble
Components: main
Signed-By: /usr/share/keyrings/gnupg-keyring.gpg" | \
sudo tee /etc/apt/sources.list.d/gnupg.sources
But now I am stuck. This is because I am getting package conflicts between ubuntu's version of GPG and this new version of GPG.
sudo apt install gnupg2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
gnupg2 : Depends: gnupg (>= 2.5.20-1) but 2.4.4-2ubuntu17.4 is to be installed
E: Unable to correct problems, you have held broken packages.
The issue is a dependency ordering problem. Your system is trying to install gnupg2 2.5.20-1 (which requires gnupg >= 2.5.20-1 ), but it's not simultaneously upgrading the gnupg package from 2.4.4 to 2.5.20.
Solution: Upgrade gnupg first
Explicitly upgrade the gnupg package before installing gnupg2 :
But when the Source has a higher Priority, it would take the Version from there. When You look at the Link, You can see what the Repo offers for Packages. And there is gnupg included.
I would prefer to be on the stable version provided by repos.gnupg.org, rather than their development branch.
This does not work.
~$ sudo apt install gnupg=2.5.20-1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
gnupg : Depends: dirmngr (>= 2.5.20-1)
Depends: gpg (>= 2.5.20-1)
Depends: gpg-agent (>= 2.5.20-1)
Depends: gpgsm (>= 2.5.20-1)
Depends: scdaemon (< 2.5.20-1.1~)
Depends: scdaemon (>= 2.5.20-1)
Breaks: dirmngr (< 2.5.20-1)
Breaks: dirmngr:i386 (< 2.5.20-1)
Recommends: gnupg-utils (>= 2.5.20-1)
Recommends: gpg-wks-client (>= 2.5.20-1) but 2.4.4-2ubuntu17.4 is to be installed
Recommends: gpgv (>= 2.5.20-1)
E: Unable to correct problems, you have held broken packages.
I tried this, but unfortunately it does not work. Here are the contents of /etc/apt/preferences.d/gnupg-pin.
~$ sudo apt install gnupg2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
gnupg2 : Depends: gnupg (>= 2.5.20-1) but 2.4.4-2ubuntu17.4 is to be installed
E: Unable to correct problems, you have held broken packages.
I am afraid that this does not work. The link in the pin field does not work. I suppose it does not like the https. And putting the pin priority at 1001 instead of 1000 does not make any difference.
If running Kyber creates a critical need, you should isolate (such as installing the newer GnuGPG to /opt/gnupg) or containerize the newer build.
Trying to replace it on the existing system will not only send you into a dependency whirlpool (which skimming through the thread, appears you have experienced this already), it also opens you up to a variety of nebulous system errors that may not be obvious at first. Highly unstable.