On 28/11/2018 14:07, Axel Beckert wrote: > Hi, > > https://release.debian.org/transitions/html/python3.7-default.html > says: "Affected: .build-depends ~ /python3-dev/" > > But that doesn't suffice, there's likely a "| .build-depends ~ > /python3-all-dev/" missing.
That would introduce a lot of false positives, because most packages that build-dep on python3-all-dev are not affected by the default change, as they should already build for all the supported versions, including python3.7. I would prefer to handle this via is_affected: .depends ~ /python3 (<</ or similar. > Affected source package is e.g. libarcus whose binary package > python3-arcus is currently uninstallable, but has no python3-dev in > the build-dependencies: > > Build-Depends: debhelper (>= 10.2.1), cmake (>= 2.8.12), dh-python, > libprotobuf-dev (>= 3.0.0), libprotoc-dev (>= 3.0.0), > protobuf-compiler (>= 3.0.0), python3-all-dev, python3-sip-dev > > The same counts for python3-savitar and src:libsavitar: > > Build-Depends: debhelper (>= 10.2.1), cmake (>= 2.8.12), dh-python, > libpugixml-dev (>= 1.7), python3-all-dev, python3-sip-dev (>= > 4.19.12+dfsg-1) | python3-sip-dev (<< 4.19.11+dfsg-1) > > P.S.: I'm not subscribed to the bug report, please Cc on reply. > Reply-To is set. Both packages binNMUed. Cheers, Emilio
