From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Errors at cdrom stage when building the python3 update package Date: Tue, 18 Oct 2022 14:31:48 +0200 Message-ID: In-Reply-To: <35e72e13-6a07-67b4-999b-8898b760a043@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0696990582944126483==" List-Id: --===============0696990582944126483== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael and all, On 17/10/2022 17:42, Adolf Belka wrote: > Hi Michael, > > On 17/10/2022 16:08, Michael Tremer wrote: >> Hello Adolf, >> >> Interesting problem. >> >> It might be that you have some lines in any of the root files starting wit= h =E2=80=9C-=E2=80=9C. >> >> Therefore tar might be interpreting this as command line options, but not = recognise them. >> >> Does this help? > Absolutely. > > I checked most of the rootfiles for both +'s and -'s but going back and loo= king at them all again I found three with -'s that I had not removed. One of = those was the python3 rootfile itself so it had 85 lines with - at the start. > > I will re-do the build again after fixing those three rootfiles and I expec= t it to work then. > That problem was solved but I have now found three programs that have not bee= n updated where the change of python from 10.3.1 to 10.3.8 has changed their = rootfiles significantly. libplist has lost one line in the log rootfile #usr/bin/plistutil #usr/include/plist #usr/include/plist/Array.h #usr/include/plist/Boolean.h #usr/include/plist/Data.h #usr/include/plist/Date.h #usr/include/plist/Dictionary.h #usr/include/plist/Integer.h #usr/include/plist/Key.h #usr/include/plist/Node.h #usr/include/plist/Real.h #usr/include/plist/String.h #usr/include/plist/Structure.h #usr/include/plist/Uid.h #usr/include/plist/plist++.h #usr/include/plist/plist.h #usr/lib/libplist++-2.0.la #usr/lib/libplist++-2.0.so usr/lib/libplist++-2.0.so.3 usr/lib/libplist++-2.0.so.3.3.0 #usr/lib/libplist-2.0.la #usr/lib/libplist-2.0.so usr/lib/libplist-2.0.so.3 usr/lib/libplist-2.0.so.3.3.0 #usr/lib/pkgconfig/libplist++-2.0.pc #usr/lib/pkgconfig/libplist-2.0.pc #usr/share/man/man1/plistutil.1 -usr/lib/python3.10/site-packages/plist.so I can't tell if this is a problem or not. It was the only file in site-packag= es for this program. iotop has the following list in the log rootfile +usr/bin/iotop +usr/lib/python3.10/site-packages/iotop-0.6-py3.10.egg -usr/lib/python3.10/site-packages/iotop -usr/sbin/iotop All the 10 previously commented out lines are gone. the iotop binary has moved from sbin to bin. This is despite the section in s= etup.py labelled as a dirty hack to ensure iotop is put in sbin instead of bi= n. That no longer seems to work with python3.10.8 Not sure how to fix this in setup.py. There is nothing about this in the ioto= p git repository. I could just adjust the lfs file to move iotop from bin to sbin after the ins= tall has been run but not sure if that is the best thing to do or not. python3-flit has added the following lines in the log rootfile +root/.cache +root/.cache/pip +root/.cache/pip/selfcheck +root/.cache/pip/selfcheck/241e69162522ccf5846a2f42ebc24b17464915a155679666b8= 9a9f31 I have never seen anything like this before and it definitely looks wrong but= I don't know what to do to fix it. There is no new update of flit that might= fix it flit is built using pip so maybe something changed between python-3.10.1 and = python-3.10.8 with pip but I couldn't find anything obvious looking through t= he change logs and I don't understand all the commands in the lfs file for fl= it to be able to try and adjust it. Any suggestion would be gladly accepted for how to deal with the above three = packages. Once these three are dealt with then that should be it for the python3 update= as the build got to the end without any further flags about rootfiles or any= thing else.=C2=A0 Then I would need to do some testing to make sure IPFire st= ill works before I submit a large patch set again. Regards, Adolf. > Thanks very much for the help. > > Regards, > Adolf. >> >> -Michael >> >>> On 15 Oct 2022, at 20:25, Adolf Belka wrote: >>> >>> Hi everyone, >>> >>> I have been working on the python3 update. With python3 updated then some= of the individual python packages required to be updated as they failed to b= uild. >>> >>> >>> To make it simpler I updated all the python3 packages that had new versio= ns and this also resulted in some rust packages needing to be updated. After = several rounds then everything built without any problems until it came to th= e cdrom stage. >>> >>> >>> I got the following errors and I have no idea what I have done wrong to m= ake this happen. The error messages unfortunately aren't much help to me. >>> >>> Can anyone help with what the issue is causing the attached log file erro= rs. >>> >>> >>> Regards, >>> >>> Adolf. >>> <_build.packages.log> >> --===============0696990582944126483==--