[Pkg-mozext-maintainers] Bug#937085: Bug#937085: mozilla-devscripts: Python2 removal in sid/bullseye

[Jann Haber]

I created an MR on Salsa to drive this a little bit forward. I found in the output of configure, that it reported python -> no. This is likely the cause of the python bindings missing later. The MR contains a patch to make configure use python3. Then the compilation does not fail anymore.

I however still don't think it works correctly - dh_missing reports there are missing files and 0 files in the python3 package. I'm not so experienced in packaging, so I was unable to fix this, but maybe the finding above help somebody else :)

https://salsa.debian.org/debian/redland-bindings/-/merge_requests/1

On Mon, 10 Feb 2020 14:47:36 -0500 Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
> On Sun 2019-11-03 22:50:59 +0100, Benjamin Drung wrote:
> > I ported amo-changelog and xpi-repack to Python 3 in version 0.54, but I
> > wasn't able to port all scripts, because there is no Python 3 version of
> > redland-bindings (see Debian bug #780741).
> 
> Afaict, upstream redland-bindings claims to support python3:
> http://librdf.org/bindings/RELEASE.html#rel1_0_17_1
> 
> see also http://bugs.librdf.org/mantis/view.php?id=549
> 
> but this is from many years ago, and afaict, there has been no
> additional work upstream on redland bindings since then.
> 
> Worse, i've been unable to make any of this build against python3.  You
> can see my (failed) attempts at preparing an NMU.  I've published them
> to salsa on the WIP-python3 branch at
> https://salsa.debian.org/debian/redland-bindings if anyone wants to try
> to improve.
> 
> So at any rate, i don't see how to get a python3-librdf package easily
> into debian to unblock the mozilla-devscripts transition to python3.
> But i do note that python3-rdflib has been in debian for a
> while. (that's a totally different RDF python module)
> 
> I haven't looked into it myself, but perhaps mozilla-devscripts could
> drop the use of redland and use rdflib instead?
> 
> Sorry to not have more effective progress to suggest.  I'm probably not
> going to have time to work more on this, but i wanted to note where i
> got to, and where i got stuck if someone else wants to pick it up.
> 
>      --dkg