Bug#1012208: unblock: python-pytest-asyncio/0.18.2-1
On Wed, Jun 01, 2022 at 01:14:31PM +0200, Graham Inggs wrote: > Hi Julian > > On Wed, 1 Jun 2022 at 12:03, Julian Gilbey wrote: > > [ Reason ] > > python-pytest-asyncio and pytest-mock need to be upgraded together; > > pytest-mock 3.7.0-2 build-depends on the newer version of > > python-pytest-asyncio (0.18.2-1), while the older version of > > pytest-mock (3.6.1-1) breaks with it. > > It seems to me that python3-pytest-asyncio misses an appropriate > Breaks on python3-pytest-mock then. > > Regards > Graham Ah, OK; I'll ask the maintainer to put one in. Best wishes, Julian
Bug#1012208: unblock: python-pytest-asyncio/0.18.2-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-pytest-asyncio (Please provide enough (but not too much) information to help the release team to judge the request efficiently. E.g. by filling in the sections below.) [ Reason ] python-pytest-asyncio and pytest-mock need to be upgraded together; pytest-mock 3.7.0-2 build-depends on the newer version of python-pytest-asyncio (0.18.2-1), while the older version of pytest-mock (3.6.1-1) breaks with it. So python-pytest-asyncio can't transition because it will break the version of pytest-mock already in testing, and pytest-mock can't transition because of the build-dependency on the newer python-pytest-asyncio. [ Impact ] (What is the impact for the user if the unblock isn't granted?) python3-jupyter-kernels won't transition, and so I can't get the newer verion of spyder into testing either (I haven't uploaded it to unstable yet, though). [ Tests ] (What automated or manual tests cover the affected code?) It's the autopkgtests that are blocking things; they succeed (at least for me) if the newer versions of both packages are used. [ Risks ] (Discussion of the risks involved. E.g. code is trivial or complex, key package vs leaf package, alternatives available.) A lot of packages use these in their testing suites. [ Checklist ] [ ] all changes are documented in the d/changelog [ ] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing not so relevant here? [ Other info ] (Anything else the release team should know.) unblock python-pytest-asyncio/0.18.2-1
Processed: Re: Bug#1012208: unblock: python-pytest-asyncio/0.18.2-1
Processing commands for cont...@bugs.debian.org: > reassign 1012208 python3-pytest-asyncio Bug #1012208 [release.debian.org] unblock: python-pytest-asyncio/0.18.2-1 Bug reassigned from package 'release.debian.org' to 'python3-pytest-asyncio'. Ignoring request to alter found versions of bug #1012208 to the same values previously set Ignoring request to alter fixed versions of bug #1012208 to the same values previously set > retitle 1012208 python3-pytest-asyncio: please add Breaks: > python3-pytest-mock (<< 3.7.0) Bug #1012208 [python3-pytest-asyncio] unblock: python-pytest-asyncio/0.18.2-1 Changed Bug title to 'python3-pytest-asyncio: please add Breaks: python3-pytest-mock (<< 3.7.0)' from 'unblock: python-pytest-asyncio/0.18.2-1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012208: unblock: python-pytest-asyncio/0.18.2-1
reassign 1012208 python3-pytest-asyncio retitle 1012208 python3-pytest-asyncio: please add Breaks: python3-pytest-mock (<< 3.7.0) thanks Dear Jonas, I've updated python3-pytest-mock to fix #1006736. Unfortunately, the two packages are still not transitioning to testing. I've had the following brief conversation with release.d.o about this: On Wed, Jun 01, 2022 at 12:39:38PM +0100, Julian Gilbey wrote: > On Wed, Jun 01, 2022 at 01:14:31PM +0200, Graham Inggs wrote: > > Hi Julian > > > > On Wed, 1 Jun 2022 at 12:03, Julian Gilbey wrote: > > > [ Reason ] > > > python-pytest-asyncio and pytest-mock need to be upgraded together; > > > pytest-mock 3.7.0-2 build-depends on the newer version of > > > python-pytest-asyncio (0.18.2-1), while the older version of > > > pytest-mock (3.6.1-1) breaks with it. > > > > It seems to me that python3-pytest-asyncio misses an appropriate > > Breaks on python3-pytest-mock then. > > > > Regards > > Graham > > Ah, OK; I'll ask the maintainer to put one in. > > Best wishes, > >Julian Please could you upload a new version of python3-pytest-asyncio which has a Breaks: python3-pytest-mock (<= 3.7.0) clause? Thanks! Julian
Bug#1012208: unblock: python-pytest-asyncio/0.18.2-1
Hi Julian On Wed, 1 Jun 2022 at 12:03, Julian Gilbey wrote: > [ Reason ] > python-pytest-asyncio and pytest-mock need to be upgraded together; > pytest-mock 3.7.0-2 build-depends on the newer version of > python-pytest-asyncio (0.18.2-1), while the older version of > pytest-mock (3.6.1-1) breaks with it. It seems to me that python3-pytest-asyncio misses an appropriate Breaks on python3-pytest-mock then. Regards Graham
Bug#1012223: transition: ace
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: sudipm.mukher...@gmail.com Hi, Small transition with only two affected packages: diagnostics, ivtools, Both of them builds fine with ace 7.0.7+dfsg-1 version in experimental. The autogenerated ben tracker looks good. Please consider 'ace' for transition. Thanks in advance. -- Regards Sudip
Bug#1007222: transition: onetbb
Control: tags -1 + moreinfo Hi I noticed some packages in the tracker not appearing in your list; e.g. openimageio, pcl and yade. These packages have transitive build-dependencies on libtbb-dev through e.g. libopenvdb-dev or libvtk9-dev, and should be investigated as well. Note that we will require fixes, or at least patches, for "key packages" [1] before starting with this transition, and at least trilinos is currently on that list. It may be worth considering again Matthias' suggestion in #1006920 to keep the old tbb package around as libtbb2-dev and libtbb2-doc in order to allow packages like numba to get the new tbb soon, and other packages stuck with the old tbb more time to get fixed. Regards Graham [1] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Processed: Re: Bug#1007222: transition: onetbb
Processing control commands: > tags -1 + moreinfo Bug #1007222 [release.debian.org] transition: onetbb Added tag(s) moreinfo. -- 1007222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1007222: transition: onetbb
On Wed, 2022-06-01 at 20:29 +0200, Graham Inggs wrote: > Control: tags -1 + moreinfo > > I noticed some packages in the tracker not appearing in your list; > e.g. openimageio, pcl and yade. These packages have transitive > build-dependencies on libtbb-dev through e.g. libopenvdb-dev or > libvtk9-dev, and should be investigated as well. My bad. So solely `reverse-depends -b` may miss something. I'll investigate and append results to the transition bug. > Note that we will require fixes, or at least patches, for "key > packages" [1] before starting with this transition, and at least > trilinos is currently on that list. > > It may be worth considering again Matthias' suggestion in #1006920 to > keep the old tbb package around as libtbb2-dev and libtbb2-doc in > order to allow packages like numba to get the new tbb soon, and other > packages stuck with the old tbb more time to get fixed. I personally dislike making the old package libtbb2-dev. How about we make the old src:tbb package go through NEW again with the following renames: libtbb-dev -> libtbb-legacy-dev, this sounds much better than libtbb2-dev because it explains itself to be a to-be-deprecated version. In this way we can finish the transition very quickly and leave longer time for broken packages to migrate to onetbb. For me, submitting patches is as well much easier as I only have to change libtbb-dev -> libtbb-legacy-dev for broken packages.
