Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #11561 > unrolled thread

pytest 4 and autopkgtest dependency loops

Back to article view | Back to linux.debian.maint.python

Contents

  pytest 4 and autopkgtest dependency loops Scott Talbert <swt@techie.net> - 2019-08-09 18:10 +0200
    Re: pytest 4 and autopkgtest dependency loops Scott Talbert <swt@techie.net> - 2019-08-09 19:30 +0200
      Re: pytest 4 and autopkgtest dependency loops Graham Inggs <ginggs@debian.org> - 2019-08-09 20:10 +0200
        Re: pytest 4 and autopkgtest dependency loops Felix Zielcke <fzielcke@z-51.de> - 2019-08-09 20:30 +0200
    Re: pytest 4 and autopkgtest dependency loops Graham Inggs <ginggs@debian.org> - 2019-08-09 19:30 +0200
      Re: pytest 4 and autopkgtest dependency loops Ondrej Novy <novy@ondrej.org> - 2019-08-09 21:00 +0200

#11561 — pytest 4 and autopkgtest dependency loops

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [next] | [standalone]

#11562

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

[toc] | [prev] | [next] | [standalone]

#11564

On Fri, 9 Aug 2019 at 19:28, Scott Talbert <swt@techie.net> 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.

[toc] | [prev] | [next] | [standalone]

#11565

Am Freitag, den 09.08.2019, 20:05 +0200 schrieb Graham Inggs:
> On Fri, 9 Aug 2019 at 19:28, Scott Talbert <swt@techie.net> 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

[toc] | [prev] | [next] | [standalone]

#11563

Hi Scott

On Fri, 9 Aug 2019 at 18:01, Scott Talbert <swt@techie.net> 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

[toc] | [prev] | [next] | [standalone]

#11566

[Multipart message — attachments visible in raw view] — view raw

Hi,

pá 9. 8. 2019 v 19:22 odesílatel Graham Inggs <ginggs@debian.org> 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ý

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web