Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)
Scott Kitterman writes: > We haven't started the transition yet. When it starts, binNMU should > be enough for most of the packages. When will you start the transition? -- Brian May
Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)
On November 28, 2015 7:21:57 PM EST, Brian May wrote: >Ben Finney 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 >> 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
Re: Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)
Ben Finney 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 > 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. -- Brian May
Which bug report is tracking the “python3 is Python 3.5” transition? (was: Packaging Python that requires 3.5)
Brian May writes: > However I don't know much about this Python 3.5 transition, or what > the current waiting point is. 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 https://wiki.debian.org/Teams/ReleaseTeam/Transitions>. A transition is initiated by a bug report against ‘release.debian.org’, tagged with the user-tag “transition”. You can check current transitions https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=release.debian@packages.debian.org;tag=transition>. The transition of default ‘python3’ to Python 3.5 does not appear in that set, so I'm not sure how it's being tracked. The prior transition – to add support for Python 3.5 – is at https://bugs.debian.org/798999> and refers to future transitions. I think maybe the “default python3 is Python 3.5” transition has somehow become entangled with that prior one. > Is there anything that can be done to help? Have a read through the log for bug#798999 and see whether they're waiting on something we can help with. -- \ “Are you pondering what I'm pondering?” “I think so, ... Brain, | `\but how can we get seven dwarves to shave their legs?” —_Pinky | _o__) and The Brain_ | Ben Finney
