Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#29105 - Please reintroduce gnupg v1.* to testing
Attached to Project:
Arch Linux
Opened by fmk (clownish) - Sunday, 25 March 2012, 10:24 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 25 March 2012, 13:48 GMT
Opened by fmk (clownish) - Sunday, 25 March 2012, 10:24 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 25 March 2012, 13:48 GMT
|
DetailsDescription:
On 2012-03-24 gnupg was updated to 2.0.18-2 in testing, formerly gnupg2. Replacing gnupg with gnupg2 without having the possibility of using gnupg v1.* at all leads to problems, as gnupg2 does just work with gpg-agent and is really hard to use without pinentry which requires X (you may use pinentry-curses, but this still forces gpg-agent). So scripts which run without X and require gpg will stop working without additional configuration. Also than man-page stats: "In contrast to the standalone version gpg, which is more suited for server and embedded platforms, this version is commonly installed under the name gpg2 and more targeted to the desktop as it requires several other modules to be installed. The standalone version will be kept maintained and it is possible to install both versions on the same system." I don't see a reason for not providing both packages as before. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Sunday, 25 March 2012, 13:48 GMT
Reason for closing: Won't implement
Additional comments about closing: We package the most recent stable upstream version, that is, GnuPG-2. Please open specific bug reports for any issue you might have with GnuPG and we will sort them out.
Sunday, 25 March 2012, 13:48 GMT
Reason for closing: Won't implement
Additional comments about closing: We package the most recent stable upstream version, that is, GnuPG-2. Please open specific bug reports for any issue you might have with GnuPG and we will sort them out.
https://mailman.archlinux.org/pipermail/arch-dev-public/2012-March/022690.html
That's the interesting part for you:
https://mailman.archlinux.org/pipermail/arch-dev-public/2012-March/022719.html
packages.
First of all, symlinking gpg2 to gpg will not provide backwards compatibility.
Second, there is no use in removing v1 completly, why just don't make gpgme depend on gnupg2?
Third, calling gnupg2 gnupg is irritating, and would require to change
man-pages etc. too. Also it makes downgrading to v1 at the moment impossible,
because gpgme depends on gnupg2 which is now gnupg.
Beside of that, moving gnupg v1.* to aur will, in my eyes, support the view that gnupg is somewhat
not stable / outdated / can't be trusted which is not true.