Skip to content

Commit

Permalink
Fix gnupgcompat1 which doesn't seem to work with gnupg version 2.1.
Browse files Browse the repository at this point in the history
  • Loading branch information
peti committed Nov 7, 2014
1 parent a55228c commit 4c84621
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pkgs/top-level/all-packages.nix
Original file line number Diff line number Diff line change
Expand Up @@ -1269,7 +1269,7 @@ let

gnupg1orig = callPackage ../tools/security/gnupg/1.nix { };

gnupg1compat = callPackage ../tools/security/gnupg/1compat.nix { };
gnupg1compat = callPackage ../tools/security/gnupg/1compat.nix { gnupg = gnupg20; };

# use config.packageOverrides if you prefer original gnupg1
gnupg1 = gnupg1compat;
Expand Down

2 comments on commit 4c84621

@wkennington
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer that we mask gnupg to 2.0 just for git-annex so that we can uncover any other issues when pushing forward. It would be nice to see gpg21 used in the 14.11 release. The compat package really does work fine.

@peti
Copy link
Member Author

@peti peti commented on 4c84621 Nov 7, 2014

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have reproducible evidence to show that gnupg1compat changes behavior when updating GnuPG from 2.0 to 2.1. Do you have any evidence to suggest that these build failures are the fault of git-annex? I.e. is there any indication that git-annex uses the gpg binary in an incorrect way?

Please sign in to comment.