Hi all, On Thu, 09 Aug 2018 09:32:00 +0000 Niels Thykier <niels@thykier.net> wrote: > 3) Build-Depends are not enforced on removal. That is packages > /can/ be removed while packages are build depending on them. > > Limitation 2+3 are slightly more involved and may take quite a while for > us to implement. Seems like this is really in need of attention. Currently people are working to get rid of Python 2 packages. We currently have multiple packages in testing not able to build due to recent migrations. See https://qa.debian.org/dose/debcheck/src_testing_main/ and the amd64 or each link at the top. texlive-generic-extra was another issue recently and still on that list, I filed bugs for those. The annoying thing of Build-Depends is that they stick around in unstable, exactly because of Build-Depends, hence the packages don't start to fail there. And also autopkgtests runs are happy because they can pull the package from unstable. I may be saying something stupid, but shouldn't the build-depends not *just* be added to the depends in the migration phase? Or is that still quite involved due to -arch/-indep? Paul
Attachment:
signature.asc
Description: OpenPGP digital signature