Commit Graph

72 Commits

Author SHA1 Message Date
github-actions[bot]
1b5da764a7
Merge staging-next into staging 2021-01-27 12:24:09 +00:00
Ben Siraphob
3bbad8b041 treewide: remove inherited stdenv.lib 2021-01-27 12:44:43 +07:00
Thomas Tuegel
5590e365e4
qtbase: Check for wrapQtAppsHook in setupHook 2021-01-25 15:56:15 -06:00
Ben Siraphob
66e44425c6 pkgs/development/libraries: stdenv.lib -> lib 2021-01-21 19:11:02 -08:00
Jonathan Ringer
9bb3fccb5b treewide: pkgs.pkgconfig -> pkgs.pkg-config, move pkgconfig to alias.nix
continuation of #109595

pkgconfig was aliased in 2018, however, it remained in
all-packages.nix due to its wide usage. This cleans
up the remaining references to pkgs.pkgsconfig and
moves the entry to aliases.nix.

python3Packages.pkgconfig remained unchanged because
it's the canonical name of the upstream package
on pypi.
2021-01-19 01:16:25 -08:00
Michael Weiss
bfb627d78f gpgme: 1.15.0 -> 1.15.1 2021-01-10 16:16:24 +01:00
Mario Rodas
74c81a64f0 gpgme: fix build on darwin 2021-01-08 04:20:00 +00:00
Michael Weiss
1e1eb0eb44
gpgme: 1.14.0 -> 1.15.0 (#103919) 2020-11-16 19:32:00 +01:00
Michael Weiss
0c50808975
gpgme: 1.13.1 -> 1.14.0 (#93353) 2020-07-19 11:44:08 +02:00
Daiderd Jordan
7b3a2963d1
treewide: replace base64 encoded hashes 2020-06-03 18:35:19 +02:00
Jörg Thalheim
c88f04cb93 gpgme: convert macos sed patch scripts to patch files
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.
2020-04-21 08:37:12 +02:00
Kirill Elagin
5470d96645 pgpgme: Fix build with python on macOS
* 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.
2020-04-21 08:37:12 +02:00
Michael Reilly
84cf00f980
treewide: Per RFC45, remove all unquoted URLs 2020-04-10 17:54:53 +01:00
Jan Tojnar
6a99952795
gpgme: Fix tests with gnupg > 2.2.19 2020-04-02 06:35:36 +02:00
Robin Gloster
ab0cfd9e03
treewide: NIX_*_COMPILE -> string 2019-12-31 00:10:18 +01:00
Mateusz Kowalczyk
1451a52a38 Remove myself (fuuzetsu) from maintainer lists
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.
2019-12-05 16:29:48 +09:00
volth
46420bbaa3 treewide: name -> pname (easy cases) (#66585)
treewide replacement of

stdenv.mkDerivation rec {
  name = "*-${version}";
  version = "*";

to pname
2019-08-15 13:41:18 +01:00
R. RyanTM
b063dc8557 gpgme: 1.13.0 -> 1.13.1
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
2019-06-16 18:03:24 -07:00
Dmitry Kalinkin
f19a36f524
gpgme: disable tests on darwin 2019-06-07 16:03:51 -04:00
c0bw3b
9cb260d091 [treewide] delete unused patches 2019-05-04 19:52:24 +02:00
Will Dietz
5c280ce1e4 gpgme: 1.12.0 -> 1.13.0
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.
2019-03-26 13:23:54 -05:00
Michael Eden
aefea5f0bd gpgme: cross compilation 2019-03-21 10:33:30 -04:00
Michael Weiss
399761ea0a
gpgme: Update the URL for fix-key-expiry.patch
The old URL was gone, see:
https://github.com/NixOS/nixpkgs/pull/53693#pullrequestreview-195177688

Thanks @volth :)
2019-01-24 17:24:18 +01:00
Tor Hedin Brønner
96bfa25500 libsForQt5.qgpgme: fix tests after 2019-01-06
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
2019-01-09 09:19:30 +01:00
Matthieu Coudron
3902b3f4e7 python3Packages.gpgme: enable python3 version
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
2018-10-19 14:20:08 +09:00
Will Dietz
c02fc32e1d gpgme: enable tests, they pass! :) 2018-10-12 21:45:02 -05:00
Will Dietz
6424a1425c gpgme: 1.11.1 -> 1.12.0
https://lists.gnupg.org/pipermail/gnupg-announce/2018q4/000429.html
2018-10-09 17:40:54 -05:00
Jan Malakhovski
53c9efe9e5 gpgme: use default texinfo 2018-09-08 23:04:55 +00:00
John Ericson
2c2f1e37d4 reewide: Purge all uses stdenv.system and top-level system
It is deprecated and will be removed after 18.09.
2018-08-30 17:20:32 -04:00
Jan Malakhovski
97aa8b164e gpgme: make tests run, but disable. Spooky! 2018-08-11 09:35:30 +00:00
volth
52f53c69ce pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
Michael Weiss
f76c842706 gpgme: 1.10.0 -> 1.11.1
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-04-21 23:25:14 +02:00
Matthieu Coudron
a8403b64f8 gpgme: add withPython ? false to enable bindings
Useful for MUAs mostly, like alot
2018-03-21 10:21:39 +09:00
Matthieu Coudron
d9292429e7 alot: 0.5.1 to 0.7.0
- 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.
2018-03-21 10:21:38 +09:00
Michael Weiss
41a4bded9b gpgme: 1.9.0 -> 1.10.0
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-12-14 13:49:00 +01:00
Thomas Tuegel
5ba0dd1ad7
qgpgme: build with -DQT_NO_DEBUG
qgpgme uses Q_ASSERT which causes build inputs to be retained unnecessarily at
runtime unless debugging is disabled.
2017-08-21 06:51:32 -05:00
Silvan Mosberger
f5fa5fa4d6 pkgs: refactor needless quoting of homepage meta attribute (#27809)
* 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-08-01 22:03:30 +02:00
Thomas Tuegel
f5c00c43bb
qgpgme: init at 1.9.0 2017-06-18 08:44:44 -05:00
Jos van den Oever
05ef92e53a
gpgme: enable Qt 5 bindings 2017-06-18 08:44:44 -05:00
Michael Weiss
40d171855f gpgme: 1.8.0 -> 1.9.0
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-04-02 01:26:22 +02:00
Michael Weiss
4e29638323 Revert "gpgme: Drop multiple outputs (dev and info)"
This reverts commit 872770286d.

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-21 23:57:57 +01:00
Michael Weiss
872770286d gpgme: Drop multiple outputs (dev and info)
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-03-21 22:43:00 +01:00
Ignat Loskutov
d1a9f2e8be gpgme: fix build on macOS 2017-02-16 01:13:23 +03:00
Franz Pletz
403432f6ab
gpgme: 1.7.0 -> 1.8.0 2017-01-30 01:15:22 +01:00
Thomas Tuegel
da9c6a7744
gpgme: fix build on i686-linux 2016-10-10 13:37:24 -05:00
Franz Pletz
81bb09541c
gpgme: 1.6.0 -> 1.7.0 2016-09-24 21:55:34 +02:00
Tuomas Tynkkynen
a17216af4c treewide: Shuffle outputs
Make either 'bin' or 'out' the first output.
2016-08-29 14:49:51 +03:00
Vladimír Čunát
ae74c356d9 Merge recent 'staging' into closure-size
Let's get rid of those merge conflicts.
2016-02-03 16:57:19 +01:00
aszlig
39a07cabe8
gpgme: Use fixed path for GnuPG binaries
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>
2016-01-21 01:39:18 +01:00
Vladimír Čunát
f8ce44d518 gpgme: split dev and info outputs 2015-10-13 20:19:00 +02:00