From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adolf Belka <adolf.belka@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 12:36:50 +0200
Message-ID: <7078c86a-71cb-183f-7188-dd0a623f0a68@ipfire.org>
In-Reply-To: <3F393EB4-1500-4548-B0B1-DF478538D125@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8267702634163889970=="
List-Id: <development.lists.ipfire.org>

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

Hi Michael,

On 18/09/2022 11:23, Michael Tremer wrote:
> Hello,
>=20
> This fucking feature will kill me some time. Or I will kill it.
>=20
> Matthias, are you going to submit this change as a patch?
I am doing a patch for this.

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

--===============8267702634163889970==--