[Python-modules-team] Bug#629699: webhelpers: FTBFS: test_distance_of_time_in_words

2012-01-02 Thread Matthias Klose
the Fedora patch is not enough, it fails later with:

==
ERROR: test_mimetypes.test_root_path
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 187, in runTest
self.test(*self.arg)
  File "/home/packages/tmp/webhelpers-1.3/tests/test_mimetypes.py", line 36, in
test_root_path
eq_(m.mimetype('text/html'), 'text/html')
  File "/home/packages/tmp/webhelpers-1.3/webhelpers/mimehelper.py", line 114,
in mimetype
self.env['HTTP_ACCEPT'])
TypeError: __init__() takes exactly 2 arguments (3 given)

==
ERROR: test_mimetypes.test_with_extension
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 187, in runTest
self.test(*self.arg)
  File "/home/packages/tmp/webhelpers-1.3/tests/test_mimetypes.py", line 44, in
test_with_extension
eq_(m.mimetype('text/html'), False)
  File "/home/packages/tmp/webhelpers-1.3/webhelpers/mimehelper.py", line 114,
in mimetype
self.env['HTTP_ACCEPT'])
TypeError: __init__() takes exactly 2 arguments (3 given)

==
ERROR: test_mimetypes.test_with_unregistered_extention
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 187, in runTest
self.test(*self.arg)
  File "/home/packages/tmp/webhelpers-1.3/tests/test_mimetypes.py", line 53, in
test_with_unregistered_extention
eq_(m.mimetype('text/html'), False)
  File "/home/packages/tmp/webhelpers-1.3/webhelpers/mimehelper.py", line 114,
in mimetype
self.env['HTTP_ACCEPT'])
TypeError: __init__() takes exactly 2 arguments (3 given)

==
ERROR: test_mimetypes.test_root_path
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 187, in runTest
self.test(*self.arg)
  File "/home/packages/tmp/webhelpers-1.3/tests/test_mimetypes.py", line 36, in
test_root_path
eq_(m.mimetype('text/html'), 'text/html')
  File "/home/packages/tmp/webhelpers-1.3/webhelpers/mimehelper.py", line 114,
in mimetype
self.env['HTTP_ACCEPT'])
TypeError: __init__() takes exactly 2 arguments (3 given)

==
ERROR: test_mimetypes.test_with_extension
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 187, in runTest
self.test(*self.arg)
  File "/home/packages/tmp/webhelpers-1.3/tests/test_mimetypes.py", line 44, in
test_with_extension
eq_(m.mimetype('text/html'), False)
  File "/home/packages/tmp/webhelpers-1.3/webhelpers/mimehelper.py", line 114,
in mimetype
self.env['HTTP_ACCEPT'])
TypeError: __init__() takes exactly 2 arguments (3 given)

==
ERROR: test_mimetypes.test_with_unregistered_extention
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 187, in runTest
self.test(*self.arg)
  File "/home/packages/tmp/webhelpers-1.3/tests/test_mimetypes.py", line 53, in
test_with_unregistered_extention
eq_(m.mimetype('text/html'), False)
  File "/home/packages/tmp/webhelpers-1.3/webhelpers/mimehelper.py", line 114,
in mimetype
self.env['HTTP_ACCEPT'])
TypeError: __init__() takes exactly 2 arguments (3 given)



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#691254: Fix ftbfs with python3.3 multiarch setup

2012-10-23 Thread Matthias Klose
Source: python-scipy
Version: 0.10.1+dfsg1-4
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python3.3
Tags: patch

patch at
http://launchpadlibrarian.net/120798860/python-scipy_0.10.1%2Bdfsg1-4_0.10.1%2Bdfsg1-4ubuntu1.diff.gz

please don't be fooled by the wrong changelog entry.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#691251: python3.3 compatibility (No such file or directory: '/home/yoh/python-env/python3.3/bin/easy_install')

2012-10-23 Thread Matthias Klose
On 23.10.2012 16:41, Yaroslav Halchenko wrote:
[...]

please note that python3.3 comes with its own pyvenv-3.3

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#691241: fix ftbfs with multiple python3 versions, and fix a python3.3 issue

2012-10-23 Thread Matthias Klose
Source: py3cairo
Version: 1.10.0+dfsg-3~exp2
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: python3.3
Tags: patch

patch at
http://launchpadlibrarian.net/120606963/py3cairo_1.10.0%2Bdfsg-3~exp2_1.10.0%2Bdfsg-3~exp2ubuntu1.diff.gz

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#686871: add patch

2013-02-19 Thread Matthias Klose
tag 686871 + patch
thanks

patch at
http://launchpadlibrarian.net/131660345/python-kyotocabinet_1.22-1_1.22-1ubuntu1.diff.gz

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#707805: Please drop python2.6-argparse build-dependency

2013-05-16 Thread Matthias Klose
Control: severity -1 serious

Removing the dependency, the packages fails to build from source:

make[1]: Entering directory `/home/packages/tmp/sorl-thumbnail-11.12'
mkdir -p tmp-locales
localedef -i en_US -c -f UTF-8 tmp-locales/en_US.UTF-8
set -e; \
for python in python2.7; do \
  for name in pil pgmagick imagemagick graphicsmagick; do \
LOCPATH=/home/packages/tmp/sorl-thumbnail-11.12/tmp-locales
LC_ALL=en_US.UTF-8 PYTHONPATH=tests LOCAL_BUILD=1 $python tests/runtests.py
--settings=settings.$name ; \
  done; \
done
Traceback (most recent call last):
  File "tests/runtests.py", line 53, in 
settings_module=args.settings_module,
  File "tests/runtests.py", line 13, in runtests
from django.test.utils import get_runner
  File "/usr/lib/python2.7/dist-packages/django/test/__init__.py", line 5, in

from django.test.client import Client, RequestFactory
  File "/usr/lib/python2.7/dist-packages/django/test/client.py", line 21, in

from django.db import close_connection
  File "/usr/lib/python2.7/dist-packages/django/db/__init__.py", line 11, in

if settings.DATABASES and DEFAULT_DB_ALIAS not in settings.DATABASES:
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 53, in
__getattr__
self._setup(name)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 48, in
_setup
self._wrapped = Settings(settings_module)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 152, in
__init__
raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be
empty.
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory `/home/packages/tmp/sorl-thumbnail-11.12'
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#560918: Bug#560912: Expat issues update

2009-12-13 Thread Matthias Klose

On 13.12.2009 16:29, Michael Gilbert wrote:

Hi all,

In order to guarantee that the system expat is used, the
'--with-expat=sys' configure argument must be used.  If you think
your package is already using the system expat, or if you are updating
your package to use the system expat, please check to make sure that
this option is being used. Thanks.


there's no such option for python, which uses a modified copy of expat.




___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#565068: pyxine: ftbfs with gcc-4.5

2010-01-12 Thread Matthias Klose
Package: pyxine
Version: 0.1alpha2-6
Severity: normal
Tags: sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-4.5

The package fails to build in a test rebuild on at least amd64 with
gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4.
For the compiler version used, see:
http://lists.debian.org/debian-devel/2010/01/msg00230.html

The full build log can be found at:
http://people.debian.org/~lucas/logs/2010/01/08b/pyxine_0.1alpha2-6_lsid64b.buildlog
The last lines of the build log are cwat the end of this report.

The reason of the build failure is likely in the package (compiler or
linker message found in the build log), if this turns out as a gcc bug,
please reassign to the gcc-4.5 package. If the build ends with a
message "confused by earlier errors, bailing out", please
ignore it for now; these compiler errors are filed separately.


[...]
gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -Wall -g -O2 
-fPIC -I/usr/include/python2.5_d -c pxlib/Mutex.cc -o 
build/temp_d.linux-x86_64-2.5/pxlib/Mutex.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -Wall -g -O2 
-fPIC -I/usr/include/python2.5_d -c pxlib/Thread.cc -o 
build/temp_d.linux-x86_64-2.5/pxlib/Thread.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -Wall -g -O2 
-fPIC -I/usr/include/python2.5_d -c pxlib/XDisplay.cc -o 
build/temp_d.linux-x86_64-2.5/pxlib/XDisplay.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -Wall -g -O2 
-fPIC -I/usr/include/python2.5_d -c pxlib/Traits.cc -o 
build/temp_d.linux-x86_64-2.5/pxlib/Traits.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
In file included from /usr/include/python2.5_d/Python.h:8:0,
 from pxlib/Traits.h:31,
 from pxlib/Traits.cc:24:
/usr/include/python2.5_d/pyconfig.h:970:0: warning: "_POSIX_C_SOURCE" redefined
/usr/include/features.h:158:0: note: this is the location of the previous 
definition
/usr/include/python2.5_d/pyconfig.h:982:0: warning: "_XOPEN_SOURCE" redefined
/usr/include/features.h:160:0: note: this is the location of the previous 
definition
gcc -pthread -fno-strict-aliasing -g -Wall -Wstrict-prototypes -Wall -g -O2 
-fPIC -I/usr/include/python2.5_d -c pxlib/Callback.cc -o 
build/temp_d.linux-x86_64-2.5/pxlib/Callback.o
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
Ada/C/ObjC but not for C++
In file included from /usr/include/python2.5_d/Python.h:8:0,
 from pxlib/Traits.h:31,
 from pxlib/Callback.h:30,
 from pxlib/Callback.cc:25:
/usr/include/python2.5_d/pyconfig.h:970:0: warning: "_POSIX_C_SOURCE" redefined
/usr/include/features.h:158:0: note: this is the location of the previous 
definition
/usr/include/python2.5_d/pyconfig.h:982:0: warning: "_XOPEN_SOURCE" redefined
/usr/include/features.h:160:0: note: this is the location of the previous 
definition
pxlib/Callback.cc:87:1: error: 'pyxine::PythonContext::PythonContext' names the 
constructor, not the type
error: command 'gcc' failed with exit status 1
[20198 refs]
make: *** [install] Error 1
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary gave error exit 
status 2



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#578327: os.execlp takes at least two parameters

2010-04-18 Thread Matthias Klose

Package: skype4py
Version: 1.0.31.0-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu

Found via archive scan:

 ./skype4py-1.0.31.0/Skype4Py/API/posix_dbus.py:
