Hi,
On Fri, Jul 08, 2022 at 09:33:10PM +0200, Carsten Schoenert wrote:
> Hi,
>
> Am 16.06.22 um 10:05 schrieb Julian Gilbey:
> ...
> > Great, thanks. Since the pygments in testing fails on pytest 7.2.1,
> > and the version in experimental depends on pytest >= 7.0, we'll need
> > to do the following when we are ready to upload pytest 7.2.1 to
> > unstable:
> >
> > * Mark pytest 7.2.1 as Breaks: pygments (<< 2.12.0)
>
> looking at the autopkgtest on the CI pygments is still failing while testing
> with versions from testing. Mostly because I think as pytest < 7 (from
> testing) is used. All other versions differences are not critical I guess.
> The following list of used packages are given by the different versions
> between testing and unstable.
Yes, indeed; as pygments depends on pytest >= 7 and the version
currently in testing breaks with pytest 7, pytest must declare Breaks:
python3-pygments (<< 2.12.0). [Explanation: britney (?) tries each
package on its own when testing for migration: pytest can't migrate as
that would break pygments in testing, and pygments can't migrate as it
depends on the newer pytest. So we're stuck and neither will
migrate. But if pytest 7 declares a Breaks on pygments (<< 2.12.0),
then it will attempt to migrate both of them simultaneously.]
Best wishes,
Julian
