aboutsummaryrefslogtreecommitdiff
path: root/pkgs/development/libraries/gpgme (follow)
Commit message (Collapse)AuthorAgeFilesLines
* gpgme: 1.14.0 -> 1.15.0 (#103919)Michael Weiss2020-11-161-2/+2
|
* gpgme: 1.13.1 -> 1.14.0 (#93353)Michael Weiss2020-07-191-10/+4
|
* treewide: replace base64 encoded hashesDaiderd Jordan2020-06-031-2/+2
|
* gpgme: convert macos sed patch scripts to patch filesJörg Thalheim2020-04-212-16/+23
| | | | | | This is less brittle and breaks loud if the code changes. Also remove the /usr/bin/file patch. It is not really required for the build to work, the generated warning is harmless.
* pgpgme: Fix build with python on macOSKirill Elagin2020-04-211-0/+9
| | | | | | | | | | | * Replace LD_LIBRARY_PATH with OS-specific name (e.g. DYLD_LIBRARY_PATH on macOS). * Disable Python tests on macOS, because they use gpg, which fails due to a very long socket path (https://github.com/NixOS/nix/pull/1085). The former should be fixed upstream. The latter is a Nix-specific issue, but it can be worked-around upstream by making Python tests respect --disable-gpg-test.
* treewide: Per RFC45, remove all unquoted URLsMichael Reilly2020-04-101-1/+1
|
* gpgme: Fix tests with gnupg > 2.2.19Jan Tojnar2020-04-021-1/+16
|
* treewide: NIX_*_COMPILE -> stringRobin Gloster2019-12-311-2/+2
|
* Remove myself (fuuzetsu) from maintainer listsMateusz Kowalczyk2019-12-051-1/+1
| | | | | | I haven't been doing any maintenance for a long time now and not only do I get notified, it also creates a fake impression that all these packages had at least one maintainer when in practice they had none.
* treewide: name -> pname (easy cases) (#66585)volth2019-08-151-2/+2
| | | | | | | | | treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
* gpgme: 1.13.0 -> 1.13.1R. RyanTM2019-06-161-2/+2
| | | | | | | Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/gpgme/versions
* gpgme: disable tests on darwinDmitry Kalinkin2019-06-071-1/+6
|
* [treewide] delete unused patchesc0bw3b2019-05-041-12/+0
|
* gpgme: 1.12.0 -> 1.13.0Will Dietz2019-03-261-13/+3
| | | | | | | https://lists.gnupg.org/pipermail/gnupg-announce/2019q1/000437.html Drop autoreconfHook and git, otherwise version contains `-unknown` which is unfortunate but also breaks build w/seahorse.
* gpgme: cross compilationMichael Eden2019-03-211-0/+4
|
* gpgme: Update the URL for fix-key-expiry.patchMichael Weiss2019-01-241-2/+2
| | | | | | | The old URL was gone, see: https://github.com/NixOS/nixpkgs/pull/53693#pullrequestreview-195177688 Thanks @volth :)
* libsForQt5.qgpgme: fix tests after 2019-01-06Tor Hedin Brønner2019-01-091-1/+9
| | | | | | The keys used in one of the qt tests expired on 2019-01-06 breaking the build. closes https://github.com/NixOS/nixpkgs/issues/53632
* python3Packages.gpgme: enable python3 versionMatthieu Coudron2018-10-191-4/+4
| | | | | | | | | | | | | | | | | when calling python3Packages.gpgme, it was still picking python2. Changed withPython into pythonSupport since it's the convention. I had to enable ncurses too because of this error when configuring: configure:19978: checking python extra libraries configure:19985: result: -lpthread -ldl -lcrypt -lncurses -lutil -lm configure:19992: checking python extra linking flags configure:19999: result: -Xlinker -export-dynamic configure:20006: checking consistency of all components of python development environment configure:20032: gcc -o conftest -g -O2 -I/nix/store/hy65mn4wjswqih75gfr6g4q3xgqdm325-python3-3.6.6/include/python3.6m conftest.c -L/nix/store/hy65mn4wjswqih75gfr6g4q3xgqdm325-python3-3.6.6/lib -lpython3.6m -Xlinker -export-dynamic -lpthread -ldl -lcrypt -lncurses -lutil -lm >&5 /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/ld: cannot find -lncurses collect2: error: ld returned 1 exit status configure:20032: $? = 1
* gpgme: enable tests, they pass! :)Will Dietz2018-10-121-1/+1
|
* gpgme: 1.11.1 -> 1.12.0Will Dietz2018-10-091-2/+2
| | | | https://lists.gnupg.org/pipermail/gnupg-announce/2018q4/000429.html
* gpgme: use default texinfoJan Malakhovski2018-09-081-2/+2
|
* reewide: Purge all uses `stdenv.system` and top-level `system`John Ericson2018-08-301-1/+4
| | | | It is deprecated and will be removed after 18.09.
* gpgme: make tests run, but disable. Spooky!Jan Malakhovski2018-08-111-0/+4
|
* pkgs/*: remove unreferenced function argumentsvolth2018-07-211-1/+1
|
* gpgme: 1.10.0 -> 1.11.1Michael Weiss2018-04-211-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.
* gpgme: add withPython ? false to enable bindingsMatthieu Coudron2018-03-211-2/+0
| | | | Useful for MUAs mostly, like alot
* alot: 0.5.1 to 0.7.0Matthieu Coudron2018-03-211-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.
* gpgme: 1.9.0 -> 1.10.0Michael Weiss2017-12-141-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.
* qgpgme: build with -DQT_NO_DEBUGThomas Tuegel2017-08-211-2/+5
| | | | | qgpgme uses Q_ASSERT which causes build inputs to be retained unnecessarily at runtime unless debugging is disabled.
* pkgs: refactor needless quoting of homepage meta attribute (#27809)Silvan Mosberger2017-08-011-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
* qgpgme: init at 1.9.0Thomas Tuegel2017-06-181-5/+16
|
* gpgme: enable Qt 5 bindingsJos van den Oever2017-06-182-2/+16
|
* gpgme: 1.8.0 -> 1.9.0Michael Weiss2017-04-021-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
* Revert "gpgme: Drop multiple outputs (dev and info)"Michael Weiss2017-03-211-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.
* gpgme: Drop multiple outputs (dev and info)Michael Weiss2017-03-211-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.
* gpgme: fix build on macOSIgnat Loskutov2017-02-161-0/+3
|
* gpgme: 1.7.0 -> 1.8.0Franz Pletz2017-01-301-3/+2
|
* gpgme: fix build on i686-linuxThomas Tuegel2016-10-101-0/+3
|
* gpgme: 1.6.0 -> 1.7.0Franz Pletz2016-09-241-2/+2
|
* treewide: Shuffle outputsTuomas Tynkkynen2016-08-291-1/+1
| | | | Make either 'bin' or 'out' the first output.
* Merge recent 'staging' into closure-sizeVladimír Čunát2016-02-031-5/+6
|\ | | | | | | Let's get rid of those merge conflicts.
| * gpgme: Use fixed path for GnuPG binariesaszlig2016-01-211-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>
* | gpgme: split dev and info outputsVladimír Čunát2015-10-131-4/+7
|/
* gpgme: 1.5.5 -> 1.6.0William A. Kennington III2015-09-041-2/+2
|
* gpgme: 1.5.4 -> 1.5.5Matthias Beyer2015-07-011-2/+2
|
* gpgme: 1.5.3 -> 1.5.4William A. Kennington III2015-04-281-2/+2
|
* gpgme: use different mirrorCharles Strahan2015-01-241-1/+1
|
* gpgme: 1.5.2 -> 1.5.3William A. Kennington III2014-12-161-2/+2
|
* gpgme: update from 1.5.1 to 1.5.2Mateusz Kowalczyk2014-12-031-2/+2
|
* gpgme: update from 1.4.3 to 1.5.1Mateusz Kowalczyk2014-09-211-4/+12
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 10:32:23 +0000