os.execlp('skype')
 ./skype4py-1.0.31.0/Skype4Py/API/posix_x11.py:
os.execlp('skype')

with just one arg, it would crash earlier python versions, now raises an 
exception. just repeat the program name as a second arg.




___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#596313: python-multiprocessing: python2.5-dev used as build-dependency, not python-dev or python2.6-dev

2010-09-10 Thread Matthias Klose
Package: python-multiprocessing
Version: 2.6.2.1-4
Severity: serious
User: debian-pyt...@lists.debian.org
Usertag: python2.6

The package build-depends on python2.5-dev, which is not the default
python version for squeeze.  The package should be rebuilt with
python2.6, either build-depending on python-dev (recommended) or
python2.6-dev.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#596313: python2.5-dev used as build-dependency, not python-dev or python2.6-dev)

2010-09-10 Thread Matthias Klose

severity 596313 important
thanks

only serious when python2.5 gets removed.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#597099: build a python3-xdg package (using debhelper v7)

2010-09-16 Thread Matthias Klose

Package: pyxdg
Version: 0.19-2
Tags: patch

attached is a patch to build a python3-xdg package; I have no interest in pyxdg 
itself, just took it as an example for a package using debhelper v7.


The required changes are:

 - Build-depend on the python3-* packages corresponding to the
   existing python-* dependencies.

 - python3-* binary package entry in the control file.

 - Use of distribute/setuptools instead of distutils to automagically
   call 2to3 for the source code conversion.  Please check the
   converted code before uploading a package.

 - Add .install files, now necessary, because two binary packages
   are built.

 - Call dh with the option `--with python3'.  The python-xdg package
   could be built using dh_python2 too. In that case call dh with
   `--with python2,python3' and remove the build dependency on
   python-support.

 - Provide override targets for dh_auto_clean, dh_auto_build and
   dh_auto_install.


Required build dependencies can be found in experimental.  Please consider 
uploading the package to experimental, and/or later to sid. The release team 
will consider freeze exceptions for python3-* packages. See

http://lists.debian.org/debian-python/2010/09/msg00021.html

diff -Nru pyxdg-0.19/debian/changelog pyxdg-0.19/debian/changelog
--- pyxdg-0.19/debian/changelog 2010-06-23 16:55:34.0 +0200
+++ pyxdg-0.19/debian/changelog 2010-09-15 18:50:19.0 +0200
@@ -1,3 +1,9 @@
+pyxdg (0.19-2.1) experimental; urgency=low
+
+  * Build a python3-xdg package.
+
+ -- Matthias Klose   Wed, 15 Sep 2010 18:49:43 +0200
+
 pyxdg (0.19-2) unstable; urgency=low
 
   * Fix case when $XDG_*_HOME is empty (fix-BaseDirectory-cornercase.patch)
diff -Nru pyxdg-0.19/debian/control pyxdg-0.19/debian/control
--- pyxdg-0.19/debian/control   2010-01-28 11:47:59.0 +0100
+++ pyxdg-0.19/debian/control   2010-09-16 16:55:04.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian Python Modules Team 

 Uploaders: Piotr Lewandowski 
-Build-Depends: debhelper (>= 7), python-support
+Build-Depends: debhelper (>= 7), python-support, python3-all (>= 3.1.2-10~), 
python-setuptools, python3-setuptools
 Standards-Version: 3.8.4
 Vcs-Browser: http://svn.debian.org/viewsvn/python-modules/packages/pyxdg/trunk/
 Vcs-Svn: svn://svn.debian.org/python-modules/packages/pyxdg/trunk/
@@ -21,3 +21,16 @@
   * Icon Theme Specification Version 0.8
   * Recent File Spec 0.2
   * Shared-MIME-Database Specification 0.13 
+
+Package: python3-xdg
+Architecture: all
+Depends: ${misc:Depends}, ${python3:Depends}
+Description: Python3 library to access freedesktop.org standards
+ PyXDG contains implementations of freedesktop.org standards in Python:
+ .
+  * Base Directory Specification Version 0.6
+  * Menu Specification Version 1.0-draft1
+  * Desktop Entry Specification Version 1.0
+  * Icon Theme Specification Version 0.8
+  * Recent File Spec 0.2
+  * Shared-MIME-Database Specification 0.13 
diff -Nru pyxdg-0.19/debian/patches/series pyxdg-0.19/debian/patches/series
--- pyxdg-0.19/debian/patches/series2010-06-22 16:40:52.0 +0200
+++ pyxdg-0.19/debian/patches/series2010-09-16 16:57:22.0 +0200
@@ -4,3 +4,4 @@
 fix-BaseDirectory-empty-vars.patch
 fix-583497.patch
 fix-string-exceptions.patch
+setup-2to3.patch
diff -Nru pyxdg-0.19/debian/patches/setup-2to3.patch 
pyxdg-0.19/debian/patches/setup-2to3.patch
--- pyxdg-0.19/debian/patches/setup-2to3.patch  1970-01-01 01:00:00.0 
+0100
+++ pyxdg-0.19/debian/patches/setup-2to3.patch  2010-09-16 16:54:24.0 
+0200
@@ -0,0 +1,18 @@
+--- pyxdg-0.19.orig/setup.py
 pyxdg-0.19/setup.py
+@@ -1,6 +1,7 @@
+ #!/usr/bin/python
+ 
+-from distutils.core import setup
++import sys
++from setuptools import setup
+ 
+ setup( name = "pyxdg",
+version = "0.19",
+@@ -9,5 +10,5 @@ setup( name = "pyxdg",
+maintainer_email = "h_wen...@cojobo.net",
+url = "http://cvs.freedesktop.org/cgi-bin/viewcvs.cgi/pyxdg/";,
+packages = ['xdg'],
+-   license = "LGPL-2")
++   license = "LGPL-2", use_2to3=sys.version_info >= (3, 0))
+ 
diff -Nru pyxdg-0.19/debian/python3-xdg.install 
pyxdg-0.19/debian/python3-xdg.install
--- pyxdg-0.19/debian/python3-xdg.install   1970-01-01 01:00:00.0 
+0100
+++ pyxdg-0.19/debian/python3-xdg.install   2010-09-15 18:55:22.0 
+0200
@@ -0,0 +1 @@
+usr/lib/python3
diff -Nru pyxdg-0.19/debian/python-xdg.install 
pyxdg-0.19/debian/python-xdg.install
--- pyxdg-0.19/debian/python-xdg.install1970-01-01 01:00:00.0 
+0100
+++ pyxdg-0.19/debian/python-xdg.install2010-09-15 18:55:01.0 
+0200
@@ -0,0 +1 @@
+usr/lib/python2*
diff -Nru pyxdg-0.19/debian/rules pyxdg-0.19/debian/rules
--- pyxdg-0.19/debian/rules 2009-12-09 21:11:54.0 +0100
+++ pyxdg-0.19/debian/rules 2010-09-16 16:57:45.0 +0200
@@ -1,4 +

[Python-modules-team] binary packages with explicit python2.5 build dependency

2010-09-26 Thread Matthias Klose
Sent to you as a package maintainer or an uploader for one
of the packages mentioned at

  http://lists.debian.org/debian-release/2010/09/msg01832.html

At least one of the binary packages built by these source packages
ends up with a dependency, recommendation or suggestion on python2.5
without having an explicit build dependency on python2.5 or python2.5-dev.

Please fix this without reintroducing explicit build depedencies on
python2.5 or python2.5-dev, if possible.

Thanks, Matthias

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#565068: pyxine: ftbfs with gcc-4.5

2010-12-05 Thread Matthias Klose

tag 565068 + patch
user ubuntu-de...@lists.ubuntu.com
usertags 565068 + origin-ubuntu natty ubuntu-patch
thanks

patch at:
http://launchpadlibrarian.net/60145393/pyxine_0.1alpha2-6build1_0.1alpha2-6ubuntu1.diff.gz



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#616782: cssutils: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:cssutils
Version: 0.9.7~b2-2
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#616858: libapache2-mod-python: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:libapache2-mod-python
Version: 3.3.1-9
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#616954: py-radix: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:py-radix
Version: 0.5-2
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#616967: pygpu: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:pygpu
Version: 0.2.0a-629-2
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#616990: python-apptools: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-apptools
Version: 3.3.2-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#616994: python-axiom: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-axiom
Version: 0.6.0-2
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#616996: python-chaco: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-chaco
Version: 3.3.1-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617002: python-enable: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-enable
Version: 3.3.1-3
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617003: python-enthoughtbase: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-enthoughtbase
Version: 3.0.5-2
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617004: python-envisagecore: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-envisagecore
Version: 3.1.2-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617005: python-envisageplugins: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-envisageplugins
Version: 3.1.2-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617009: python-kde3: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-kde3
Version: 3.16.7-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617028: python-scipy: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-scipy
Version: 0.7.2+dfsg1-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617029: python-setupdocs: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-setupdocs
Version: 1.0.4-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617037: python-traits: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-traits
Version: 3.4.0-2
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617038: python-traitsbackendqt: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-traitsbackendqt
Version: 3.4.0-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617039: python-traitsbackendwx: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-traitsbackendwx
Version: 3.4.0-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#617040: python-traitsgui: deprecation of dh_pycentral, please use dh_python2

2011-03-06 Thread Matthias Klose
Package: src:python-traitsgui
Version: 3.4.0-1
Severity: important
Tags: sid wheezy
User: debian-pyt...@lists.debian.org
Usertags: pycentral-deprecation

The package build-depends on python-central, which should be
removed in time for the wheezy release.  dh_python2 should be used instead.
dh_python2 installs into the same locations as pycentral, but
avoids the creation and removal of symlinks at package installation
and removal time, making the upgrade process more robust and faster.
.
dh_python2 guarantees the installation into the same recommended site
directory used by dh_pycentral, into which anybody can install without
being forced to use any packaging helper tools.
.
Please find suggestions and help for the change at
http://wiki.debian.org/Python/PyCentral2DhPython2
.
Please file bug reports against dh_python2 for the python-dev package.
.
Consider waiting with this change until python2.7 is a supported
python version in unstable.  Test packages can already be built
in experimental (having the python-* packages from experimental installed).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#734295: shiboken tests fail with python3.4

2014-01-05 Thread Matthias Klose
Package: shiboken
Version: 1.2.1-2
Severity: important
Tags: sid, jessie
User: debian-pyt...@lists.debian.org
Usertag: python3.4


build log from
https://launchpad.net/ubuntu/+source/shiboken/1.2.1-2build1/+build/5413447/+files/buildlog_ubuntu-trusty-amd64.shiboken_1.2.1-2build1_FAILEDTOBUILD.txt.gz

24% tests passed, 127 tests failed out of 168

Total Test time (real) =  12.39 sec

The following tests FAILED:
 41 - other_collector_external_operator (SEGFAULT)
 42 - other_conversion_operator_for_class_without_implicit_conversions 
(SEGFAULT)
 43 - other_extended_multiply_operator (SEGFAULT)
 44 - other_module_reload (SEGFAULT)
 45 - other_new_ctor_operator (SEGFAULT)
 46 - other_objtypehashes (SEGFAULT)
 47 - other_otherderived (SEGFAULT)
 48 - other_typediscovery (SEGFAULT)
 49 - other_usersprimitivefromothermodule (SEGFAULT)
 50 - other_wrongctor (SEGFAULT)
 51 - sample___del__ (SEGFAULT)
 52 - sample_abstract (SEGFAULT)
 53 - sample_addedfunction (SEGFAULT)
 54 - sample_argumentmodifications (SEGFAULT)
 55 - sample_bug_554 (SEGFAULT)
 56 - sample_bug_704 (SEGFAULT)
 57 - sample_bytearray (SEGFAULT)
 58 - sample_child_return (SEGFAULT)
 59 - sample_class_fields (SEGFAULT)
 60 - sample_collector (SEGFAULT)
 61 - sample_complex (SEGFAULT)
 62 - sample_conversion_operator (SEGFAULT)
 63 - sample_copy (SEGFAULT)
 64 - sample_ctorconvrule (SEGFAULT)
 65 - sample_cyclic (SEGFAULT)
 66 - sample_date (SEGFAULT)
 67 - sample_decisor (SEGFAULT)
 68 - sample_delete (SEGFAULT)
 69 - sample_deprecated (SEGFAULT)
 70 - sample_derived (SEGFAULT)
 71 - sample_duck_punching (SEGFAULT)
 72 - sample_echo (SEGFAULT)
 73 - sample_enum (SEGFAULT)
 74 - sample_enumfromremovednamespace (SEGFAULT)
 75 - sample_event_loop_call_virtual (SEGFAULT)
 76 - sample_event_loop_thread (SEGFAULT)
 77 - sample_filter (SEGFAULT)
 78 - sample_handleholder (SEGFAULT)
 79 - sample_hashabletype (SEGFAULT)
 80 - sample_ignorederefop (SEGFAULT)
 81 - sample_implicitconv_numerical (SEGFAULT)
 82 - sample_implicitconv (SEGFAULT)
 83 - sample_inheritanceandscope (SEGFAULT)
 84 - sample_injectcode (SEGFAULT)
 85 - sample_innerclass (SEGFAULT)
 86 - sample_intlist (SEGFAULT)
 87 - sample_invalid_virtual_return (SEGFAULT)
 88 - sample_keep_reference (SEGFAULT)
 89 - sample_list (SEGFAULT)
 90 - sample_lock (SEGFAULT)
 91 - sample_map (SEGFAULT)
 92 - sample_metaclass (SEGFAULT)
 93 - sample_mi_virtual_methods (SEGFAULT)
 94 - sample_mixed_mi (SEGFAULT)
 95 - sample_modelindex (SEGFAULT)
 96 - sample_modelview (SEGFAULT)
 97 - sample_modifications (SEGFAULT)
 98 - sample_modified_constructor (SEGFAULT)
 99 - sample_modifiedvirtualmethods (SEGFAULT)
