Re: First results from running build without python2

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]

Hello,

Thank you for looking into this.

This is a third-party script that came from either Mozilla or RedHat. Maybe they have ported it. If not, it should not be rocket science to do it ourselves. If we do it, we should of course upstream it.

However, can you comment out this package and continue the build? This should be required until you reach the cdrom stage.

If this is the only thing that flags up, we should port the script. If we find another, stronger reason to keep Python 2 around, we do not need to bother and can keep the script this way.

-Michael

> On 3 Aug 2021, at 13:31, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> So with crda and the remaining python2 modules removed the question was if removing python2 from the build ran without any problem or if something was flagged up.
> 
> 
> ca-certificates was flagged up.
> 
> There is a python2 script, certdata2pem.py, which fails if python2 is not present. Running that script with python3 flags up some invalid syntax, unsurprisingly.
> 
> I found some patches in Debian from 2015 for certdata2pem.py to provide python3 compatibility. Unfortunately looking at the patch approx half could not be applied because the lines don't exist in the IPFire version of certdata2pem.py (sections to do with blacklisted certs)
> 
> I then ran the 2to3 converter on certdata2pem.py and tried that in the build but it came up with the following error.
> 
> TypeError: a bytes-like object is required, not 'str'
> 
> 
> I don't know how to further move forward with this as I am totally unfamiliar with the python language.
> 
> 
> Regards,
> 
> Adolf.
> 
>