[Python-modules-team] Bug#911271: [Pkg-privacy-maintainers] Bug#911271: foolscap: (Build) Depends on non existing python-txtorcon

[Julian Taylor]

On 18.10.18 14:31, Julian Taylor wrote:
> On 18.10.18 14:28, Antoine Beaupré wrote:
>> On 2018-10-18 13:26:28, Julian Taylor wrote:
>>> On 18.10.18 01:07, Antoine Beaupré wrote:
>>>> On 2018-10-18 00:16:15, Sebastian Andrzej Siewior wrote:
>>>>> Package: foolscap
>>>>> Version: 0.13.1-1
>>>>> Severity: serious
>>>>>
>>>>> txtorcon does not build the Python2 variant (python-txtorcon) since its
>>>>> last upload, only the python3 one (python3-txtorcon) remains.
>>>>>
>>>>> As of now the package can't be built due to missing packages.
>>>>
>>>> Seems to me foolscap should be ported to python rather than to force
>>>> txtorcon to support a (soon to be) obsolete version of python. :)
>>>>
>>>
>>> foolscap is based on twisted which seems to have gotten python3 support
>>> recently. First one has to check if foolscap can work with python3 twisted.
>>>
>>> Please do not remove python2 packages from the bottom up, start from the
>>> dependency leaves and work down instead of just breaking everything above.
>>> txtorcon still supports python2 according to their github page.
>>
>> If you look at the txtorcon removal, you'll see it fixed RC bugs about
>> the py2 version, so it was not just a gratitious change...
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905253
>>
>> A.
>>
> 
> that bug looks more like a packaging error or fixable installation error
> than a bug in the py2 version.
> removing the py2 package making other packages rc buggy looks like
> overkill without prior consultation of reverse dependencies.
> 

sorry I may have been a bit brief. The bug you are referencing is the
error output of the pycompile step during package installation. The
python2 package installs a python3 only file (not the py3.py ending) so
it fails.
This can be caused by either upstreams installer incorrectly installing
py3 files in the py2 variant (as upstream installation usually does not
have this pycompile step a stray py3 file does not harm much) or less
likely the package installs the file in the wrong package.
In any case the fix should be simple, the package can take care to not
install py3 files in the py2 package. I can help by providing a patch if
this solution is acceptable.

Regardless we should check if foolscap can also use python3.
But even if that is possible I still would like to keep the python2
version as foolscap and twisted only so recently got py3 support users
will still need the python2 versions for a while until those that had to
wait for migration can migrate.