Dear maintainer(s),

With a recent upload of sqlalchemy the autopkgtest of sqlacodegen fails
in testing when that autopkgtest is run with the binary packages of
sqlalchemy from unstable. It passes when run with only packages from
testing. In tabular form:

                        pass            fail
sqlalchemy             from testing    2.0.31+ds1-1
sqlacodegen            from testing    3.0.0~rc3-2
all others             from testing    from testing

The package of sqlacodegen in unstable isn't affected and it also has
this in the changelog: "Require sqlalchemy version 2+". So it seems to
me that the new version of sqlalchemy Breaks the version of sqlacodegen
in testing. To avoid surprises during (partial) upgrades, maybe a
versioned Breaks is appropriate? With the versioned Breaks, britney2
(the migration software) can also figure out that the packages need to
go together, schedule the autopkgtest with both packages from unstable,
so it will not show the regression. If this happens to be a test only
issue (given the changelog entry and the versioned (Build-)Depends I
doubt this) and you don't want to add the versioned Breaks, please let
the Release Team know, such that we can apply the right tricks.

I copied some of the output at the bottom of this report.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=sqlalchemy

https://ci.debian.net/data/autopkgtest/testing/amd64/s/sqlacodegen/48418754/log.gz

=================================== FAILURES
===================================
  61s _____________________________ test_cli_declarative