On November 28, 2015 7:21:57 PM EST, Brian May <b...@debian.org> wrote: >Ben Finney <ben+deb...@benfinney.id.au> writes: > >> API/ABI transitions (such as switching default Python 3 to be PYthon >> 3.5) are managed by the release team, with a workflow described at >> <URL:https://wiki.debian.org/Teams/ReleaseTeam/Transitions>. > >There is https://release.debian.org/transitions/html/python3.5.html > >Still trying to work out what the "Dependency level n" headers mean. > >What are the implications of the "Collisions" section? Looks like >packages in multiple transitions. > >Are the orange packages a problem or not? So if the build is failing on >a platform it will get an orange status as well as if it doesn't meet >the good or bad criteria. > >If I understand this correctly, all packages as part of the transition >get uploaded to experimental, and then get moved at once to unstable? > >Unfortunately the >https://release.debian.org/transitions/html/python3.5.html page doesn't >indicate if somebody is already working on the package or not. > >I would have thought binNMU would be sufficient for some of these >packages, however maybe these easy targets have already been fixed now? > >> Have a read through the log for bug#798999 and see whether they're >> waiting on something we can help with. > >Not that I can see. So maybe that means any of the red packages on the >transition tracking page. > >Some of the packages look like they are broken with no immediate fix, >maybe should get removed from unstable *if* inclusion in unstable is >holding up the transition. e.g. openturns.
We haven't started the transition yet. When it starts, binNMU should be enough for most of the packages. Scott K