From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <986DFF3E-1D02-4101-84B0-A683A89EDA69@ipfire.org>
In-Reply-To: <3333c93e-8d01-e0f2-437d-d68cc5b31538@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0157251813152875794=="
List-Id: <development.lists.ipfire.org>

--===============0157251813152875794==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Adolf,

Interesting problem.

It might be that you have some lines in any of the root files starting with =
=E2=80=9C-=E2=80=9C.

Therefore tar might be interpreting this as command line options, but not rec=
ognise them.

Does this help?

-Michael

> On 15 Oct 2022, at 20:25, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>=20
> Hi everyone,
>=20
> I have been working on the python3 update. With python3 updated then some o=
f the individual python packages required to be updated as they failed to bui=
ld.
>=20
>=20
> 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 se=
veral rounds then everything built without any problems until it came to the =
cdrom stage.
>=20
>=20
> I got the following errors and I have no idea what I have done wrong to mak=
e this happen. The error messages unfortunately aren't much help to me.
>=20
> Can anyone help with what the issue is causing the attached log file errors.
>=20
>=20
> Regards,
>=20
> Adolf.
> <_build.packages.log>


--===============0157251813152875794==--