Actually I recently changed it to detect misconfigured cross-platform build
systems. All the m4 files are chnage from time to time; it is the same as with
libtool or config.guess.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 8 2011
Apr 4 2011
Well, so be it then. I can't say I understand the decision (have you considered those
who don't need that unnecessary flexibility?), but I guess I'll just have to continue
shipping gpgme.m4 within the geany-plugins autofoo buildsys. The waf buildsys will just
have to reimplement the check. I don't look forward to the day that you guys decide to
change gpgme.m4 though, assuming that ever happens.
If you use CMAKE, you need to write your own test. gpgme-config provides all
what you need.
Mar 30 2011
That's the current approach I'm using, but like I said in the first message, it
feels ugly and hackish.
Okay, I now see what you mean.
autoconf.sh is a mainatiner tool and not a distribution. If your application
uses gpgme, I suggest to distribute the gpgme.m4 in the m4 directory.
I don't understand what you mean. gpgme.m4 gets installed my gpgme and thus the
AM_PATH_GPGME macro is available. There will be no pkg-config support, becuase
cusom config files are more flexible.
Mar 29 2011
Feb 21 2011
Please try a decent version of GPGME before entering an entry into the BTS.
Jan 7 2011
Fixed in 3a7058c
Dec 27 2010
Aug 19 2010
Aug 17 2010
May 7 2010
1467 has an improved check.
libassuan is a hard requirement for gpgme since version 1.3. And yes, configure
should complain about it.
May 2 2010
Feb 24 2010
Marcus, can you please take care of this.
Feb 22 2010
Feb 11 2010
Marcus, plase have a look at it.
Feb 10 2010
Feb 9 2010
Marcus, please add a note that the GnuPG documentation is the only specification
for key parameters. And change the example so that it works with the new
default feature of gpg.
Feb 8 2010
Feb 2 2010
Ah right. Apologies for my ignorance.
Jan 29 2010
Anyways, I can provide a gpgme trace at level 9 if you consider it necessary.
Hello Werner.
Frankly, I can only guess what you are doing. Is that a seahorse action to add
another user id or an existing key? A backtrace does not help at all here.
Jan 11 2010
Marcus, not yet so far. I would appreciate a test on your end, as I might not
get to the issue for a while. There should be enough information to reproduce
the issue.
Jan 8 2010
Hi Bernhard,
Dec 21 2009
ping
Please give a detailed report, I can't do much with the brief comments in your
repo. Note that gpg1 and gpg2 are slighly different and thus in corener cases
you may get different error codes.
Dec 17 2009
fixed in rev 1442, thanks for reporting it
Closing the report, if it is still an issue it can be reopened.
Dec 16 2009
I've tried to reproduce the fault with 1.2.0 but could not so it seems to be
fixed.
Thanks.
Is there any way we can make process on this one? Is it still an issue?
I think that this is probably fixed in the gpgme 1.2.0 release. The following
patch by Werner has a similar effect to the patch provided by the submitter:
Nov 26 2009
Why "make it fail"; why not "make it run"?
I guess (did not test) that the bug can be fixed by replacing
#if @NEED__FILE_OFFSET_BITS@
with
#if @NEED__FILE_OFFSET_BITS@ - 0
or by making configure always setting a nonempty value;
depending on your preferred style of programming.
Marcus, please make it fail more gracefully.
Nov 19 2009
Nov 11 2009
Is there any chance of getting this fixed? The problem is very annoying as it
causes the library to disturb the application using it and I can't think of any
simple workaround for it.
The patch is just three lines so it should be easy to include, right?
Nov 4 2009
It's more complicated, as the same code works when engine is set explicitely to
gpg2 but the gpg1 engine return a no error data.
You passed no data to the fucntion. Please ask on gnupg-users for help.
Oct 27 2009
Aug 28 2009
Marcus: I recall that you recently changed something in the cancel code - is
that his problem?
Aug 26 2009
Aug 13 2009
Quite right, claws actually does invoke AC_SYS_LARGEFILE.
Aug 11 2009
Sorry, typo in the URL, (there was one "kolab/" too much, but you could have
gotten to it via the main page. :) )
https://www.intevation.de/roundup/kolab/issue3583 (offline s/mime signing
without CRL for secret key gives unkown system error)
Sorry for the delay. I can not access the kolab tracker (404), has the link
changed? Errors for individual keys in a keylisting are not available in
detail, but only the invalid flag is set. When using an invalid key, a more
detailed reason may be available. There is currently no way to get more
detailed reasons about why a key in a key listing is invalid.
Aug 10 2009
Aug 3 2009
I see. Your plaintext needs to be zeroized after decryption and processing by
you. gpgme does not directly support this. What you can do for data objects
hold in memory is: