Re: pytest 4 and autopkgtest dependency loops
Hi, pá 9. 8. 2019 v 19:22 odesílatel Graham Inggs napsal: > I believe the solutions is for python-pytest and python3-pytest to add > Breaks: python-pytest-xdist (<< 1.29.0-1~) > and > Breaks: python3-pytest-xdist (<< 1.29.0-1~) > respectively. > right. Prepared in git: https://salsa.debian.org/python-team/modules/pytest/commit/d7e05b342b11799218fabf7efaa47a80d7823613 will add more Breaks after more pytest compatibility fixies and will do "bigger" upload of pytest later. Thanks a lot. -- Best regards Ondřej Nový
Re: pytest 4 and autopkgtest dependency loops
Am Freitag, den 09.08.2019, 20:05 +0200 schrieb Graham Inggs: > On Fri, 9 Aug 2019 at 19:28, Scott Talbert wrote: > > Thanks. As an aside, what does the tilde at the end of the version > > number > > mean? I have seen that in control files before, but I've been > > unable to > > find anything in the documentation about it. > > The tilde is to accommodate backports. > > e.g. a backport of python-pytest-xdist might be versioned 1.29.0- > 1~bpo10+1 > in that case, it would still be broken by (<< 1.29.0-1) without the > tilde. The general meaning of the tilde is that it's lower then the empty string. So that 1.0-1 is considered newer then 1.0-1~foo
Re: pytest 4 and autopkgtest dependency loops
On Fri, 9 Aug 2019 at 19:28, Scott Talbert wrote: > Thanks. As an aside, what does the tilde at the end of the version number > mean? I have seen that in control files before, but I've been unable to > find anything in the documentation about it. The tilde is to accommodate backports. e.g. a backport of python-pytest-xdist might be versioned 1.29.0-1~bpo10+1 in that case, it would still be broken by (<< 1.29.0-1) without the tilde.
Re: pytest 4 and autopkgtest dependency loops
On Fri, 9 Aug 2019, Graham Inggs wrote: However, there's one package that seems like it is going to cause a problem. I uploaded pytest-xdist 1.29.0-1, which *requires* pytest 4, so pytest-xdist won't migrate to testing until pytest 4 does. On the other hand, pytest 4 won't migrate to testing until all its autopkgtest failures (which include pytest-xdist) clear (right?). So it seems we have a loop here. How do we resolve it? I believe the solutions is for python-pytest and python3-pytest to add Breaks: python-pytest-xdist (<< 1.29.0-1~) and Breaks: python3-pytest-xdist (<< 1.29.0-1~) respectively. Thanks. As an aside, what does the tilde at the end of the version number mean? I have seen that in control files before, but I've been unable to find anything in the documentation about it. Scott
Re: pytest 4 and autopkgtest dependency loops
Hi Scott On Fri, 9 Aug 2019 at 18:01, Scott Talbert wrote: > However, there's one package that seems like it is going to cause a > problem. I uploaded pytest-xdist 1.29.0-1, which *requires* pytest 4, so > pytest-xdist won't migrate to testing until pytest 4 does. On the other > hand, pytest 4 won't migrate to testing until all its autopkgtest failures > (which include pytest-xdist) clear (right?). So it seems we have a loop > here. How do we resolve it? I believe the solutions is for python-pytest and python3-pytest to add Breaks: python-pytest-xdist (<< 1.29.0-1~) and Breaks: python3-pytest-xdist (<< 1.29.0-1~) respectively. Regards Graham
pytest 4 and autopkgtest dependency loops
Hi, Ondřej, I saw you uploaded pytest 4. This has caused autopkgtest failures in a few of the packages I maintain, which I've been working on fixing. I think those should be fine once they migrate to testing, as it should clear the autopkgtest failure from pytest 4. However, there's one package that seems like it is going to cause a problem. I uploaded pytest-xdist 1.29.0-1, which *requires* pytest 4, so pytest-xdist won't migrate to testing until pytest 4 does. On the other hand, pytest 4 won't migrate to testing until all its autopkgtest failures (which include pytest-xdist) clear (right?). So it seems we have a loop here. How do we resolve it? Scott
