Re: Python3.6 plans​ for Buster

2017-06-16 Thread Steve Langasek
On Fri, Jun 16, 2017 at 10:23:06PM -0700, Steve Langasek wrote:
> [1] pytables is a failure specific to Ubuntu armhf buildds which raise
> SIGBUS, this should not affect Debian.  python-astropy rebuilds with no
> problem, but doesn't pick up python3.6 support.

To clarify: python-astropy builds an astropy-utils package that winds up
with /usr/bin/python3.5 as an interpreter instead of /usr/bin/python3.  So
that's a bug, and worth fixing, but it seemed non-trivial and the package
could be dealt with by just having one extra no-change rebuild later in the
transition.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature


Python3.6 plans​ for Buster

2017-06-16 Thread Scott Kitterman
Python3.6 is already in Unstable and I expect to see it in Testing soon after 
Stretch is released.

I've just now uploaded a version of python3-defaults to Experimental that adds 
python3.6 as as supported (but not default) python3.  If you have binary 
extensions packaged, please start testing with this version to make sure your 
package builds correctly with both python3.5 and python3.6 as supported.

As a reminder (and for anyone new) we'll do the transition to python3.6 in 
three stages:

 - Add python3.6 as supported and rebuild all binary extensions to support both 
python3.5 and python3.6

 - Switch to python3.6 as default

 - Drop python3.5 from supported and rebuild again to remove python3.5 support.

Last time I compared my understanding of the Buster schedule with the python3.7 
schedule, I recall concluding that we'd likely be on python3.6 for the Buster 
release (not sure that's still true).  If so, we only have to do this once this 
cycle and​I think the sooner the better.

Scott K



Re: Problem backporting python-pyvcf

2017-06-16 Thread Graham Inggs
Hi Andreas

Try the following in debian/rules:

export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie



Bug#864887: ITP: python-django-netfields -- Django PostgreSQL netfields implementation

2017-06-16 Thread Michael Fladischer
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-django-netfields
  Version : 0.7
  Upstream Author : James Oakley 
* URL : https://github.com/jimfunk/django-postgresql-netfields/
* License : BSD-3-clause
  Programming Lang: Python
  Description : Django PostgreSQL netfields implementation

 This project is an attempt at making proper PostgreSQL net related fields for
 Django. In Django pre 1.4 the built in IPAddressField does not support IPv6 and
 uses an inefficient HOST() cast in all lookups. As of 1.4 you can use
 GenericIPAddressField for IPv6, but the casting problem remains.
 .
 In addition to the basic IPAddressField replacement a CIDR and a MACADDR field
 have been added. This library also provides a manager that allows for advanced
 IP based lookup directly in the ORM.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAllD55URHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WoHBwgAqp0kK185VilKQG3ymoNydm8k58roOsdI
oRQkzBXVA0YEHw4KxqK7L1eu77En3oddKZzDtr4izHPJPWZo5CDPpMBOfkScnANN
59SnxjHPCVWVYZ/4g6B4EOPLO6t+XYLk+Ukp7dwg02mAxUS/VrSmq/E0izP0Z/4f
3zR12542hxN8J8OsTc1l2rbQ7a0LAgBvYqfZRyNkzPkepcmH1CjGFTD2u1I66CVq
AFqh7PQku3WShpKDeEleamcoivzVCOO0d9DOz1D/kuWy/2pBA6M9ssERs0yGOSkO
EyzqiZfenml/i0LF6ZZ6oa/MJq5fDWyo9b4J0jW9NtpNDHTSHzkduA==
=6jfw
-END PGP SIGNATURE-



Problem backporting python-pyvcf

2017-06-16 Thread Andreas Tille
Hi,

I tried to upgrade the Jessie backport of python-pyvcf from
0.6.7-1~bpo8+1 to 0.6.8-1.  Unfortunately when trying to build this
minor update the build runs into lots of errors like:

...
creating build/temp.linux-amd64-2.7
creating build/temp.linux-amd64-2.7/vcf
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c 
vcf/cparse.c -o build/temp.linux-amd64-2.7/vcf/cparse.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat 
-Werror=format-security -fPIE -pie -Wl,-z,relro -Wl,-z,now -g -O2 -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 
build/temp.linux-amd64-2.7/vcf/cparse.o -o 
/build/python-pyvcf-0.6.8/.pybuild/pythonX.Y_2.7/build/vcf/cparse.so
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/Scrt1.o: In 
function `_start':
(.text+0x20): undefined reference to `main'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function 
`__Pyx_PyFunction_FastCallNoKw':
/build/python-pyvcf-0.6.8/vcf/cparse.c:2681: undefined reference to 
`_PyThreadState_Current'
/build/python-pyvcf-0.6.8/vcf/cparse.c:2691: undefined reference to 
`PyFrame_New'
/build/python-pyvcf-0.6.8/vcf/cparse.c:2700: undefined reference to 
`PyEval_EvalFrameEx'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function `__Pyx_AddTraceback':
/build/python-pyvcf-0.6.8/vcf/cparse.c:3732: undefined reference to 
`_PyThreadState_Current'
/build/python-pyvcf-0.6.8/vcf/cparse.c:3732: undefined reference to 
`PyFrame_New'
/build/python-pyvcf-0.6.8/vcf/cparse.c:3740: undefined reference to 
`PyTraceBack_Here'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function 
`__Pyx_CreateCodeObjectForTraceback':
/build/python-pyvcf-0.6.8/vcf/cparse.c:3676: undefined reference to 
`PyString_FromString'
/build/python-pyvcf-0.6.8/vcf/cparse.c:3683: undefined reference to 
`PyString_FromFormat'
/build/python-pyvcf-0.6.8/vcf/cparse.c:3676: undefined reference to 
`PyString_FromString'
/build/python-pyvcf-0.6.8/vcf/cparse.c:3690: undefined reference to 
`PyString_FromString'
/build/python-pyvcf-0.6.8/vcf/cparse.c:3696: undefined reference to `PyCode_New'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function `__pyx_insert_code_object':
/build/python-pyvcf-0.6.8/vcf/cparse.c:3648: undefined reference to 
`PyMem_Realloc'
/build/python-pyvcf-0.6.8/vcf/cparse.c:3628: undefined reference to 
`PyMem_Malloc'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function 
`__Pyx_RaiseArgtupleInvalid':
/build/python-pyvcf-0.6.8/vcf/cparse.c:2899: undefined reference to 
`PyExc_TypeError'
/build/python-pyvcf-0.6.8/vcf/cparse.c:2899: undefined reference to 
`PyErr_Format'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function `__Pyx_SetItemInt_Fast':
/build/python-pyvcf-0.6.8/vcf/cparse.c:3296: undefined reference to 
`PyInt_FromSsize_t'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function `__Pyx_SetItemInt_Generic':
/build/python-pyvcf-0.6.8/vcf/cparse.c:3255: undefined reference to 
`PyObject_SetItem'
build/temp.linux-amd64-2.7/vcf/cparse.o: In function 
`__Pyx_PyFunction_FastCallDict':
...


and so on (errors are continuing).  Does anybody have an idea what might
went wrong here under Jessie which builds nicely under Stretch or should
I post a full build log?

Kind regards

  Andreas.

-- 
http://fam-tille.de