Closing the report about porting to a non-supported target.

The makefile looks portable to me. As there was no feedback for two years, I am
closing the report. Please reopen with more details if the problem persists.

This can't be done any better, so closing the report.

Closing this vague report of something that's most certainly not an issue anymore.

Actually, gpg can not do much if configuration options can't be parsed. GPGME
does not see the exit code due to the double-fork approach.

In principle, this can happen on Un*x systems, too. There is no guarantee about
the filesystem encoding. Glib has special interfaces for filename conversion
(G_FILENAME_ENCODING) to deal with this.

Closing this report which has no activity for 5 years.

Closing this report, as nothing happened in half a year with regards to the
finnish translation.

This is a good feature request, but it requires some coding to make it work. I
think that this should be done via a context popup menu on the keylisting
entries (in addition to a menu entry).

Fixed now.

Mirror doesn't exist anymore. Closing the report.

Closing this report. If further support is required, please reopen.

I can not reproduce this. The file downloads and unpacks fine for me. I get a
different md5sum, too: 8ee26d7fe829e81eb8bce2d974a7c500 gpa-0.7.6.tar.bz2

I put the new fr.po into SVN. Thanks for all your work! Marcus

I put the changes in SVN. The POTFILES.in changes seem already to be in there.
I also put a translation domain for the action group in recipientdlg.c. I hope
that's allright.

I put it in SVN. Thanks for your help!

Thanks, I put the version in #975 into SVN.

Duplicate of T975

Note: It also works for gpgme_op_decrypt_verify, but the error code
GPG_ERR_NO_DATA needs to be ignored in this case. This is because we didn't get
a DECRYPTION_OKAY status message, and this is semantically the same as for a
signed but not decrypted file. We can consider making this case better in a
major upgrade when we change the ABI anyway, but not now.

Works fine for me with gpgme_op_verify, which actually runs the gpgme -o command
as you gave it. Did you rewind the output data object before trying to
read the data?

The problem is that the changes only take effect if the user presses return in
the entry field of the combo box. I just applied a change that puts the change
to effect on every focus-out-event, which seems to match what the Human
Interface Guide of GNOME suggests.

great that you could find the problem! closing the report.

Fixed in revision 833. Can you please confirm this?

I added a comment for the unit. Thanks.

I applied the patch. Thanks!

Another suggestion is to run with GPGME_DEBUG=9 in a console and see what the
error reported by the engine is. Also, check if you can run gpg/gpgsm with the
intended operations on the command line.

I can not reproduce this with gpa 0.7.6. Can you try the GPA contained in
gpg4win 1.1.3?

You could try to debug GNUPG ((set debug-file and debug-level=guru option).
Maybe that reveals something.

Do you mean it fails with the exact name and email address you gave below? If
not, what special characters occur in your name/email address?

The key 87978569 is mine. The other's is Werner's. A new key from Werner that
is not expired is available on the webpage you link. I consider this fixed.

It does list the latest GPGME 1.1.4 release now. Thank you.

Fixed, thank you.

I fixed it, thank you.

Fixed now.

I can't reproduce this with the SVN version of GPA and GNU/Linux as target. Are
you using GNU/Linux as well? Can you try the SVN version?

I put the status to deferred, as the final decision to keep or remove
gpgme_data_seek will be done when the other deprecated interfaces will be removed.

Found it. It used PACKAGE, not PACKAGE_GT, thereby using the wrong po file,
messing things up.

The problem is that gpg2 sends the translated string for "Enter passphrase: " in
ISO8859-1 (?) to the gpg-agent, although we specified that all internal
communication should be in UTF-8. pinentry then tries to translate that string
to ISO8859-1 again, which obviously fails.

No further feedback, so setting to resolved.

Thanks for the detailed report. I put in your fix (with minor cosmetic
corrections). As for the prototype ttyname_r: I hesitate to put any of the
_SOURCE_ macros in the build unconditionally, as this may trigger other issues.
If you give me the output of ./config.guess on your platform, I will put it in
for that platform (please also verify if defining any of these results in a
proper working build.)

I checked it in for now.

This patch fixes the issue for me. It adds status writes for MISSING_PASSPHRASE
in the cancellation case. One of the main gpg developers should review the
patch, though, because the code flow is (overly?) complex already and there may
be a way to do this better.

D38: 122_gpg-cancel.diff