From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Errors at cdrom stage when building the python3 update package
Date: Mon, 17 Oct 2022 15:08:25 +0100 [thread overview]
Message-ID: <986DFF3E-1D02-4101-84B0-A683A89EDA69@ipfire.org> (raw)
In-Reply-To: <3333c93e-8d01-e0f2-437d-d68cc5b31538@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
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?
-Michael
> On 15 Oct 2022, at 20:25, Adolf Belka <adolf.belka(a)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>
next prev parent reply other threads:[~2022-10-17 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 19:25 Adolf Belka
2022-10-17 14:08 ` Michael Tremer [this message]
2022-10-17 15:42 ` Adolf Belka
2022-10-18 12:31 ` Adolf Belka
2022-11-09 19:07 ` Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=986DFF3E-1D02-4101-84B0-A683A89EDA69@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox