[Python-modules-team] Processed: raise severity of python3.4 issues (which is now a supported python version)
Processing commands for cont...@bugs.debian.org: severity 734291 serious Bug #734291 [cython] cython testsuite not yet ready for python3.4 Severity set to 'serious' from 'important' severity 734298 serious Bug #734298 [pytables] pytables tests fail with python3.4 Severity set to 'serious' from 'important' severity 734295 serious Bug #734295 [shiboken] shiboken tests fail with python3.4 Severity set to 'serious' from 'important' severity 736706 serious Bug #736706 [python-misaka] python-misaka needs to b-d on python3-all-dev Severity set to 'serious' from 'important' severity 739598 serious Bug #739598 [pystache] pystache tests fail with python3.4 Severity set to 'serious' from 'important' severity 734339 serious Bug #734339 [pycangjie] pycangjie build-depends on python3-all-dev, but only builds for the default python version Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 734291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734291 734295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734295 734298: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734298 734339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734339 736706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736706 739598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ 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
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/python-mock-1.0.1/mock.py, line 221, in
[Python-modules-team] Bug#739893: test failures with python3.4
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] django-floppyforms 1.1.1-1 MIGRATED to testing
FYI: The status of the django-floppyforms source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.1.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ 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] cairosvg 1.0.4-1 MIGRATED to testing
FYI: The status of the cairosvg source package in Debian's testing distribution has changed. Previous version: 1.0.3-1 Current version: 1.0.4-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ 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] genshi 0.7-2 MIGRATED to testing
FYI: The status of the genshi source package in Debian's testing distribution has changed. Previous version: 0.7-1 Current version: 0.7-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ 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] simplejson 3.3.3-1 MIGRATED to testing
FYI: The status of the simplejson source package in Debian's testing distribution has changed. Previous version: 3.3.2-1 Current version: 3.3.3-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ 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#739898: python-git: untracked_files no longer detected
Package: python-git
Version: 0.3.2~RC1-3
Severity: important
Tags: upstream patch
Hi,
The output of git status is no longer in the format expected by python-git, in
particular the Repo.untracked_files property parses the git status output
expecting a:
# Untracked files:
while later versions of git droped the #, also there are some subtleties in
the management of the file names (avoid the use of replace and rstrip
removes spaces not only '\n').
I'm attaching a patch that fixes the untracked_files property.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-git depends on:
ii git [git-core] 1:1.9.0-1
ii git-core1:1.9.0-1
ii libjs-jquery1.7.2+dfsg-3
ii python 2.7.5-5
ii python-gitdb0.5.4-1
python-git recommends no packages.
python-git suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/pyshared/git/repo/base.py (from python-git
package)
diff -Naru python-git/git/repo/base.py python-git.new/git/repo/base.py
--- python-git/git/repo/base.py 2011-07-05 21:50:02.0 +0200
+++ python-git.new/git/repo/base.py 2014-02-23 17:54:32.157547255 +0100
@@ -512,35 +512,33 @@
return True
# END untracked files
return False
-
+
@property
def untracked_files(self):
:return:
list(str,...)
-
+
Files currently untracked as they have not been staged yet. Paths
are relative to the current working directory of the git command.
-
+
:note:
ignored files will not appear here, i.e. files mentioned in .gitignore
# make sure we get all files, no only untracked directores
- proc = self.git.status(untracked_files=True, as_process=True)
- stream = iter(proc.stdout)
+ proc = self.git.status(porcelain=True,
+ untracked_files=True,
+ as_process=True)
+ # Untracked files preffix in porcelain mode
+ preffix = ??
untracked_files = list()
- for line in stream:
- if not line.startswith(# Untracked files:):
+ for line in proc.stdout:
+ if not line.startswith(preffix):
continue
- # skip two lines
- stream.next()
- stream.next()
-
- for untracked_info in stream:
-if not untracked_info.startswith(#\t):
- break
-untracked_files.append(untracked_info.replace(#\t, ).rstrip())
- # END for each utracked info line
- # END for each line
+filename = line[len(preffix):].rstrip('\n')
+# Special characters are escaped
+if filename[0] == filename[-1] == '':
+filename = filename[1:-1].decode('string_escape')
+ untracked_files.append(filename)
return untracked_files
@property
___
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] Processing of python-babel_1.3+dfsg.1-3_amd64.changes
python-babel_1.3+dfsg.1-3.dsc has incorrect size; deleting it Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ 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] SQLAlchemy 0.9.X in unstable
Hi guys, I just uploaded sqlalchemy 0.9.3 to unstable (0.9.1 and 0.9.2 was only in experimental). I've set urgency to low to give it a bit more time before if migrates to testing. Please check if your package works fine with 0.9 and let me know if it doesn't. If the dependency on python-sqlalchemy was generated by dh_python2, you already have python-sqlalchemy ( 0.9) in Depends. If your package works fine with 0.9.X, just rebuild it with the one in unstable - dh_python2 will generate 0.10 Migration notes: * http://docs.sqlalchemy.org/en/rel_0_9/changelog/migration_09.html or * /usr/share/doc/python-sqlalchemy-doc/rst/changelog/migration_09.txt or * /usr/share/doc/python-sqlalchemy-doc/html/changelog/migration_09.html ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] SQLAlchemy 0.9.X in unstable
CC-ing the release team, since I think you should have coordinate with them here. On 02/23/2014 11:58 PM, Piotr Ożarowski wrote: Hi guys, I just uploaded sqlalchemy 0.9.3 to unstable Noo !!! Man, this is a COMPLETE DISASTER for me. Don't do this again without any coordination! This *will* break about everything in OpenStack. I'm just recovering from the last upload of SQLAlchemy 0.8.x which you did last July without any coordination, yet you're doing it again. It took about 7 months for upstream to do the switch, and during a full release cycle, I had lots and lots of troubles. (0.9.1 and 0.9.2 was only in experimental). I've set urgency to low to give it a bit more time before if migrates to testing. I would also submit a RC bug against it, because this needs a transition, and preferably managed by the release team. Please check if your package works fine with 0.9 and let me know if it doesn't. I'm letting you know. You have just broke: - ceilometer - cinder - glance - heat - keystone - neutron - nova - trove - taskflow Plus those not released yet but already packaged on Alioth, but which I was planning on uploading soon: - ironic - tuskar - designate All of the above is using SQLA 0.8.x, and upstream isn't planning on doing the switch to 0.9.x before next April at least (schedule release of Icehouse). Are you going to help patching the upstream code for them? I don't think so... :( Note that OpenStack Icehouse will be in feature freeze early next month, and that I don't think I can ask for an upgrade of everything to SQLAlchemy 0.9. If you were doing this at the beginning of a release cycle (which happens every 6 months), maybe that could be accepted upstream, but not like this, just before the feature freeze. If the dependency on python-sqlalchemy was generated by dh_python2, you already have python-sqlalchemy ( 0.9) in Depends. If your package works fine with 0.9.X, just rebuild it with the one in unstable - dh_python2 will generate 0.10 That's realistically going to break everything, and rebuilding will not fix anything. I haven't checked yet, but I know upstream did in the CI, and it broke. Also, sqlalchemy-migrate doesn't currently work with SQLA 0.9. See upstream working on it: https://review.openstack.org/#/c/66156/ I don't think it's reasonable to upload SQLA if SQLA-migrate doesn't support version 0.9.x. Migration notes: * http://docs.sqlalchemy.org/en/rel_0_9/changelog/migration_09.html or * /usr/share/doc/python-sqlalchemy-doc/rst/changelog/migration_09.txt or * /usr/share/doc/python-sqlalchemy-doc/html/changelog/migration_09.html The issues I'm talking about will not simply be fixed by reading the above. The procedure to get things fixed in OpenStack are long, and probably will not be workable before the next release. Please revert this upload immediately (with an EPOC) and until other packages have reasonable upstream support for it. Thomas Goirand (zigo) ___ 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] Processing of python-babel_1.3+dfsg.1-3_amd64.changes
python-babel_1.3+dfsg.1-3.dsc doesn't exist Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] SQLAlchemy 0.9.X in unstable
Quoting Thomas Goirand (2014-02-23 17:37:54) Please revert this upload immediately (with an EPOC) and until other packages have reasonable upstream support for it. ...or not e.g. 0.9.3-1.really.0.8.something - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature ___ 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] python-django-uuidfield_0.5.0-1_amd64.changes is NEW
binary:python-django-uuidfield is NEW. source:python-django-uuidfield is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. ___ 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] Processing of python-testtools_0.9.35-1_amd64.changes
python-testtools_0.9.35-1_amd64.changes uploaded successfully to localhost along with the files: python-testtools_0.9.35-1.dsc python-testtools_0.9.35.orig.tar.gz python-testtools_0.9.35-1.debian.tar.xz python-testtools_0.9.35-1_all.deb python3-testtools_0.9.35-1_all.deb python-testtools-doc_0.9.35-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ 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] python-testtools_0.9.35-1_amd64.changes is NEW
binary:python-testtools-doc is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