100 - sample_multi_cpp_inheritance (SEGFAULT)
101 - sample_multiple_derived (SEGFAULT)
102 - sample_namespace (SEGFAULT)
103 - sample_newdivision (SEGFAULT)
104 - sample_nondefaultctor (SEGFAULT)
105 - sample_nonzero (SEGFAULT)
106 - sample_numericaltypedef (SEGFAULT)
108 - sample_objecttype (SEGFAULT)
109 - sample_objecttype_with_named_args (SEGFAULT)
110 - sample_objecttypebyvalue (SEGFAULT)
111 - sample_objecttypelayout (SEGFAULT)
112 - sample_objecttypeoperators (SEGFAULT)
113 - sample_objecttypereferenceasvirtualmethodargument (SEGFAULT)
114 - sample_oddbool (SEGFAULT)
115 - sample_oldstyleclass_as_number (SEGFAULT)
116 - sample_onlycopyclass (SEGFAULT)
117 - sample_overflow (SEGFAULT)
118 - sample_overload_sorting (SEGFAULT)
119 - sample_overload (SEGFAULT)
120 - sample_overloadwithdefault (SEGFAULT)
121 - sample_ownership_argument_invalidation (SEGFAULT)
122 - sample_ownership_delete_child_in_cpp (SEGFAULT)
123 - sample_ownership_delete_child_in_python (SEGFAULT)
124 - sample_ownership_delete_parent (SEGFAULT)
125 - sample_ownership_invalidate_after_use (SEGFAULT)
126 - sample_ownership_invalidate_child (SEGFAULT)
127 - sample_ownership_invalidate_nonpolymorphic (SEGFAULT)
128 - sample_ownership_invalidate_parent (SEGFAULT)
129 - sample_ownership_reparenting (SEGFAULT)
130 - sample_ownership_transference (SEGFAULT)
131 - sample_pair (SEGFAULT)
132 - sample_pen (SEGFAULT)
133 - sample_point (SEGFAULT)
134 - sample_pointerholder (SEGFAULT)
135 - sample_pointf (SEGFAULT)
136 - sample_primitivereferenceargument (SEGFAULT)
137 - sample_privatector (SEGFAU

[Python-modules-team] Bug#734299: python-cffi's testsuite fails when run with python3.4

2014-01-05 Thread Matthias Klose
Package: python-cffi
Version: 0.7.2-2
Severity: important
Tags: sid, jessie
User: debian-pyt...@lists.debian.org
Usertag: python3.4

this looks similiar to #707164, there tracked down to some virtualenv issue.

= test session starts ==
platform linux -- Python 3.4.0 -- pytest-2.5.1
collected 1028 items

c/test_c.py
.s...s..s..
testing/test_cdata.py .
testing/test_ctypes.py
..s...s.s.s...s.ss..s..s.sss
testing/test_ffi_backend.py
..s...s.s...s.s.s..
testing/test_function.py .s...ss..ss..s
testing/test_model.py 
testing/test_ownlib.py ..ss..
testing/test_parsing.py ..s
testing/test_platform.py 
testing/test_unicode_literals.py 
testing/test_verify.py
s..s
testing/test_verify2.py
s..s
testing/test_version.py .
testing/test_vgen.py
s..s
testing/test_vgen2.py
s..s
testing/test_zdistutils.py ..
testing/test_zintegration.py FFF

=== FAILURES ===

[...]

== 7 failed, 975 passed, 46 skipped in 89.30 seconds ===
E: pybuild pybuild:256: test: plugin custom failed with: exit code=1: python3.4
-m pytest c/ testing/

complete log at
https://launchpadlibrarian.net/161592090/buildlog_ubuntu-trusty-amd64.python-cffi_0.7.2-2build1_FAILEDTOBUILD.txt.gz

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#734358: python3-cairo depends on both libpython3.3 and libpython3.4

2014-01-06 Thread Matthias Klose
Package: py3cairo
Version: 1.10.0+dfsg-4~exp1
Severity: important
Tags: sid, jessie
User: debian-pyt...@lists.debian.org
Usertags: python3.4

python3-cairo depends on both libpython3.3 and libpython3.4. Please do not link
the extension against the shared library at all.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#739607: don't link the extension with the python library

2014-02-20 Thread Matthias Klose
Package: py3cairo
Version: 1.10.0+dfsg-3
Tags: patch

Please don't link the extension with the python library

patch at
http://launchpadlibrarian.net/166876566/py3cairo_1.10.0%2Bdfsg-3build2_1.10.0%2Bdfsg-3ubuntu1.diff.gz

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#739879: pycxx needs an update for python3.4

2014-02-23 Thread Matthias Klose
Package: pycxx
Version: 6.2.4-5
Severity: serious
Tags: sid jessie patch
User: debian-pyt...@lists.debian.org
Usertags: python3.4

Needs a rebuild and a patch for 3.4. See
https://patches.ubuntu.com/p/pycxx/pycxx_6.2.4-5ubuntu2.patch

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#739890: some tests fail with python3.4

2014-02-23 Thread Matthias Klose
Package: python-mock
Version: 1.0.1-2
Severity: serious
Tags: sid jessie
User: debian-pyt...@lists.debian.org
Usertags: python3.4

the tests fail with python3.4:

==
ERROR: test_create_autopsec (tests.testcallable.TestCallable)
--
Traceback (most recent call last):
  File "/build/buildd/python-mock-1.0.1/tests/testcallable.py", line 143, in
test_create_autopsec
mock = create_autospec(X)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 2193, in create_autospec
_check_signature(spec, mock, is_type, instance)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 213, in _check_signature
_copy_func_details(func, checksig)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 221, in 
_copy_func_details
funcopy.__module__ = func.__module__
AttributeError: 'wrapper_descriptor' object has no attribute '__module__'

==
ERROR: test_create_autospec_instance (tests.testcallable.TestCallable)
--
Traceback (most recent call last):
  File "/build/buildd/python-mock-1.0.1/tests/testcallable.py", line 152, in
test_create_autospec_instance
mock = create_autospec(SomeClass, instance=True)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 2193, in create_autospec
_check_signature(spec, mock, is_type, instance)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 213, in _check_signature
_copy_func_details(func, checksig)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 221, in 
_copy_func_details
funcopy.__module__ = func.__module__
AttributeError: 'method-wrapper' object has no attribute '__module__'

==
ERROR: test_attributes (tests.testhelpers.SpecSignatureTest)
--
Traceback (most recent call last):
  File "/build/buildd/python-mock-1.0.1/tests/testhelpers.py", line 451, in
test_attributes
sub_mock = create_autospec(Sub)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 2193, in create_autospec
_check_signature(spec, mock, is_type, instance)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 213, in _check_signature
_copy_func_details(func, checksig)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 221, in 
_copy_func_details
funcopy.__module__ = func.__module__
AttributeError: 'wrapper_descriptor' object has no attribute '__module__'

==
ERROR: test_autospec_functions_with_self_in_odd_place
(tests.testhelpers.SpecSignatureTest)
--
Traceback (most recent call last):
  File "/build/buildd/python-mock-1.0.1/tests/testhelpers.py", line 832, in
test_autospec_functions_with_self_in_odd_place
a = create_autospec(Foo)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 2193, in create_autospec
_check_signature(spec, mock, is_type, instance)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 213, in _check_signature
_copy_func_details(func, checksig)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 221, in 
_copy_func_details
funcopy.__module__ = func.__module__
AttributeError: 'wrapper_descriptor' object has no attribute '__module__'

==
ERROR: test_autospec_property (tests.testhelpers.SpecSignatureTest)
--
Traceback (most recent call last):
  File "/build/buildd/python-mock-1.0.1/tests/testhelpers.py", line 843, in
test_autospec_property
foo = create_autospec(Foo)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 2193, in create_autospec
_check_signature(spec, mock, is_type, instance)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 213, in _check_signature
_copy_func_details(func, checksig)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 221, in 
_copy_func_details
funcopy.__module__ = func.__module__
AttributeError: 'wrapper_descriptor' object has no attribute '__module__'

==
ERROR: test_autospec_reset_mock (tests.testhelpers.SpecSignatureTest)
--
Traceback (most recent call last):
  File "/build/buildd/python-mock-1.0.1/tests/testhelpers.py", line 363, in
test_autospec_reset_mock
m = create_autospec(int)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 2193, in create_autospec
_check_signature(spec, mock, is_type, instance)
  File "/build/buildd/python-mock-1.0.1/mock.py", line 213, in _check_signature
_copy_func_details(func, checksig)
  File "/build/buildd/pyt

[Python-modules-team] Bug#739893: test failures with python3.4

2014-02-23 Thread Matthias Klose
Package: python-repoze.lru
Version: 0.6-3
Severity: serious
Tags: sid jessie
User: debian-pyt...@lists.debian.org
Usertags: python3.4

the tests fail with python3.4, however the testsuite doesn't say which ones do
fail ...

OK (unexpected successes=4)
running test
running egg_info
writing namespace_packages to repoze.lru.egg-info/namespace_packages.txt
writing requirements to repoze.lru.egg-info/requires.txt
writing dependency_links to repoze.lru.egg-info/dependency_links.txt
writing top-level names to repoze.lru.egg-info/top_level.txt
writing repoze.lru.egg-info/PKG-INFO
writing entry points to repoze.lru.egg-info/entry_points.txt
reading manifest file 'repoze.lru.egg-info/SOURCES.txt'
writing manifest file 'repoze.lru.egg-info/SOURCES.txt'
running build_ext
test_clear_with_multiple_names (repoze.lru.tests.CacherMaker) ... ok
test_clear_with_single_name (repoze.lru.tests.CacherMaker) ... ok
test_defaultvalue_and_clear (repoze.lru.tests.CacherMaker) ... ok
test_exception (repoze.lru.tests.CacherMaker) ... ok
test_expiring (repoze.lru.tests.CacherMaker) ... ok
test_named_cache (repoze.lru.tests.CacherMaker) ... ok
test_ctor_nocache (repoze.lru.tests.DecoratorTests) ... ok
test_expiry (repoze.lru.tests.DecoratorTests)
When timeout is given, decorator must eventually forget entries ... unexpected
success
test_multiargs (repoze.lru.tests.DecoratorTests) ... ok
test_singlearg (repoze.lru.tests.DecoratorTests) ... ok
test_default_timeout (repoze.lru.tests.ExpiringLRUCacheTests)
Default timeout provided at init time must be applied ... unexpected success
test_different_timeouts (repoze.lru.tests.ExpiringLRUCacheTests)
Timeouts must be per entry, default applied when none provided ... unexpected
success
test_equal_but_not_identical (repoze.lru.tests.ExpiringLRUCacheTests)
equal but not identical keys must be treated the same ... ok
test_eviction_counter (repoze.lru.tests.ExpiringLRUCacheTests) ... ok
test_get (repoze.lru.tests.ExpiringLRUCacheTests) ... ok
test_imperfect_hitrate (repoze.lru.tests.ExpiringLRUCacheTests)
If cache size == half the number of items -> hit rate ~50% ... ok
test_invalidate (repoze.lru.tests.ExpiringLRUCacheTests) ... ok
test_it (repoze.lru.tests.ExpiringLRUCacheTests)
Test a sequence of operations ... ok
test_perfect_hitrate (repoze.lru.tests.ExpiringLRUCacheTests)
If cache size equals number of items, expect 100% cache hits ... ok
test_put (repoze.lru.tests.ExpiringLRUCacheTests) ... ok
test_renew_timeout (repoze.lru.tests.ExpiringLRUCacheTests)
Re-putting an entry must update timeout ... unexpected success
test_size_lessthan_1 (repoze.lru.tests.ExpiringLRUCacheTests) ... ok
test_small_cache (repoze.lru.tests.ExpiringLRUCacheTests)
Cache of size 1 must work ... ok
test_equal_but_not_identical (repoze.lru.tests.LRUCacheTests)
equal but not identical keys must be treated the same ... ok
test_eviction_counter (repoze.lru.tests.LRUCacheTests) ... ok
test_get (repoze.lru.tests.LRUCacheTests) ... ok
test_imperfect_hitrate (repoze.lru.tests.LRUCacheTests)
If cache size == half the number of items -> hit rate ~50% ... ok
test_invalidate (repoze.lru.tests.LRUCacheTests) ... ok
test_it (repoze.lru.tests.LRUCacheTests) ... ok
test_perfect_hitrate (repoze.lru.tests.LRUCacheTests)
If cache size equals number of items, expect 100% cache hits ... ok
test_put (repoze.lru.tests.LRUCacheTests) ... ok
test_size_lessthan_1 (repoze.lru.tests.LRUCacheTests) ... ok
test_small_cache (repoze.lru.tests.LRUCacheTests)
Cache of size 1 must work ... ok

--
Ran 33 tests in 1.188s

FAILED (unexpected successes=4)
make[1]: *** [override_dh_auto_test] Error 1

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#740028: pycxx needs a rebuild and a patch to support python3.4

2014-02-24 Thread Matthias Klose
Package: pycxx
Version: 6.2.4-5
Severity: serious
Tags: sid jessie patch
User: debian-pyt...@lists.debian.org
Usertags: python3.4

Needs a rebuild and a patch for 3.4. See
https://patches.ubuntu.com/p/pycxx/pycxx_6.2.4-5ubuntu2.patch

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#743406: pyzmq fails tests on mips and kfreebsd-amd64

2014-04-02 Thread Matthias Klose

Package: pyzmq
Version: 14.0.1-1
Severity: serious
Tags: sid jessie
User: debian-pyt...@lists.debian.org
Usertags: python3.4

pyzmq fails tests on mips and kfreebsd-amd64, seen in the builds scheduled for 
the python3.4 support. See

https://buildd.debian.org/status/package.php?p=pyzmq

Ensure callable check works (py3k). ... ok

==
FAIL: test_monitor_connected (zmq.tests.test_monitor.TestSocketMonitor)
Test connected monitoring socket.
--
Traceback (most recent call last):
  File 
"/«PKGBUILDDIR»/.pybuild/pythonX.Y-dbg_3.4/build/zmq/tests/test_monitor.py", 
line 68, in test_monitor_connected

self.assertEqual(m['event'], zmq.EVENT_CONNECT_DELAYED)
AssertionError: 1 != 2

--
Ran 147 tests in 16.843s

FAILED (failures=1, skipped=19)


sys:1: ResourceWarning: unclosed file <_io.FileIO name=8 mode='rb'>
sys:1: ResourceWarning: unclosed file <_io.FileIO name=9 mode='wb'>
sys:1: ResourceWarning: unclosed file <_io.FileIO name=10 mode='rb'>
sys:1: ResourceWarning: unclosed file <_io.FileIO name=11 mode='wb'>
E: pybuild pybuild:256: test: plugin distutils failed with: exit code=1: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y-dbg_3.4/build; python3.4-dbg -m unittest 
discover -v
dh_auto_test: pybuild --test -i python{version}-dbg -p 3.4 3.3 --dir . returned 
exit code 13





and mips:

Ran 147 tests in 18.525s

OK (skipped=19)


I: pybuild base:170: cd /«PKGBUILDDIR»/.pybuild/pythonX.Y-dbg_3.3/build; 
python3.3-dbg -m unittest discover -v
test_zmq_bind (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 'PyPy 
Tests Only'
test_zmq_bind_connect (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 
'PyPy Tests Only'
test_zmq_ctx_new_destroy (zmq.tests.test_cffi_backend.TestCFFIBackend) ... 
skipped 'PyPy Tests Only'
test_zmq_getsockopt (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 
'PyPy Tests Only'
test_zmq_msg_data (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 
'PyPy Tests Only'
test_zmq_msg_init_close (zmq.tests.test_cffi_backend.TestCFFIBackend) ... 
skipped 'PyPy Tests Only'
test_zmq_msg_init_data (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 
'PyPy Tests Only'
test_zmq_msg_init_size (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 
'PyPy Tests Only'
test_zmq_poll (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 'PyPy 
Tests Only'
test_zmq_recv (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 'PyPy 
Tests Only'
test_zmq_send (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 'PyPy 
Tests Only'
test_zmq_setsockopt (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 
'PyPy Tests Only'
test_zmq_sleep (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 'PyPy 
Tests Only'
test_zmq_socket_open_close (zmq.tests.test_cffi_backend.TestCFFIBackend) ... 
skipped 'PyPy Tests Only'
test_zmq_stopwatch_functions (zmq.tests.test_cffi_backend.TestCFFIBackend) ... 
skipped 'PyPy Tests Only'
test_zmq_version_info (zmq.tests.test_cffi_backend.TestCFFIBackend) ... skipped 
'PyPy Tests Only'

test_basic (zmq.tests.test_pair.TestPair) ... ok
test_json (zmq.tests.test_pair.TestPair) ... ok
test_multiple (zmq.tests.test_pair.TestPair) ... ok
test_pyobj (zmq.tests.test_pair.TestPair) ... ok
test_init_iface (zmq.tests.test_log.TestPubLog) ... ok
test_init_socket (zmq.tests.test_log.TestPubLog) ... ok
test_root_topic (zmq.tests.test_log.TestPubLog) ... ok
test_unicode_message (zmq.tests.test_log.TestPubLog) ... ok
test_monitor (zmq.tests.test_monitor.TestSocketMonitor)
Test monitoring interface for sockets. ... Assertion failed: pfd.revents & 
POLLIN (signaler.cpp:193)

Aborted
E: pybuild pybuild:256: test: plugin distutils failed with: exit code=134: cd 
/«PKGBUILDDIR»/.pybuild/pythonX.Y-dbg_3.3/build; python3.3-dbg -m unittest 
discover -v
dh_auto_test: pybuild --test -i python{version}-dbg -p 3.4 3.3 --dir . returned 
exit code 13

make: *** [build-arch] Error 13

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#749692: python-pip-whl is missing dependencies on dependent wheels

2014-05-29 Thread Matthias Klose
Package: python-pip-whl
Version: 1.5.5-1
Severity: serious
Tags sid jessie

python-pip-whl is missing dependencies on dependent wheels, and is lacking a
list of these dependencies in /usr/share/python-wheels/pip.dependencies.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#468602: python-xml removal: please drop/replace (build) dependencies

2008-02-29 Thread Matthias Klose
Package: ll-xist
Severity: important
User: [EMAIL PROTECTED]
Usertags: python-xml-removal

Since some time a subset of python-xml is included in the
standard python library, while the python-xml package did not see
any updates for years.  It is time to drop it from the distribution.
Update scenarios:

 - Just drop the (build) dependency, if the functionality is included
   in python. (Build)-depend on python (>= 2.4).

 - Copy missing code in the std library from the python-xml package.
   (e.g. for some installer packages: localechoose).

 - Use another xml library (python-4suite-xml, python-lxml).

Please contact the ML [EMAIL PROTECTED]
for further questions and help.  Patches for some packages may be
available as a diff of an Ubuntu package at
http://packages.qa.debian.org/ll-xist

It is likely that the severity of this report is raised before the
release.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#468622: python-xml removal: please drop/replace (build) dependencies

2008-02-29 Thread Matthias Klose
Package: zsi
Severity: important
User: [EMAIL PROTECTED]
Usertags: python-xml-removal

Since some time a subset of python-xml is included in the
standard python library, while the python-xml package did not see
any updates for years.  It is time to drop it from the distribution.
Update scenarios:

 - Just drop the (build) dependency, if the functionality is included
   in python. (Build)-depend on python (>= 2.4).

 - Copy missing code in the std library from the python-xml package.
   (e.g. for some installer packages: localechoose).

 - Use another xml library (python-4suite-xml, python-lxml).

Please contact the ML [EMAIL PROTECTED]
for further questions and help.  Patches for some packages may be
available as a diff of an Ubuntu package at
http://packages.qa.debian.org/zsi

It is likely that the severity of this report is raised before the
release.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#468725: python-enthought-chaco2: s/python-setuptools/python-pkg-resources/ dependency

2008-02-29 Thread Matthias Klose
Package: python-enthought-chaco2
Severity: important

python-pkg-resources is now available as a separate package;
please depend on python-pkg-resources instead of python-setuptools
for the runtime dependency.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#468711: python-pudge: s/python-setuptools/python-pkg-resources/ dependency

2008-02-29 Thread Matthias Klose
Package: python-pudge
Severity: important

python-pkg-resources is now available as a separate package;
please depend on python-pkg-resources instead of python-setuptools
for the runtime dependency.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#468718: python-opengl: s/python-setuptools/python-pkg-resources/ dependency

2008-02-29 Thread Matthias Klose
Package: python-opengl
Severity: important

python-pkg-resources is now available as a separate package;
please depend on python-pkg-resources instead of python-setuptools
for the runtime dependency.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#468981: petsc4py: may use different memory API for a given memory block

2008-03-02 Thread Matthias Klose
Package: petsc4py
Severity: important
User: [EMAIL PROTECTED]
Usertags: goal-python2.5

The C API requires using the same memory API for a given memory block,
which will show up as a segfault, at least in python2.5. This code was
found by a search of all sources build-depending on python-dev, having
a PyObject_ function for allocation and a PyMem_ function for
deallocation in the same file.  This may be a real problem, or a false
positive.

The most common error seen is of the form:

  PyObject *
  new_wadobject(WadFrame *f, int count) {
wadobject   *self;
self = PyObject_NEW(wadobject, &WadObjectType);
[...]
  }

  static void
  wadobject_dealloc(wadobject *self) {
PyMem_DEL(self);
  }

This particular example can be fixed with replacing PyMem_DEL with
PyObject_Del.

For more information, see
http://docs.python.org/api/memory.html
http://docs.python.org/api/memoryExamples.html

Please set the severity of this report to "serious", if it is a real
problem, please close the report if it is a false positive.  Ask
the [EMAIL PROTECTED] ML for help. Archive of the
search results: http://ftp-master.debian.org/~he/affected-files.tar.gz



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#469001: python-scipy: may use different memory API for a given memory block

2008-03-02 Thread Matthias Klose
Package: python-scipy
Severity: important
User: [EMAIL PROTECTED]
Usertags: goal-python2.5

The C API requires using the same memory API for a given memory block,
which will show up as a segfault, at least in python2.5. This code was
found by a search of all sources build-depending on python-dev, having
a PyObject_ function for allocation and a PyMem_ function for
deallocation in the same file.  This may be a real problem, or a false
positive.

The most common error seen is of the form:

  PyObject *
  new_wadobject(WadFrame *f, int count) {
wadobject   *self;
self = PyObject_NEW(wadobject, &WadObjectType);
[...]
  }

  static void
  wadobject_dealloc(wadobject *self) {
PyMem_DEL(self);
  }

This particular example can be fixed with replacing PyMem_DEL with
PyObject_Del.

For more information, see
http://docs.python.org/api/memory.html
http://docs.python.org/api/memoryExamples.html

Please set the severity of this report to "serious", if it is a real
problem, please close the report if it is a false positive.  Ask
the [EMAIL PROTECTED] ML for help. Archive of the
search results: http://ftp-master.debian.org/~he/affected-files.tar.gz



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#468975: ll-xist: may use different memory API for a given memory block

2008-03-02 Thread Matthias Klose
Package: ll-xist
Severity: important
User: [EMAIL PROTECTED]
Usertags: goal-python2.5

The C API requires using the same memory API for a given memory block,
which will show up as a segfault, at least in python2.5. This code was
found by a search of all sources build-depending on python-dev, having
a PyObject_ function for allocation and a PyMem_ function for
deallocation in the same file.  This may be a real problem, or a false
positive.

The most common error seen is of the form:

  PyObject *
  new_wadobject(WadFrame *f, int count) {
wadobject   *self;
self = PyObject_NEW(wadobject, &WadObjectType);
[...]
  }

  static void
  wadobject_dealloc(wadobject *self) {
PyMem_DEL(self);
  }

This particular example can be fixed with replacing PyMem_DEL with
PyObject_Del.

For more information, see
http://docs.python.org/api/memory.html
http://docs.python.org/api/memoryExamples.html

Please set the severity of this report to "serious", if it is a real
problem, please close the report if it is a false positive.  Ask
the [EMAIL PROTECTED] ML for help. Archive of the
search results: http://ftp-master.debian.org/~he/affected-files.tar.gz



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#470697: docutils will ftbfs with new python-central version

2008-03-12 Thread Matthias Klose
Package: python-docutils

Please see the changes at
http://patches.ubuntu.com/p/python-docutils/python-docutils_0.4-5ubuntu1.patch

plus build-depend on python-central (>= 0.6).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#470698: python-numpy will ftbfs with new python-central version

2008-03-12 Thread Matthias Klose
Package: python-numpy

the location for the shared files did change, and the package uses
hardcoded locations. plus build-depend on python-central (>= 0.6).




___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472009: enthought-traits-ui: ftbfs with fixed python-central

2008-03-21 Thread Matthias Klose
Package: enthought-traits-ui
Version: 2.0.4-1
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 fixes bug #452227, removing an empty directory
usr/lib. Your package tries to remove that directory as well, not
ignoring the error code. Please either ignore the error code, or
remove the directory removal and build-depend on python-central (>= 0.6)
instead.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472036: elixir: ftbfs with python-central 0.6

2008-03-21 Thread Matthias Klose
Package: elixir
Version: 0.5.1-1
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 uses now a package and tool independent directory
to store the architecture independent files. Files which were located
in /usr/share/pycentral/site-packages/ are now located in
/usr/share/pyshared. Your package apparently hardcodes the former
location in some places. Please fix the packaging to work with the new
file locations.

Please ask for help by email or irc, or state if NMUs are welcome to
fix this report.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472041: enthought-chaco2: ftbfs with python-central 0.6

2008-03-21 Thread Matthias Klose
Package: enthought-chaco2
Version: 2.0.4-1
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 uses now a package and tool independent directory
to store the architecture independent files. Files which were located
in /usr/share/pycentral/site-packages/ are now located in
/usr/share/pyshared. Your package apparently hardcodes the former
location in some places. Please fix the packaging to work with the new
file locations.

Please ask for help by email or irc, or state if NMUs are welcome to
fix this report.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472043: python-scipy: ftbfs with python-central 0.6

2008-03-21 Thread Matthias Klose
Package: python-scipy
Version: 0.6.0-10
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 uses now a package and tool independent directory
to store the architecture independent files. Files which were located
in /usr/share/pycentral/site-packages/ are now located in
/usr/share/pyshared. Your package apparently hardcodes the former
location in some places. Please fix the packaging to work with the new
file locations.

Please ask for help by email or irc, or state if NMUs are welcome to
fix this report.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472039: pyro: ftbfs with python-central 0.6

2008-03-21 Thread Matthias Klose
Package: pyro
Version: 3.7-1
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 uses now a package and tool independent directory
to store the architecture independent files. Files which were located
in /usr/share/pycentral/site-packages/ are now located in
/usr/share/pyshared. Your package apparently hardcodes the former
location in some places. Please fix the packaging to work with the new
file locations.

Please ask for help by email or irc, or state if NMUs are welcome to
fix this report.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472042: pyopengl: ftbfs with python-central 0.6

2008-03-21 Thread Matthias Klose
Package: pyopengl
Version: 3.0.0~b1-1
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 uses now a package and tool independent directory
to store the architecture independent files. Files which were located
in /usr/share/pycentral/site-packages/ are now located in
/usr/share/pyshared. Your package apparently hardcodes the former
location in some places. Please fix the packaging to work with the new
file locations.

Please ask for help by email or irc, or state if NMUs are welcome to
fix this report.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472045: enthought-traits: ftbfs with python-central 0.6

2008-03-21 Thread Matthias Klose
Package: enthought-traits
Version: 2.0.4-1
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 uses now a package and tool independent directory
to store the architecture independent files. Files which were located
in /usr/share/pycentral/site-packages/ are now located in
/usr/share/pyshared. Your package apparently hardcodes the former
location in some places. Please fix the packaging to work with the new
file locations.

Please ask for help by email or irc, or state if NMUs are welcome to
fix this report.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472046: python-docutils: ftbfs with python-central 0.6

2008-03-21 Thread Matthias Klose
Package: python-docutils
Version: 0.4-5
Severity: serious
Usertags: ftbfs-new-pycentral

python-central 0.6 uses now a package and tool independent directory
to store the architecture independent files. Files which were located
in /usr/share/pycentral/site-packages/ are now located in
/usr/share/pyshared. Your package apparently hardcodes the former
location in some places. Please fix the packaging to work with the new
file locations.

Please ask for help by email or irc, or state if NMUs are welcome to
fix this report.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472157: matplotlib: libffi built from separate source, pleae b-d on libffi-dev

2008-03-22 Thread Matthias Klose
Package: matplotlib
Severity: important
Usertags: libffi

After 10 years libffi does have a new upstream release again; this
version is now packaged independent from GCC; once all packages are
converted to use the binaries built from the separate libffi, GCC
will stop building libffi packages.

Please replace the current build dependencies lib*ffi4-dev with
lib*ffi-dev and rebuild the package.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#472141: evolution-python: libffi built from separate source, pleae b-d on libffi-dev

2008-03-22 Thread Matthias Klose
Package: evolution-python
Severity: important
Usertags: libffi

After 10 years libffi does have a new upstream release again; this
version is now packaged independent from GCC; once all packages are
converted to use the binaries built from the separate libffi, GCC
will stop building libffi packages.

Please replace the current build dependencies lib*ffi4-dev with
lib*ffi-dev and rebuild the package.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#478451: matplotlib: should use python-numpy instead of python-num{eric, array}

2008-04-29 Thread Matthias Klose
Package: matplotlib
Version: 0.90.1-4
Severity: important
User: [EMAIL PROTECTED]
Usertags: python-oldnum

Both python-numeric and python-numarray do not see new upstream releases
anymore; the currently maintained project is python-numpy. Please convert
the package to use python-numpy instead.  This might require changes to
the upstream code.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#478449: ipython: should use python-numpy instead of python-num{eric, array}

2008-04-29 Thread Matthias Klose
Package: ipython
Version: 0.8.2.dfsg-2
Severity: important
User: [EMAIL PROTECTED]
Usertags: python-oldnum

Both python-numeric and python-numarray do not see new upstream releases
anymore; the currently maintained project is python-numpy. Please convert
the package to use python-numpy instead.  This might require changes to
the upstream code.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#478448: pyfits: should use python-numpy instead of python-num{eric, array}

2008-04-29 Thread Matthias Klose
Package: pyfits
Version: 1:1.3-1
Severity: important
User: [EMAIL PROTECTED]
Usertags: python-oldnum

Both python-numeric and python-numarray do not see new upstream releases
anymore; the currently maintained project is python-numpy. Please convert
the package to use python-numpy instead.  This might require changes to
the upstream code.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#489726: unconditional dependency on libatlas3gf-base

2008-07-07 Thread Matthias Klose
Package: python-numpy
Version: 1:1.1.0-2
Severity: serious

python-numpy now has an unconditional dependency on libatlas3gf-base,
needing the "specialized" atlas libraries as a runtime
dependency. Users still should have the option to use the standard
blas and lapack libs instead of the untested/unmaintained atlas
libraries in debian.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#489253: should numpy be built with atlas?

2008-07-07 Thread Matthias Klose
Ondrej Certik writes:
> On Mon, Jul 7, 2008 at 2:12 PM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> > Package: python-numpy
> > Version: 1:1.1.0-2
> > Severity: serious
> >
> > python-numpy now has an unconditional dependency on libatlas3gf-base,
> > needing the "specialized" atlas libraries as a runtime
> > dependency. Users still should have the option to use the standard
> > blas and lapack libs instead of the untested/unmaintained atlas
> > libraries in debian.
> 
> Hi Matthias,
> 
> I changed that on a request from a user:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489253
> 
> so should we revert this change? I.e. should numpy not be built with
> atlas support? This will make it quite slow in Debian.
> 
> CCing to debian python as well to get more opinions on this.

afaiu this has nothing to do if blas/lapack or atlas are used;
apparently _dotblas.so is not built when just using blas/lapack. this
seems to be the real bug which we should fix.

  Matthias



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#489253: should numpy be built with atlas?

2008-07-08 Thread Matthias Klose
[EMAIL PROTECTED] writes:
> On Mon, Jul 7, 2008 at 2:12 PM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> > Package: python-numpy
> > Version: 1:1.1.0-2
> > Severity: serious
> >
> > python-numpy now has an unconditional dependency on libatlas3gf-base,
> > needing the "specialized" atlas libraries as a runtime
> > dependency. Users still should have the option to use the standard
> > blas and lapack libs instead of the untested/unmaintained atlas
> > libraries in debian.
> 
> The problem is that the new (>1.0) numpy building system needs ATLAS 
> at compile time to enable fast matrix-multiplication. If ATLAS is not found
> at compile time, numpy.core._dotblas.so is not built and slow matrix 
> multiplication is used even if the end user has ATLAS installed. In the old
> numpy _dotblas.so was always compiled using refblas and the end user 
> would still have had the option of using ATLAS. I'm not sure I understand 
> why ATLAS is now needed at compile time, but look here:
> http://scipy.org/scipy/numpy/ticket/667
> and here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464784
> 
> I think python-numpy should stay as it is now and a bug-wishlist should be 
> reported to the atlas package to encourage packaging of the new stable
>  version (3.8.2). Filing a ticket on numpy trac may help, but the fate of 
> ticket 667 seems to indicate that there's no will of fixing this bug 
> upstream...

thanks for the update. Looking at the blas package, I see that the
cblas library is included in libblas3.  So it looks like the numpy
check is wrong, testing for a package name, and not for a
feature. This seems to explain why it did work in etch, and this
should be fixed in python-numpy.

  Matthias



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#490486: pudge: rebuild to move files to /usr/share/pyshared

2008-07-12 Thread Matthias Klose
Package: pudge
Version: 0.1.4~svn137-3
Severity: important
User: [EMAIL PROTECTED]
Usertags: pyshared

This package builds binary-indep package(s), which place file in the location
/usr/share/pycentral/. python-central now puts these files
into a package independent dirctory /usr/share/pyshared. Please rebuild
the package in a current unstable environment to move the files to the
new location.
.
I do intend to NMU the package (just doing a rebuild).



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#506682: arm patch fails to apply

2008-11-23 Thread Matthias Klose
Package: python-qt4
Severity: important
User: [EMAIL PROTECTED]
Usertags: origin-ubuntu jaunty
Tags: patch

the patch fails to apply. attached is the updated patch from the
ubuntu package:

#! /bin/sh /usr/share/dpatch/dpatch-run
## 04_qreal_api_fixes.dpatch by Torsten Marek <[EMAIL PROTECTED]>
##
## DP: Exchanges double by qreal in some wrapped methods.

@DPATCH@
--- ./sip/QtCore/qvector.sip.orig   2008-08-08 14:10:05.0 +
+++ ./sip/QtCore/qvector.sip2008-11-20 16:09:43.0 +
@@ -156,8 +156,8 @@
 return sipGetState(sipTransferObj);
 %End
 };
-// QVector is implemented as a Python list of floats.
-%MappedType QVector
+// QVector is implemented as a Python list of floats.
+%MappedType QVector
 {
 %TypeHeaderCode
 #include 
@@ -193,7 +193,7 @@
 if (sipIsErr == NULL)
 return PyList_Check(sipPy);
 
-QVector *ql = new QVector;
+QVector *ql = new QVector;
  
 for (SIP_SSIZE_T i = 0; i < PyList_GET_SIZE(sipPy); ++i)
 ql->append(PyFloat_AsDouble(PyList_GET_ITEM(sipPy, i)));
@@ -203,9 +203,9 @@
 return sipGetState(sipTransferObj);
 %End
 };
-// QVector > is implemented as a Python list of 2-element 
tuples.
+// QVector > is implemented as a Python list of 2-element 
tuples.
 template
-%MappedType QVector >
+%MappedType QVector >
 {
 %TypeHeaderCode
 #include 
@@ -222,7 +222,7 @@
 // Set the list elements.
 for (int i = 0; i < sipCpp->size(); ++i)
 {
-const QPair &p = sipCpp->at(i);
+const QPair &p = sipCpp->at(i);
 TYPE *pt = new TYPE(p.second);
 PyObject *pobj;
 
@@ -261,14 +261,14 @@
 return 1;
 }
 
-QVector > *qv = new QVector >;
+QVector > *qv = new QVector >;
  
 for (SIP_SSIZE_T i = 0; i < PyList_GET_SIZE(sipPy); ++i)
 {
 PyObject *tup = PyList_GET_ITEM(sipPy, i);
 int state;
 TYPE *s;
-QPair p;
+QPair p;
 
 p.first = PyFloat_AsDouble(PyTuple_GET_ITEM(tup, 0));
 
--- ./sip/QtCore/qlist.sip.orig 2008-08-08 14:10:05.0 +
+++ ./sip/QtCore/qlist.sip  2008-11-20 16:08:13.0 +
@@ -343,8 +343,8 @@
 %End
 };
 %If (Qt_4_3_0 -)
-// QList > is implemented as a Python list of 2-element 
tuples.
-%MappedType QList >
+// QList > is implemented as a Python list of 2-element 
tuples.
+%MappedType QList >
 {
 %TypeHeaderCode
 #include 
@@ -361,7 +361,7 @@
 // Set the list elements.
 for (int i = 0; i < sipCpp->size(); ++i)
 {
-const QPair &p = sipCpp->at(i);
+const QPair &p = sipCpp->at(i);
 PyObject *pobj;
 
 if ((pobj = Py_BuildValue((char *)"dd", p.first, p.second)) == NULL)
@@ -393,16 +393,16 @@
 return 1;
 }
 
-QList > *ql = new QList >;
+QList > *ql = new QList >;
  
 for (SIP_SSIZE_T i = 0; i < len; ++i)
 {
 PyObject *tup = PySequence_ITEM(sipPy, i);
 
-double first = PyFloat_AsDouble(PySequence_ITEM(tup, 0));
-double second = PyFloat_AsDouble(PySequence_ITEM(tup, 1));
+float first = PyFloat_AsDouble(PyTuple_GET_ITEM(tup, 0));
+float second = PyFloat_AsDouble(PyTuple_GET_ITEM(tup, 1));
  
-ql->append(QPair(first, second));
+ql->append(QPair(first, second));
 }
  
 *sipCppPtr = ql;
@@ -412,9 +412,9 @@
 };
 %End
 %If (Qt_4_3_0 -)
-// QList > is implemented as a Python list of 2-element 
tuples.
-template
-%MappedType QList >
+// QList > is implemented as a Python list of 2-element 
tuples.
+template
+%MappedType QList >
 {
 %TypeHeaderCode
 #include 
@@ -431,7 +431,7 @@
 // Set the list elements.
 for (int i = 0; i < sipCpp->size(); ++i)
 {
-const QPair &p = sipCpp->at(i);
+const QPair &p = sipCpp->at(i);
 TYPE *t = new TYPE(p.second);
 PyObject *pobj;
 
@@ -472,12 +472,12 @@
 return 1;
 }
 
-QList > *ql = new QList >;
+QList > *ql = new QList >;
  
 for (SIP_SSIZE_T i = 0; i < len; ++i)
 {
 PyObject *tup = PySequence_ITEM(sipPy, i);
-double d;
+float d;
 int state;
 
 d = PyFloat_AsDouble(PySequence_ITEM(tup, 0));
@@ -491,7 +491,7 @@
 return 0;
 }
 
-ql->append(QPair(d, *t));
+ql->append(QPair(d, *t));
 
 sipReleaseInstance(t, sipClass_TYPE, state);
 }
@@ -551,8 +551,8 @@
 return sipGetState(sipTransferObj);
 %End
 };
-// QList is implemented as a Python list of floats.
-%MappedType QList
+// QList is implemented as a Python list of floats.
+%MappedType QList
 {
 %TypeHeaderCode
 #include 
@@ -590,7 +590,7 @@
 if (sipIsErr == NULL)
 return (len >= 0);
 
-QList *ql = new QList;
+QList *ql = new QList;
  
 for (SIP_SSIZE_T i = 0; i < len; ++i)
 ql->append(PyFloat_AsDouble(PySequence_ITEM(sipPy, i)));
--- ./sip/QtGui/qbrush.sip.orig 2008-08-08 14:10:05.0 +
+++ ./sip/QtGui/qbrush.sip  2008-11-20 16:04:58.0 +
@@ -151,7 +151,7 @@
 
 QDataStream &operator>>(QData

[Python-modules-team] Bug#546429: python-setupdocs: s/python-setuptools/python-pkg-resources/ dependency

2009-09-13 Thread Matthias Klose
Package: python-setupdocs
Version: 1.0.3-1
Severity: important
User: d...@debian.org
Usertags: python-setuptools

python-pkg-resources is packaged as a separate package; usually only
the pkg_resources module is needed as a runtime dependency.
please depend on python-pkg-resources instead of python-setuptools
for the runtime dependency.

There is a chance that this report is a false positive; in this case
please just close it.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#546428: python-repoze.who: s/python-setuptools/python-pkg-resources/ dependency

2009-09-13 Thread Matthias Klose
Package: python-repoze.who
Version: 1.0.15-1
Severity: important
User: d...@debian.org
Usertags: python-setuptools

python-pkg-resources is packaged as a separate package; usually only
the pkg_resources module is needed as a runtime dependency.
please depend on python-pkg-resources instead of python-setuptools
for the runtime dependency.

There is a chance that this report is a false positive; in this case
please just close it.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#546431: python-repoze.who-plugins: s/python-setuptools/python-pkg-resources/ dependency

2009-09-13 Thread Matthias Klose
Package: python-repoze.who-plugins
Version: 20090530-4
Severity: important
User: d...@debian.org
Usertags: python-setuptools

python-pkg-resources is packaged as a separate package; usually only
the pkg_resources module is needed as a runtime dependency.
please depend on python-pkg-resources instead of python-setuptools
for the runtime dependency.

There is a chance that this report is a false positive; in this case
please just close it.



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#791257: qscintilla2: library transition may be needed when GCC 5 is the default

2015-07-03 Thread Matthias Klose
Package: src:qscintilla2
Version: 2.8.4+dfsg-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#791276: shiboken: library transition may be needed when GCC 5 is the default

2015-07-03 Thread Matthias Klose
Package: src:shiboken
Version: 1.2.2-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: libstdc++-cxx11

Background [1]: libstdc++6 introduces a new ABI to conform to the
C++11 standard, but keeps the old ABI to not break existing binaries.
Packages which are built with g++-5 from experimental (not the one
from testing/unstable) are using the new ABI.  Libraries built from
this source package export some of the new __cxx11 or B5cxx11 symbols,
and dropping other symbols.  If these symbols are part of the API of
the library, then this rebuild with g++-5 will trigger a transition
for the library.

What is needed:

 - Rebuild the library using g++/g++-5 from experimental. Note that
   most likely all C++ libraries within the build dependencies need
   a rebuild too. You can find the log for a rebuild in
 https://people.debian.org/~doko/logs/gcc5-20150701/
   Search for "BEGIN GCC CXX11" in the log.

 - Decide if the symbols matching __cxx11 or B5cxx11 are part of the
   library API, and are used by the reverse dependencies of the
   library.

 - If there are no symbols matching __cxx11 or B5cxx11 in the symbols
   forming the library API, you should close this issue with a short
   explanation.
 
 - If there are no reverse dependencies, it should be the package
   maintainers decision if a transition is needed.  However this might
   break software which is not in the Debian archive, and built
   against these packages.

 - If a library transition is needed, please prepare for the change.
   Rename the library package, append "v5" to the name of the package
   (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
   have a soversion bump and you upload this version instead of the
   renamed package.  Prepare a patch and attach it to this issue (mark
   this issue with patch), so that it is possible to NMU such a
   package. We'll probably have more than hundred transitions
   triggered. Then reassign the issue to release.debian.org and
   properly tag it as a transition issue, by sending an email to
   cont...@bugs.debian.org:
   
 user release.debian@packages.debian.org
 usertag  + transition
 block  by 790756
 reassign  release.debian.org
   
 - If unsure if a transition is needed, please tag the issue with help
   to ask for feedback from other Debian developers.

The libstdc++6 transition will be a large one, and it will come with a
lot of pain.  Please help it by preparing the follow-up transitions.

[1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#793277: pytaglib: change of type in system_error might break with GCC-5

2015-07-22 Thread Matthias Klose
Package: src:pytaglib
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: gcc-pr66145

GCC PR libstdc++/66145 is a regression in GCC 5 which won't be fixed
upstream in time for the GCC defaults change.  The work around is to
rebuild the affected packages after GCC 5 is the default compiler.
Please look at the code and decide, if the package is affected. If
not, please just close the issue.  If it's a real issue, I'll add
the packages affected to libstdc++6's Breaks attributes, with the
version of the package at the time of the defaults change.

See 
https://wiki.debian.org/GCC5#libstdc.2B-.2B-_c.2B-.2B-11_incompatibilities_.284.9_and_5.29
for further information.

To build with GCC 5,install the gcc, g++, gfortran, ... packages
from experimental (apt-get -t experimental install g++).

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#797829: python-igraph ftbfs in unstable with igraph 0.7

2015-09-02 Thread Matthias Klose
Package: src:python-igraph
Version: 0.6.5-1
Severity: serious
Tags: sid stretch patch

python-igraph ftbfs in unstable with igraph 0.7

An updated upstream package is available from
https://launchpad.net/ubuntu/+source/python-igraph/0.7.1post6-0ubuntu2

Please also create a python3-igraph package.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#771831: python-googlecloudapis: fails to upload in Ubuntu due to files from 1980

2015-09-09 Thread Matthias Klose
Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/216760504/python-googlecloudapis_0.9.30%2Bdebian1-1ubuntu1_0.9.30%2Bdebian1-1ubuntu2.diff.gz

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#798565: dulwich ftbfs on armhf and powerpc, and uninstallable in unstable

2015-09-10 Thread Matthias Klose
Package: src:dulwich
Version: 0.10.1-1
Severity: serious
Tags: sid stretch

dulwich ftbfs on armhf and powerpc, and is uninstallable in unstable ( pypy << 
2.5).

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#798943: 64bit builds raise a lot of compiler warnings

2015-09-14 Thread Matthias Klose
Package: src:dulwich
Version: 0.11.1-1
Severity: important
Tags: sid stretch

seen on every 64bit architecture:

https://buildd.debian.org/status/fetch.php?pkg=dulwich&arch=ppc64el&ver=0.11.1-1&stamp=1442171901

dulwich/_objects.c: In function 'init_objects':
dulwich/_objects.c:256:6: warning: implicit declaration of function
'Py_InitModule3' [-Wimplicit-function-declaration]
  m = Py_InitModule3("_objects", py_objects_methods, NULL);
  ^
dulwich/_objects.c:256:4: warning: assignment makes pointer from integer without
a cast [-Wint-conversion]
  m = Py_InitModule3("_objects", py_objects_methods, NULL);
^

as a side note, the packaging doesn't seem to be correct, if multiple python3
versions are supported:

see
https://launchpadlibrarian.net/217905805/buildlog_ubuntu-wily-amd64.dulwich_0.11.1-1_BUILDING.txt.gz

the 3.5 binaries are here built in the install target, and not tested.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#800940: dulwich doesn't seem to be ready for 64bit architectures

2015-10-05 Thread Matthias Klose

Package: src:dulwich
Version: 0.11.2-1
Severity: important
Tags: sid stretch

seen on the Ubuntu buildds at

Function `PyString_FromStringAndSize' implicitly converted to pointer at 
dulwich/_objects.c:52
Function `PyString_AS_STRING' implicitly converted to pointer at 
dulwich/_objects.c:212

Function `Py_InitModule3' implicitly converted to pointer at 
dulwich/_objects.c:256
Function `PyString_FromString' implicitly converted to pointer at 
dulwich/_pack.c:55
Function `_PyString_Join' implicitly converted to pointer at dulwich/_pack.c:60
Function `PyString_AS_STRING' implicitly converted to pointer at 
dulwich/_pack.c:99
Function `PyString_FromStringAndSize' implicitly converted to pointer at 
dulwich/_pack.c:115

Function `PyString_AsString' implicitly converted to pointer at 
dulwich/_pack.c:122
Function `PyInt_FromLong' implicitly converted to pointer at dulwich/_pack.c:229
Function `Py_InitModule3' implicitly converted to pointer at dulwich/_pack.c:255
Function `PyString_FromStringAndSize' implicitly converted to pointer at 
dulwich/_diff_tree.c:284
Function `PyInt_FromLong' implicitly converted to pointer at 
dulwich/_diff_tree.c:290

Function `Py_InitModule' implicitly converted to pointer at 
dulwich/_diff_tree.c:398

however the same is true for the Debian builds.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#800940: 64bit builds raise a lot of compiler warnings

2015-10-05 Thread Matthias Klose

Control: tags -1 + patch

>>> import dulwich._objects
Traceback (most recent call last):
  File "", line 1, in 
ImportError: 
/usr/lib/python3/dist-packages/dulwich/_objects.cpython-34m-x86_64-linux-gnu.so: 
undefined symbol: PyString_FromStringAndSize



please don't ship non-working extension modules.

patch at
http://launchpadlibrarian.net/220370260/dulwich_0.11.2-1_0.11.2-1ubuntu1.diff.gz

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#802833: please do not link python extensions against libpython

2015-10-23 Thread Matthias Klose

Package: src:pyside
Version: 1.2.2-2
Severity: important
Tags: sid stretch

please do not link python extensions against libpython, or else you force people 
to install all supported python versions.


See:

$ apt-cache show python3-pyside.qtcore | grep Depends
Depends: libc6 (>= 2.14), libgcc1 (>= 1:4.1.1), libpyside-py3-1.2 (= 1.2.2-2), 
libpython3.4 (>= 3.4.2), libpython3.5 (>= 3.5.0~b1), libqtcore4 (>= 4:4.8.0), 
libshiboken-py3-1.2v5 (>= 1.2.2-2+b1), libstdc++6 (>= 4.1.1), python3 (<< 3.6), 
python3 (>= 3.4~)


___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#802962: missing build dependencies on python{, 3}-click

2015-10-25 Thread Matthias Klose

Package: src:elasticsearch-curator
Version: 3.3.0-1

missing build dependencies on python{,3}-click are missing. Note these get 
generated as dependencies.


___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#803062: please ship python{, 3}-shiboken packages

2015-10-26 Thread Matthias Klose

Package: src:shiboken
Version: 1.2.2-2

Forwarded from a Ubuntu report:

It appears that the Ubuntu packages for shiboken don't include an importable 
"shiboken" module. This is necessary for some libraries using PySide, to quote 
https://shiboken.readthedocs.org/en/latest/shibokenmodule.html:


"""
This Python module can be used to access internal information related to our 
binding technology. Access to this internal information is required to e.g.: 
integrate PySide with Qt based programs that offer Python scripting like Maya™ 
or just for debug purposes.

"""

it indeed builds a shiboken.so for all python versions, but it is not shipped.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#803082: ipython ftbfs (too new lessc version)

2015-10-26 Thread Matthias Klose

Package: src:ipython
Version: 2.3.0-2
Severity: serious
Tags: sid stretch

ipython ftbfs (too new lessc version in the archive):

cd IPython/html && fab css
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/fabric/main.py", line 743, in main
*args, **kwargs
  File "/usr/lib/python2.7/dist-packages/fabric/tasks.py", line 427, in execute
results[''] = task.run(*args, **new_kwargs)
  File "/usr/lib/python2.7/dist-packages/fabric/tasks.py", line 174, in run
return self.wrapped(*args, **kwargs)
  File "/home/packages/tmp/x/ipython-2.3.0/IPython/html/fabfile.py", line 21, 
in css

_compile_less(source, target, minify, verbose)
  File "/home/packages/tmp/x/ipython-2.3.0/IPython/html/fabfile.py", line 46, 
in _compile_less

raise ValueError("lessc too new: %s >= %s" % (less_version, 
max_less_version))
ValueError: lessc too new: 1.6.3 >= 1.5.0
debian/rules:23: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/home/packages/tmp/x/ipython-2.3.0'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#803082: Bug#803082: ipython ftbfs (too new lessc version)

2015-10-30 Thread Matthias Klose

On 30.10.2015 10:03, Brian May wrote:

I suspect the solution to this is to update to use ipython 4.0.0

It looks like there have been significant structural changes in 4.0.0,
so work is required to merge the patches (conflicts occur due to missing
files) and update debian/rules.


the 3.x series seems to be still recent enough, and still has the monolithic 
approach. So maybe you'll see less surprises with this one?


___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#883157: libapache2-mod-python: Please support for Python3

2017-11-30 Thread Matthias Klose
Package: src:libapache2-mod-python
Version: 3.3.1-11
User: debian-pyt...@lists.debian.org
Usertags: py2-removal

Please consider adding support for Python3, either by using python3 as the
default, or maybe by providing a libapache2-mod-python3 binary package.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#884674: 2to binary moved to the 2to3 binary package

2017-12-18 Thread Matthias Klose
Package: src:sparql-wrapper-python
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#884669: 2to3 binary moved to it's own 2to3 package

2017-12-18 Thread Matthias Klose
Package: src:pyzmq
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#884668: 2to3 binary moved to it's own 2to3 package

2017-12-18 Thread Matthias Klose
Package: src:python-dsv
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#884667: 2to3 binary moved to it's own 2to3 package

2017-12-18 Thread Matthias Klose
Package: src:pycxx
Severity: serious
Tags: sid buster

The 2to3 binary is now built using Python3, and therefore had to move out of the
python (2) package. It's now provided in it's own 2to3 package.  Please add a
build dependency on 2to3, and check if the autopkg test dependencies need an
update as well.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#866452: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#866468: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#866457: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#866469: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#866471: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#866464: python-imaging package will be dropped

2017-12-18 Thread Matthias Klose
With the pillow release 4.4.0 expected in January 2018 the python-imaging
package will be dropped and the severity of this issue will be raised.
Please update the package drop the python-imaging (build) dependency.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#889980: missing python3 autopkg test dependencies

2018-02-09 Thread Matthias Klose
Package: src:txzmq
Version: 0.7.4-2
Severity: important
Tags: sid buster patch

missing python autopkg test dependencies

patch at
http://launchpadlibrarian.net/356269392/txzmq_0.7.4-2ubuntu1_0.7.4-2ubuntu2.diff.gz

Maybe it's better to write a second test for the Python3 runs.

However, for me at least, the tests fail:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/t/txzmq/20180208_234021_24dbd@/log.gz

autopkgtest [20:53:31]: test unittests: [---
= test session starts ==
platform linux2 -- Python 2.7.14+, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/autopkgtest.15j71t/autopkgtest_tmp, inifile:
collected 36 items

. .....ss..ss.

= 28 passed, 8 skipped in 9.23 seconds =
= test session starts ==
platform linux -- Python 3.6.4, pytest-3.2.1, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/autopkgtest.15j71t/autopkgtest_tmp, inifile:
collected 38 items

. F...FFF.FFF....ss..FEautopkgtest [23:40:11]: ERROR: timed out on
command "su -s /bin/bash ubuntu -c set -e; export USER=`id -nu`; . /etc/profile
>/dev/null 2>&1 || true;  . ~/.profile >/dev/null 2>&1 || true;
buildtree="/tmp/autopkgtest.15j71t/build.iXO/src"; mkdir -p -m 1777 --
"/tmp/autopkgtest.15j71t/unittests-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest.15j71t/unittests-artifacts"; export
ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest.15j71t/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest.15j71t/autopkgtest_tmp"; export
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=1; unset LANGUAGE LC_CTYPE
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd
"$buildtree"; export 'ADT_TEST_TRIGGERS=txzmq/0.7.4-2ubuntu2'; chmod +x
/tmp/autopkgtest.15j71t/build.iXO/src/debian/tests/unittests; touch
/tmp/autopkgtest.15j71t/unittests-stdout
/tmp/autopkgtest.15j71t/unittests-stderr;
/tmp/autopkgtest.15j71t/build.iXO/src/debian/tests/unittests 2> >(tee -a
/tmp/autopkgtest.15j71t/unittests-stderr >&2) > >(tee -a
/tmp/autopkgtest.15j71t/unittests-stdout);" (kind: test)
autopkgtest [23:40:11]: test unittests: ---]
unittestsFAIL timed out
autopkgtest [23:40:11]: test unittests:  - - - - - - - - - - results - - - - - -
- - - -
autopkgtest [23:40:12]:  summary
unittestsFAIL timed out
Exit request sent.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


[Python-modules-team] Bug#890315: python-docutils autopkg test needs to depend on 2to3 and use it instead of 2to3-3.6

2018-02-13 Thread Matthias Klose
Package: src:python-docutils
Version: 0.14+dfsg-2
Severity: important
Tags: sid buster

python-docutils autopkg tests are currently failing. the test needs to depend on
2to3 and use it instead of 2to3-3.6.

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team


  1   2   >