Control: forwarded -1 https://release.debian.org/transitions/html/python3.6.html
On 28/06/17 23:46, Scott Kitterman wrote: > Package: release.debian.org > Severity: normal > User: release.debian....@packages.debian.org > Usertags: transition > > We would like to add python3.6 as a supported python3 version along with > python3.5. This is not exactly like a normal transition. Only transient > unbuildability of higher level packages is to be expected. > > As usual, we are planning a three step transition from python3.5 to python3.6. > > Adding python3.6 as supported is first. > > Once that is complete, we'll file another request to make python3.6 the > default python3. This step does not need to immediately follow the first. > > After that, we'll drop python3.5 as a supported version (other than needing a > tracker, that step doesn't need any support from the release team and won't > entangle anything as buildability of packages is not implicated). Sure, should be all fine. For the first step, have you done a rebuild? Do or should all rdeps that build modules for all supported python versions works fine with 3.6, or are there some bugs / ftbfs issues? > Ben file: > > title = "python3-defaults"; > is_affected = .depends ~ "python3-all-dev"; You probably meant build-depends, but I prefer to use depends as otherwise there usually are too many unknowns. Hopefully the tracker (similar to the python3.5 one) is fine. Emilio > is_good = .depends ~ "python3 (<< 3.7)"; > is_bad = .depends ~ "python3 (<< 3.6)"; > > Scott K > >
