From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: First results from running build without python2 Date: Tue, 03 Aug 2021 23:38:30 +0200 Message-ID: <94694aa0-25f9-5e52-181e-f2c69f6f64c9@ipfire.org> In-Reply-To: <1D0E54D9-C82B-408B-9000-10C070DCA8F6@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5170197121900171763==" List-Id: --===============5170197121900171763== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael & all, On 03/08/2021 17:11, Michael Tremer wrote: > Hello, >=20 > Thank you for looking into this. >=20 > 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 oursel= ves. If we do it, we should of course upstream it. I found an updated script from fedora and gave that a try. This time the scri= pt went all the way through but then the build.sh script failed at the point = where it should find all the .crt files in the certs directory and it came ba= ck and said there weren't any. >=20 > However, can you comment out this package and continue the build? This shou= ld be required until you reach the cdrom stage. I then commented ca-certificates out in make.sh and ran the build. This time it stopped at spice-protocol which is an addon and uses the py-comp= ile script that is in automake to compile some python modules. py-compile is python2 based and the build stopped because it could not find p= ython There is a py_compile.py script that is python3 based but when I ran that in = place of the py-compile script I got a Permission denied error when it tried = to carry out the compile. I then commented out spice-protocol and ran the build. It then failed on frr which did look for python3-config but then failed due t= o not finding python-config or pkg-config python It looks like I should be able to tell it to use python3 in the ./configure I commented out frr and nothing else failed before cdrom was reached. So the packages that need to be made to work with python3 are ca-certificates spice-protocol frr I also converted client175 with 2to3 converter and built it and installed the= .ipfire package into a vm and successfully got the WUI page for Media Player= IPFire to render. What I haven't tested yet is if the audio works. I will ne= ed to get audio set up in my vm to try that. Regards, Adolf. >=20 > If this is the only thing that flags up, we should port the script. If we f= ind another, stronger reason to keep Python 2 around, we do not need to bothe= r and can keep the script this way. >=20 > -Michael >=20 >> On 3 Aug 2021, at 13:31, Adolf Belka 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, unsur= prisingly. >> >> I found some patches in Debian from 2015 for certdata2pem.py to provide py= thon3 compatibility. Unfortunately looking at the patch approx half could not= be applied because the lines don't exist in the IPFire version of certdata2p= em.py (sections to do with blacklisted certs) >> >> I then ran the 2to3 converter on certdata2pem.py and tried that in the bui= ld 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 unfamil= iar with the python language. >> >> >> Regards, >> >> Adolf. >> >> >=20 --===============5170197121900171763==--