On Wed, 22 Jun 2022 14:13:29 +0200 Bastian Germann <b...@debian.org> wrote: > On Sat, 18 Jun 2022 17:58:24 -0500 "David (Plasma) Paul" > <davidp...@librem.one> wrote: > > markdown-it-py fails to build from source with versions of flit > > earlier than 3.4 according to the package's pyproject.toml.[0] > > Attached is a patch to fix the declared build dependency on flit in > > the debian/control file to match the supported versions listed in > > the package's pyproject.toml file. > > > > [0] However, I was able to get markdown-it-py to build with flit > > 3.3.0-1~bpo11+1, so maybe the value in the pyproject.toml file is > > higher than it strictly needs to be. Regardless of what the actual > > exact minimum value is, I can confirm that flit 3.0.0 is > > insufficient. > > Please do not file RC bugs when a bookworm/sid only package does not > build for bullseye-backports. If you want a backport please express > that intend otherwise this is invalid.
Apologies for the being overzealous with regards to Build-Depends versioning. I will file this sort of report as a wishlist severity bug in the future. Sorry for overstepping. FWIW, my original reasoning for filing this bug went like this: For the sake of ensuring bootstrappability of any release N of Debian by the previous Debian release N-1, the build-dependencies of any release N source package ought to be satisfiable solely by some combination of (A) binary packages from the release N-1 binary archive (B) binary packages built from release N source packages using build-dependencies consisting solely of some combination of A and B In order to aid in this bootstrapping process, the allowed versions of the declared build dependencies of release N source packages should be constrained such that combinations of A and B which satisify the declared dependencies but fail to build the package are eliminated. Again, I'm sorry for being a nuisance and I will try to do better in the future. -- Plasma
