about summary refs log tree commit diff
path: root/pkgs/development/libraries/gpgme
AgeCommit message (Collapse)AuthorFilesLines
2018-04-21gpgme: 1.10.0 -> 1.11.1Michael Weiss1-2/+2
I've rebuild all packages that depend on gpgme and everything seems fine so far (there are a few failures but the ones I've checked are unrelated to gpgme). Upstream release notes (Noteworthy changes in version 1.11.1): * Fixed build problems in the 1.11.0 release. * Added C++ interfaces which were planned for 1.11.0. The 1.11.0 release came with these changes: * New encryption API to support direct key specification including hidden recipients option and taking keys from a file. This also allows to enforce the use of a subkey. * New encryption flag for the new API to enforce the use of plain mail addresses (addr-spec). * The import API can now tell whether v3 keys are skipped. These old and basically broken keys are not anymore supported by GnuPG 2.1. * The decrypt and verify API will now return the MIME flag as specified by RFC-4880bis. * The offline mode now has an effect on gpg by disabling all network access. [#3831] * A failed OpenPGP verification how returns the fingerprint of the intended key if a recent gpg version was used for signature creation. * New tool gpgme-json as native messaging server for web browsers. As of now public key encryption and decryption is supported. Requires Libgpg-error 1.29. * New context flag "request-origin" which has an effect when used with GnuPG 2.2.6 or later. * New context flag "no-symkey-cache" which has an effect when used with GnuPG 2.2.7 or later. * New convenience constant GPGME_KEYLIST_MODE_LOCATE. * Improved the Python documentation. * Fixed a potential regression with GnuPG 2.2.6 or later. * Fixed a crash in the Python bindings on 32 bit platforms. [#3892] * Various minor fixes.
2018-03-21gpgme: add withPython ? false to enable bindingsMatthieu Coudron1-2/+0
Useful for MUAs mostly, like alot
2018-03-21alot: 0.5.1 to 0.7.0Matthieu Coudron1-4/+19
- added gnupg to checkInputs - generate manpage (optional) - move alot.desktop file to $out/share/applications - disabled tests as they need the network (dependency on twisted) Thanks to Sarah Brofeldt, Ben Mcginnes for their help (and other) and to FRidh for the repeated careful reviews.
2017-12-14gpgme: 1.9.0 -> 1.10.0Michael Weiss1-10/+2
I've removed qgpgme-format-security.patch as version 1.10.0 already contains it: git tag --contains=5d4f977dac542340c877fdd4b1304fa8f6e058e6 Everything rebuilds fine so far. Upstream release notes (Noteworthy changes in version 1.10.0): * Now returns more specific error codes for decryption to distinguish between bad passphrase, user canceled, and no secret key. * Now returns key origin information if available. * Added context flag "auto-key-retrieve" to selectively enable the corresponding gpg option. * Added flag is_de_vs to decryption and verify results. * py: Use SEEK_SET as default for data.seek. * cpp: Various new APIs. * Reduced spawn overhead on Linux again. Added new configure option --disable-linux-getdents to disable this feature for very old Linux versions. * Improved the Python bindings build system. * Made the test suite less fragile.
2017-08-21qgpgme: build with -DQT_NO_DEBUGThomas Tuegel1-2/+5
qgpgme uses Q_ASSERT which causes build inputs to be retained unnecessarily at runtime unless debugging is disabled.
2017-08-01pkgs: refactor needless quoting of homepage meta attribute (#27809)Silvan Mosberger1-1/+1
* pkgs: refactor needless quoting of homepage meta attribute A lot of packages are needlessly quoting the homepage meta attribute (about 1400, 22%), this commit refactors all of those instances. * pkgs: Fixing some links that were wrongfully unquoted in the previous commit * Fixed some instances
2017-06-18qgpgme: init at 1.9.0Thomas Tuegel1-5/+16
2017-06-18gpgme: enable Qt 5 bindingsJos van den Oever2-2/+16
2017-04-02gpgme: 1.8.0 -> 1.9.0Michael Weiss1-18/+14
For the license change see: - https://directory.fsf.org/wiki/GPGME#tab=Details - AUTHORS [0] See #24491 for the other changes. [0]: https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgme.git;a=blob;f=AUTHORS;h=bbf1576ad27dc51956c371282862b468c633ea49;hb=HEAD
2017-03-21Revert "gpgme: Drop multiple outputs (dev and info)"Michael Weiss1-0/+3
This reverts commit 872770286d04cadb9816cd1665d3d5f17adce456. This will fix fwknop as well (should have done it like this in the first place, where was my mind...). Conclusion: Did something stupid... :o - I am *so incredibly sorry*, will be way more careful (was already careful, but apparently not enought...) next time and use nox. Sorry @everyone and thanks @calvertvl for noticing this.
2017-03-21gpgme: Drop multiple outputs (dev and info)Michael Weiss1-3/+0
This shouldn't break anything as currently neither dev nor info will be generated anyway (since both directories don't actually exist at the install phase - "mv bin dev" would produce the dev output). This change is required for building fwknop with GnuPG support.
2017-02-16gpgme: fix build on macOSIgnat Loskutov1-0/+3
2017-01-30gpgme: 1.7.0 -> 1.8.0Franz Pletz1-3/+2
2016-10-10gpgme: fix build on i686-linuxThomas Tuegel1-0/+3
2016-09-24gpgme: 1.6.0 -> 1.7.0Franz Pletz1-2/+2
2016-08-29treewide: Shuffle outputsTuomas Tynkkynen1-1/+1
Make either 'bin' or 'out' the first output.
2016-02-03Merge recent 'staging' into closure-sizeVladimír Čunát1-5/+6
Let's get rid of those merge conflicts.
2016-01-21gpgme: Use fixed path for GnuPG binariesaszlig1-5/+6
By default, GPGME tries to search in $PATH for the gpg and gpgconf binaries. This has the downside, that the library won't work by its own and needs to have GnuPG in systemPackages or the user environment. I've stumbled on this while working on one of the dependencies of nixos-assimilate and nixpart (volume_key), where the testing environment didn't come with GnuPG in $PATH and thus the tests have failed. After testing this with a few programs using GPGME, I haven't found any weird behavior in conjunction with the GnuPG agent. However one possible implication could be that if the GnuPG used in $PATH (and the config files in the user's home directory) should be vastly incompatible, it could lead to failures. In practice however, the GnuPG1/2 versions pretty much seem to stay compatible within their major releases so it shouldn't pose a problem. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2015-10-13gpgme: split dev and info outputsVladimír Čunát1-4/+7
2015-09-04gpgme: 1.5.5 -> 1.6.0William A. Kennington III1-2/+2
2015-07-01gpgme: 1.5.4 -> 1.5.5Matthias Beyer1-2/+2
2015-04-28gpgme: 1.5.3 -> 1.5.4William A. Kennington III1-2/+2
2015-01-24gpgme: use different mirrorCharles Strahan1-1/+1
2014-12-16gpgme: 1.5.2 -> 1.5.3William A. Kennington III1-2/+2
2014-12-03gpgme: update from 1.5.1 to 1.5.2Mateusz Kowalczyk1-2/+2
2014-09-21gpgme: update from 1.4.3 to 1.5.1Mateusz Kowalczyk1-4/+12
2013-12-04gpgme: update from 1.4.1 to 1.4.3Nixpkgs Monitor1-2/+2
2013-06-24gpgme: Update to latest upstream version 1.4.1.aszlig1-3/+3
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-28Rename buildNativeInputs -> nativeBuildInputsEelco Dolstra1-1/+1
Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs" sounds like an imperative rather than a noun phrase.
2012-11-15gpg/pth: fixing the pth building on armLluis Batlle1-4/+13
I could built pth with the fix commented in: http://forums.gentoo.org/viewtopic-t-904280-start-0.html And I remove the 'pth.supported' structure I had built.
2012-11-14pth, gpg: taking out pth in non-supported platforms.Lluis Batlle1-1/+2
I know that pth fails to build on arm, by now.
2012-04-09gpgme: upgraded to 1.3.1Mathijs Kwik1-2/+2
svn path=/nixpkgs/trunk/; revision=33679
2011-07-21* Whitespace.Eelco Dolstra1-3/+5
svn path=/nixpkgs/branches/kde-4.7/; revision=27883
2011-06-07gpgme: propagate some dependenciesYury G. Kudryashov1-1/+4
svn path=/nixpkgs/trunk/; revision=27384
2010-05-19Remove gpg->gpg2 symlinkYury G. Kudryashov1-2/+3
Also make gpgme compile&find gpg2 svn path=/nixpkgs/trunk/; revision=21885
2010-05-19Mass GnuPG upgradeYury G. Kudryashov1-4/+4
gnupg tests fail. Will try to fix later. svn path=/nixpkgs/trunk/; revision=21884
2010-05-19Move gnupg to gnupg1 and gnupg2 to gnupgYury G. Kudryashov1-2/+2
Also add gnupg1-compatibility symlinks to gnupg2. Most packages should be able to use gnupg2 instead of gnupg1. svn path=/nixpkgs/trunk/; revision=21883
2008-01-28More dependencies for gpgmeYury G. Kudryashov1-2/+2
svn path=/nixpkgs/trunk/; revision=10347
2007-08-08Some upgrades needed for kde4:Yury G. Kudryashov1-3/+3
* alsa-lib: 1.0.12 -> 1.0.14 * alsa-utils: 1.0.13 -> 1.0.14 * strigi: 0.5.1 -> 0.5.3dev * libgpg-error: 1.0 -> 1.4 * gpgme: 1.0.3 -> 1.1.4 * cmake: 2.4.6 -> 2.4.7 * Some kde4 components added (not compilable yet). * icu4c-3.6 added * boost: added unicode support to RegEx, switched to "system" layout svn path=/nixpkgs/trunk/; revision=9068
2006-01-30* Copy lots of files to nix.cs.uu.nl.Eelco Dolstra1-1/+1
svn path=/nixpkgs/trunk/; revision=4623
2005-12-19* Updated Sylpheed to 2.1.9 and added GPG support (through gpgme).Eelco Dolstra1-0/+10
svn path=/nixpkgs/trunk/; revision=4400
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-08 16:19:41 +0000