Hi,
pá 23. 11. 2018 v 13:21 odesílatel Ole Streicher
napsal:
> By reading the upstream changelog, I could not find a cause what should
> cause the incompatibility. Also, the logs now all contain a warning like
>
me either. :(
> /usr/lib/python2.7/dist-packages/_pytest/cacheprovider.py:58
>
bibtexparser_1.0.1+ds-1_amd64.changes uploaded successfully to localhost
along with the files:
bibtexparser_1.0.1+ds-1.dsc
bibtexparser_1.0.1+ds.orig.tar.xz
bibtexparser_1.0.1+ds-1.debian.tar.xz
bibtexparser_1.0.1+ds-1_amd64.buildinfo
python-bibtexparser-doc_1.0.1+ds-1_all.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 23 Nov 2018 16:22:39 +
Source: bibtexparser
Binary: python-bibtexparser python3-bibtexparser python-bibtexparser-doc
Architecture: source all
Version: 1.0.1+ds-1
Distribution: unstable
Urgency: medium
Package: python-pytest
Version: 3.9.3-2
Severity: serious
Affects: python-astropy, python-ccdproc, astropy-healpix, python-drizzle
Dear maintainer,
many astronomy Python packages rely on pytest for build and CI tests.
The Python 2 tests are now broken with the new version of pytest, since
the
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 23 Nov 2018 08:55:24 +0100
Source: path.py
Binary: python-path python3-path
Architecture: source
Version: 11.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Ondřej
Hi Ondrey,
newer astropy (>= 3.x) is limited to Python 3.x, and the problem appears
only with Python 2.7. The "python-astropy" package mentioned in the
Affects field of the bug is the stable (but supported) version 2.0.x,
which is (now) Python-2 only. The other packages mentioned there support
path.py_11.5.0-3_source.changes uploaded successfully to localhost
along with the files:
path.py_11.5.0-3.dsc
path.py_11.5.0-3.debian.tar.xz
path.py_11.5.0-3_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
setuptools-scm_3.1.0-2_source.changes uploaded successfully to localhost
along with the files:
setuptools-scm_3.1.0-2.dsc
setuptools-scm_3.1.0-2.debian.tar.xz
setuptools-scm_3.1.0-2_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Hi Ole,
this looks like bug in astropy and other packages. They are just not
compatible with newer pytest.
For example astropy upstream uses pytest 3.9 and/or 3.10 for testing code,
see
https://github.com/astropy/astropy/commit/3e34e7c450ebd982978423d8774ef6953832f610
I tried to build simple
python3-dulwich_0.19.9-2~bpo9+1_amd64.deb: trying to install to backports-new,
but could not find source
binary:python3-dulwich is NEW.
binary:pypy-dulwich is NEW.
binary:python-dulwich is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were
pytest_3.10.1-1_source.changes uploaded successfully to localhost
along with the files:
pytest_3.10.1-1.dsc
pytest_3.10.1.orig.tar.gz
pytest_3.10.1-1.debian.tar.xz
pytest_3.10.1-1_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
python3-dulwich_0.19.9-2~bpo9+1_amd64.deb: trying to install to backports-new,
but could not find source
binary:python3-dulwich is NEW.
binary:pypy-dulwich is NEW.
binary:python-dulwich is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were
Processing control commands:
> tag -1 pending
Bug #914420 [python-pytest] python-pytest: Breaks many Python 2 test suites
Added tag(s) pending.
--
914420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
python-pyvmomi_6.7.1-2~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
python-pyvmomi_6.7.1-2~bpo9+1.dsc
python-pyvmomi_6.7.1-2~bpo9+1.debian.tar.xz
python-pyvmomi-doc_6.7.1-2~bpo9+1_all.deb
python-pyvmomi_6.7.1-2~bpo9+1_all.deb
Processing control commands:
> tag -1 pending
Bug #881565 [python3-acoustid] python-acoustid: incompatible with python3 (fix
availble upstream)
Bug #881566 [python3-acoustid] python-acoustid: incompatible/broken on Python 3
(fix available upstream)
Added tag(s) pending.
Added tag(s) pending.
Processing control commands:
> tag -1 pending
Bug #878623 [python-acoustid] python-acoustid: acoustid.fingerprint_file(p)
fails with TypeError: data must be bytes, buffer, or memoryview
Added tag(s) pending.
--
878623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878623
Debian Bug
dulwich_0.19.9-2~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
dulwich_0.19.9-2~bpo9+1_amd64.buildinfo
pypy-dulwich-dbgsym_0.19.9-2~bpo9+1_amd64.deb
pypy-dulwich_0.19.9-2~bpo9+1_amd64.deb
python-dulwich-dbgsym_0.19.9-2~bpo9+1_amd64.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 23 Nov 2018 18:59:56 +0100
Source: pytest
Binary: pypy-pytest python-pytest python-pytest-doc python3-pytest
Architecture: source
Version: 3.10.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python
Your message dated Fri, 23 Nov 2018 23:58:02 +
with message-id
and subject line Bug#881565: fixed in pyacoustid 1.1.5-1
has caused the Debian Bug report #881565,
regarding python-acoustid: incompatible with python3 (fix availble upstream)
to be marked as done.
This means that you claim that
Your message dated Fri, 23 Nov 2018 23:58:02 +
with message-id
and subject line Bug#881565: fixed in pyacoustid 1.1.5-1
has caused the Debian Bug report #881565,
regarding python-acoustid: incompatible/broken on Python 3 (fix available
upstream)
to be marked as done.
This means that you
Your message dated Fri, 23 Nov 2018 23:58:02 +
with message-id
and subject line Bug#878623: fixed in pyacoustid 1.1.5-1
has caused the Debian Bug report #878623,
regarding python-acoustid: acoustid.fingerprint_file(p) fails with TypeError:
data must be bytes, buffer, or memoryview
to be
Your message dated Fri, 23 Nov 2018 19:23:50 +
with message-id
and subject line Bug#914420: fixed in pytest 3.10.1-1
has caused the Debian Bug report #914420,
regarding python-pytest: Breaks many Python 2 test suites
to be marked as done.
This means that you claim that the problem has been
binary:python-pyvmomi is NEW.
binary:python-pyvmomi-doc is NEW.
binary:python3-pyvmomi is NEW.
binary:python-pyvmomi is NEW.
binary:python-pyvmomi-doc is NEW.
binary:python3-pyvmomi is NEW.
source:python-pyvmomi is NEW.
Your package has been put into the NEW queue, which requires manual action
dulwich_0.19.9-2~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
dulwich_0.19.9-2~bpo9+1_amd64.buildinfo
pypy-dulwich-dbgsym_0.19.9-2~bpo9+1_amd64.deb
pypy-dulwich_0.19.9-2~bpo9+1_amd64.deb
python-dulwich-dbgsym_0.19.9-2~bpo9+1_amd64.deb
dulwich_0.19.9-2~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
dulwich_0.19.9-2~bpo9+1_amd64.buildinfo
pypy-dulwich-dbgsym_0.19.9-2~bpo9+1_amd64.deb
pypy-dulwich_0.19.9-2~bpo9+1_amd64.deb
python-dulwich-dbgsym_0.19.9-2~bpo9+1_amd64.deb
python3-dulwich_0.19.9-2~bpo9+1_amd64.deb: trying to install to backports-new,
but could not find source
binary:python3-dulwich is NEW.
binary:pypy-dulwich is NEW.
binary:python-dulwich is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were
binary:pypy-dulwich is NEW.
binary:python-dulwich is NEW.
binary:python3-dulwich is NEW.
binary:python3-dulwich is NEW.
binary:pypy-dulwich is NEW.
binary:python-dulwich is NEW.
source:dulwich is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to
flask-wtf 0.14.2-2 is marked for autoremoval from testing on 2018-12-10
It is affected by these RC bugs:
912069: flask-wtf: flask-wtf FTBFS: FAIL: test_i18n_enabled
(tests.test_i18n.TestI18NCase)
___
Python-modules-team mailing list
dulwich_0.19.9-2~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
dulwich_0.19.9-2~bpo9+1.dsc
dulwich_0.19.9.orig.tar.gz
dulwich_0.19.9-2~bpo9+1.debian.tar.xz
dulwich_0.19.9-2~bpo9+1_amd64.buildinfo
pypy-dulwich-dbgsym_0.19.9-2~bpo9+1_amd64.deb
flask-mongoengine 0.9.3-2 is marked for autoremoval from testing on 2018-12-10
It (build-)depends on packages with these RC bugs:
912069: flask-wtf: flask-wtf FTBFS: FAIL: test_i18n_enabled
(tests.test_i18n.TestI18NCase)
___
Python-modules-team
Package: python3-wget
Version: 3.2-1
Severity: normal
python3-wget has the following in it's Depends:
Depends: python-urllib3, ${misc:Depends}, ${python3:Depends}
Unfortunately, python-urllib3 is both wrong and unnecessary. It is wrong
because a python3 package needs to depend on the python3
31 matches
Mail list logo
