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 with “-“.
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 looking 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 expect it to work then.
Thanks very much for the help.
Regards, Adolf.
-Michael
On 15 Oct 2022, at 20:25, Adolf Belka adolf.belka@ipfire.org 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 build.
To make it simpler I updated all the python3 packages that had new versions 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 the cdrom stage.
I got the following errors and I have no idea what I have done wrong to make 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 errors.
Regards,
Adolf. <_build.packages.log>