From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject:
 Re: Incorrect naming convention used on the Core Update 170 download file.
Date: Sun, 18 Sep 2022 14:55:27 +0200
Message-ID: <f7c70ac5-a9ac-f6b6-3026-93da6350c5ef@ipfire.org>
In-Reply-To: <3F393EB4-1500-4548-B0B1-DF478538D125@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2265724181925200777=="
List-Id: <development.lists.ipfire.org>

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

On 18.09.2022 11:23, Michael Tremer wrote:
> Hello,
>=20
> This fucking feature will kill me some time. Or I will kill it.

+1

I would testify as a witness for you...
Three years probation and then you would be out again. ;-)

> Matthias, are you going to submit this change as a patch?=20

Patch is on the road - see below:

https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommit;h=3Dfbd0608c2cb5372fff7=
857065ec7e605b1bf9cf7

> -Michael
>=20
>> On 17 Sep 2022, at 11:28, Matthias Fischer <matthias.fischer(a)ipfire.org>=
 wrote:
>>=20
>> Hi,
>>=20
>> Confirmed. Somehow the name of the ISO has changed.
>>=20
>> But - correct me if I'm wrong! - the naming of the ISO file takes place
>> in '/usr/local/bin/backupiso':
>>=20
>> Current is:
>> ...
>> ISO=3D"ipfire-$IPFVER.$arch-full-core$COREVER.iso"
>> ...
>>=20
>> IMHO it could be sufficient to change this to:
>> ...
>> ISO=3D"ipfire-$IPFVER-core$CORVER-$arch.iso"
>> ...
>>=20
>> I haven't searched for other occurences yet, but I think that could be
>> the culprit...
>>=20
>> jm2c
>>=20
>> Matthias
>>=20
>> On 16.09.2022 16:24, Adolf Belka wrote:
>>> Hi All,
>>>=20
>>> On 16/09/2022 16:02, Adolf Belka wrote:
>>>> Hi everyone,
>>>>=20
>>>> On the forum there have been a couple of people who tried creating an is=
o backup and it only showed a 0 byte file.
>>>>=20
>>>>=20
>>>> I have confirmed with my vm testbed. The same thing works fine for CU169.
>>>>=20
>>>>=20
>>>> After looking through code I have found that Core Update 169  and 170 fi=
le name order is different. The arch is placed in a different location
>>>>=20
>>>>=20
>>>> https://downloads.ipfire.org/releases/ipfire-2.x/2.27-core169/ipfire-2.2=
7.x86_64-full-core169.iso
>>>>=20
>>>> https://downloads.ipfire.org/releases/ipfire-2.x/2.27-core170/ipfire-2.2=
7-core170-x86_64.iso
>>>>=20
>>>> This means that backup.pl is not able to find the Core Update 170 iso fr=
om the downloads site.
>>>>=20
>>> If the change in iso file naming convention was intended then backup.pl a=
lso needs to be modified for the iso naming convention.
>>>=20
>>>=20
>>> Regards,
>>>=20
>>> Adolf.
>>>=20
>>>>=20
>>>> Regards,
>>>>=20
>>>> Adolf.
>>>>=20
>>>>=20
>>=20
>=20


--===============2265724181925200777==--