Your message dated Mon, 5 Aug 2019 08:37:11 +0000
with message-id <a2ea97c3f378dd046fd4398d930478da8a977a2c.ca...@firma.seznam.cz>
and subject line Re: python3-pytest: pytest v4 breaks existing tests
has caused the Debian Bug report #933914,
regarding python3-pytest: pytest v4 breaks existing tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
933914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pytest
Version: 4.6.4-1
Severity: serious
Justification: breaks autopkgtest tests
Control: affects -1 + src:apipkg src:betamax src:ccdproc src:chardet
Control: affects -1 + src:dask src:django-axes src:doit src:drms
Control: affects -1 + src:fiat src:mpi4py src:pandas src:pygalmesh
Control: affects -1 + src:pyjwt src:pytest-sugar src:pytest-xdist
Control: affects -1 + src:pytest-xvfb src:python-dbfread
Control: affects -1 + src:python-dugong src:python-graphviz
Control: affects -1 + src:python-hypothesis src:python-parameterized
Control: affects -1 + src:python-transliterate src:setuptools-scm
Control: affects -1 + src:spyder-line-profiler src:spyder-reports
Control: affects -1 + src:spyder-unittest src:sudsy
python3-pytest v4 has changed the pytest API, causing many existing
tests to fail.
This upgrade should be treated as a Transition, uploading the package to
experimental first.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages python3-pytest depends on:
ii python3 3.7.3-1
ii python3-atomicwrites 1.1.5-2
ii python3-attr 18.2.0-1
ii python3-importlib-metadata 0.18-2
ii python3-more-itertools 4.2.0-1
ii python3-packaging 19.0-1
ii python3-pkg-resources 41.0.1-1
ii python3-pluggy 0.12.0-1
ii python3-py 1.8.0-1
ii python3-six 1.12.0-1
ii python3-wcwidth 0.1.7+dfsg1-6
python3-pytest recommends no packages.
python3-pytest suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Tags: wontfix
Hi Drew,
On Mon, 05 Aug 2019 11:43:39 +0800 Drew Parsons <dpars...@debian.org>
wrote:> This upgrade should be treated as a Transition, uploading the
package to> experimental first.
We are not using Transitions for Python upgrades because almost every
module upgrade breaks something. It's too much overhead for us. Last
time I uploaded pytest to experimental first and send information to
ML, nothing happened [1].
Because we have autopkgtest migration test, this package will not
migrate to testing until compatibility issues are fixed. So there is
not breakage of testing.
Because this is build-depends related and we don't have "build-depends-
break" there is nothing I can do in pytest package itself.
Please create individual FTBFS bugs for affected packages and maybe tag
them with something like "pytest4".
Thank you.
[1] https://lists.debian.org/debian-python/2018/11/msg00016.html
--
Best regards Ondřej Nový
signature.asc
Description: This is a digitally signed message part
--- End Message ---
