Bug#665731: New upstream version, and questions about patches

2013-08-08 Thread Simon Chopin
Package: python-gpgme
Followup-For: Bug #665731

Any news on this?


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#665731: New upstream version, and questions about patches

2012-03-25 Thread James Henstridge
Package: python-gpgme

Hi,

I'm the upstream maintainer for pygpgme, and thought you might want to
know that there is a new release available now:

https://launchpad.net/pygpgme/trunk/0.3

The main new feature of this release is compatibility with Python 3.x
in addition to Python 2.x (the same setup.py should build the
extension on both versions).


I also went through the distro patches in the latest package, and had
a few comments:

1) fix_context_initialization
This bug was fixed in 0.2 by adding the gpgme_check_version() to the
module initialisation routine, so this patch could be dropped.

2) testsuite-all-versions
If you want to use the make file to run the test suite, you should be
able to override the interpreter by running make PYTHON=python3.2
check.  This should work without the patch.

3) lfs-support
Does this patch actually change the behaviour of the module?  I was
looking through all the source files, and they should be including
Python.h first, which will set _FILE_OFFSET_BITS=64 if the
interpreter has been configured with large file support.  I'd prefer
not to hard code something like this unless necessary.

Thanks,

James Henstridge.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org