From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Incorrect naming convention used on the Core Update 170 download file. Date: Fri, 16 Sep 2022 16:24:34 +0200 Message-ID: In-Reply-To: <831fb363-c048-3649-85c3-321c8f2f2828@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6410916255203568224==" List-Id: --===============6410916255203568224== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 iso b= ackup 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=C2=A0 and 170 = file 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.27.x= 86_64-full-core169.iso > > https://downloads.ipfire.org/releases/ipfire-2.x/2.27-core170/ipfire-2.27-c= ore170-x86_64.iso > > This means that backup.pl is not able to find the Core Update 170 iso from = the downloads site. > If the change in iso file naming convention was intended then backup.pl also = needs to be modified for the iso naming convention. Regards, Adolf. > > Regards, > > Adolf. > > --===============6410916255203568224==--