From: Michael Tremer <michael.tremer@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 11:23:57 +0200 [thread overview]
Message-ID: <3F393EB4-1500-4548-B0B1-DF478538D125@ipfire.org> (raw)
In-Reply-To: <511781b6-6fcd-501c-3829-b0b7915d4833@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
Hello,
This fucking feature will kill me some time. Or I will kill it.
Matthias, are you going to submit this change as a patch?
-Michael
> 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="ipfire-$IPFVER.$arch-full-core$COREVER.iso"
> ...
>
> IMHO it could be sufficient to change this to:
> ...
> ISO="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 iso 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 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.x86_64-full-core169.iso
>>>
>>> https://downloads.ipfire.org/releases/ipfire-2.x/2.27-core170/ipfire-2.27-core170-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.
>>>
>>>
>
next prev parent reply other threads:[~2022-09-18 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 14:02 Adolf Belka
2022-09-16 14:24 ` Adolf Belka
2022-09-17 9:28 ` Matthias Fischer
2022-09-17 10:22 ` Adolf Belka
2022-09-17 11:00 ` Matthias Fischer
2022-09-17 11:29 ` Adolf Belka
2022-09-17 13:12 ` Matthias Fischer
2022-09-17 15:06 ` Adolf Belka
2022-09-17 15:16 ` Matthias Fischer
2022-09-18 9:23 ` Michael Tremer [this message]
2022-09-18 10:36 ` Adolf Belka
2022-09-18 12:55 ` Matthias Fischer
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=3F393EB4-1500-4548-B0B1-DF478538D125@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