Updating to version 2.1.12

Asked by Dashamir Hoxha on 2016-06-01

The upstream package is updated to 2.1.12 (https://www.gnupg.org/download/), which I guess has more bug fixes, etc.
Are you going to update this package to it, and when?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnupg2 Edit question
Assignee:
No assignee Edit question
Solved by:
Dashamir Hoxha
Solved:
2016-06-02
Last query:
2016-06-02
Last reply:
2016-06-02

What is the output of:

lsb_release -a; uname -a

Thanks

Dashamir Hoxha (dashohoxha) said : #2

# lsb_release -a; uname -a
bash: lsb_release: command not found
Linux 8411bd21cf3d 3.13.0-86-generic #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

It is running in a Docker container.

I'm not seeing the 2.1.12 version in any PPAs. It's not even in Yakety.

What bugs are you seeing in the current version?

Dashamir Hoxha (dashohoxha) said : #4

Sir, the question is: why there is no version 2.1.12 yet? When will it be done?

If there is a significant reason to upgrade it then it will be upgraded. Packages in Ubuntu (and especially in LTS releases) are not upgraded just because a new version is available.

The fact that you said "which I guess has more bug fixes, etc" shows that you are just seeing a new version number rather than looking at what the actual difference is between the versions.

If you log a bug and state why the package should be upgraded sooner then it may get updated sooner. I suggest you don't blindly chase version numbers.

Dashamir Hoxha (dashohoxha) said : #6

Thanks for your answer. It makes sense, LTS upgrades packages only when they have security fixes.
However GnuPG is somehow a security related software, so I think that every new release is important.

I am not sure how many bugs are actually fixed, but I hear time after time on the discussion list that "this bug is fixed on 2.1.12".
(I also don't know how many new bugs 2.1.12 has introduced.) This announcement has a more detailed list of the fixed bugs:
https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000387.html

I know that 2.1.12 is not considered a stable release, but so is 2.1.11 too. It does not make sense for me to include 2.1.11 in a LTS, but not to upgrade to 2.1.12 . If you had to stick to stable releases, then you should have kept the version 2.0, which is officially called "the stable version", and not move forward to 2.1.11. So, in my opinion, either you roll back to 2.0, or move forward to 2.1.12

I suggest you report a bug