<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 9 Nov 2020 at 22:20, Matthias Klose <<a href="mailto:doko@debian.org">doko@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10/23/20 1:07 PM, Matthias Klose wrote:<br>
> On 10/18/20 12:13 PM, Matthias Klose wrote:<br>
>> Python 3.9 as a supported Python3 version is now in unstable, and all binNMUs<br>
>> are done (thanks to Graham for the work). Bug reports should be all filed for<br>
>> all known problems [1], and the current state of the 3.9 addition can be seen at<br>
>> [2] (a few of the "bad" are false packages with b-d n python3-all-dev, but not<br>
>> building for 3.9, bug reports also filed).<br>
>><br>
>> The major outstanding issue is the pandas stack, all other problems are found in<br>
>> leaf packages (leaf in the sense of that no other package for the 3.9 addition<br>
>> is blocked).<br>
>><br>
>> Please help fixing the remaining issues!<br>
>><br>
>> Matthias<br>
>><br>
>> [1]<br>
>> <a href="https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.9;users=debian-python@lists.debian.org" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.9;users=debian-python@lists.debian.org</a><br>
>> [2] <a href="https://release.debian.org/transitions/html/python3.9.html" rel="noreferrer" target="_blank">https://release.debian.org/transitions/html/python3.9.html</a><br>
> <br>
> Going on with a test rebuild of 3.9 as default to file bug reports for more<br>
> packages. The first stage1 packages for 3.9 as default [1] can be found at<br>
> <br>
> deb [trusted=yes] <a href="http://people.debian.org/~doko/tmp/python3.9" rel="noreferrer" target="_blank">http://people.debian.org/~doko/tmp/python3.9</a> ./<br>
> deb [trusted=yes] <a href="http://people.debian.org/~ginggs/python3.9-repo" rel="noreferrer" target="_blank">http://people.debian.org/~ginggs/python3.9-repo</a> ./<br>
> <br>
> The first repo just having the python3-defaults packages from experimental. The<br>
> second repo of course will be outdated very soon ... Bug reports for stage1 are<br>
> filed, Graham is now running the test builds for stage2.<br>
> <br>
> The autopkg test results at [2] need checking. There's currently a britney bug<br>
> which marks things as bad, and only gets it right after a week. Plus there's no<br>
> way to select an "unrelated" package from unstable for a test, and have it<br>
> marked as a successful test. So basically you need to wait until all the 3.9<br>
> related fixes migrate to testing for running a successful autopkg test.<br>
> <br>
> Matthias<br>
> <br>
> [1] <a href="https://release.debian.org/transitions/html/python3.9-default.html" rel="noreferrer" target="_blank">https://release.debian.org/transitions/html/python3.9-default.html</a><br>
> [2] <a href="https://tracker.debian.org/pkg/python3-defaults" rel="noreferrer" target="_blank">https://tracker.debian.org/pkg/python3-defaults</a><br>
<br>
- python3-defaults now migrated to testing. The following packages were<br>
removed from testing with fastened hints.<br>
<br>
numba<br>
python-executing<br>
python-fabio<br>
python-icecream<br>
python-molotov<br>
supysonic<br>
<br>
- The Python related ftbfs issues from the last archive test rebuild<br>
were user-tagged with 'python3.9', although I didn't make much<br>
effort to determine if these are ftbfs seen for 3.9 only, or for<br>
both 3.8 and 3.9. dh-python now supports building and testing for<br>
all supported python version before bailing out in case of errors,<br>
but this came too late for the test rebuild.<br>
<br>
issues for key packages (those with lots of dependencies) are:<br>
<br>
<a href="https://bugs.debian.org/973056" rel="noreferrer" target="_blank">https://bugs.debian.org/973056</a> src:sphinx-tabs<br></blockquote><div><br></div><div>Fixed.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://bugs.debian.org/973057" rel="noreferrer" target="_blank">https://bugs.debian.org/973057</a> src:python-py<br></blockquote><div><br></div><div>Fixed.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://bugs.debian.org/973061" rel="noreferrer" target="_blank">https://bugs.debian.org/973061</a> src:nototools<br></blockquote><div><br></div><div>Pasted a trivial fix to the bug. I guess it could be NMUed (it's not a Python team package).</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://bugs.debian.org/973072" rel="noreferrer" target="_blank">https://bugs.debian.org/973072</a> src:python-kubernetes<br></blockquote><div><br></div><div>I patched the failures (see the bug) but then the build hangs for me.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://bugs.debian.org/973087" rel="noreferrer" target="_blank">https://bugs.debian.org/973087</a> src:python-fs<br></blockquote><div><br></div><div>Fixed, but I forgot to put the Closes: #xxx in the changelog.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://bugs.debian.org/973114" rel="noreferrer" target="_blank">https://bugs.debian.org/973114</a> src:python-future<br>
<a href="https://bugs.debian.org/973121" rel="noreferrer" target="_blank">https://bugs.debian.org/973121</a> src:cairocffi<br>
<a href="https://bugs.debian.org/973126" rel="noreferrer" target="_blank">https://bugs.debian.org/973126</a> src:responses<br>
<a href="https://bugs.debian.org/973134" rel="noreferrer" target="_blank">https://bugs.debian.org/973134</a> src:python-webob<br>
<a href="https://bugs.debian.org/973165" rel="noreferrer" target="_blank">https://bugs.debian.org/973165</a> src:pyflakes<br></blockquote><div><br></div><div>Fixed.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://bugs.debian.org/973167" rel="noreferrer" target="_blank">https://bugs.debian.org/973167</a> src:ufonormalizer<br>
<a href="https://bugs.debian.org/973168" rel="noreferrer" target="_blank">https://bugs.debian.org/973168</a> src:pylint<br></blockquote><div><br></div><div>This looks confusing! Upstream is thinking about it but I'm not sure what their ETA is.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<a href="https://bugs.debian.org/973193" rel="noreferrer" target="_blank">https://bugs.debian.org/973193</a> src:parso<br>
<a href="https://bugs.debian.org/973195" rel="noreferrer" target="_blank">https://bugs.debian.org/973195</a> src:python-asyncssh<br>
<a href="https://bugs.debian.org/973239" rel="noreferrer" target="_blank">https://bugs.debian.org/973239</a> src:python-fixtures<br></blockquote><div><br></div><div>Upstream is thinking about this too.</div><div><br></div><div>Cheers,</div><div>mwh</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
For the other ftbfs, see [1].<br>
<br>
Matthias<br>
<br>
[1]<br>
<a href="https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.9;users=debian-python@lists.debian.org" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.9;users=debian-python@lists.debian.org</a><br>
<br>
</blockquote></div></div>