Bug#1001371: pytest-twisted: (autopkgtest) needs update for python3.10: E {'warnings': 2} != {'warnings': 1}
On 25/01/2022 23:22, peter green wrote: The upstream report at https://github.com/pytest-dev/pytest-twisted/issues/146 was closed as the additional warning is produced by Twisted. The Twisted fix isn't merged yet. It looks like the twisted fix has now been merged upstream, does it make sense to apply it as a patch to the Debian twisted patch to solve this bug? The good news is that the twisted fix has been incorporated into a new upstream version, which has been uploaded to Debian. I told debci to re-run the test in unstable and it confirmed it was fixed. https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pytest-twisted/19192829/log.gz The not so good news is it's currently blocked from migrating to testing by an autopkgtest failure in gavodachs. I just filed a rc bug report for that. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005725
Bug#1001371: pytest-twisted: (autopkgtest) needs update for python3.10: E {'warnings': 2} != {'warnings': 1}
The upstream report at https://github.com/pytest-dev/pytest-twisted/issues/146 was closed as the additional warning is produced by Twisted. The Twisted fix isn't merged yet. It looks like the twisted fix has now been merged upstream, does it make sense to apply it as a patch to the Debian twisted patch to solve this bug? The removal of pytest-twisted from testing has caused two packages to have uninstallable build-dependencies in testing, graphql-relay and python-promise
Bug#1001371: pytest-twisted: (autopkgtest) needs update for python3.10: E {'warnings': 2} != {'warnings': 1}
The upstream report at https://github.com/pytest-dev/pytest-twisted/issues/146 was closed as the additional warning is produced by Twisted. The Twisted fix isn't merged yet. TBH as I don't need this package anymore (python3-scrapy doesn't use it anymore) I'm considering orphaning it. -- WBR, wRAR signature.asc Description: PGP signature
