public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] core187: correct the shipping of ipblocklist sources
Date: Tue, 16 Jul 2024 13:51:55 +0200	[thread overview]
Message-ID: <5e33337b-a0df-462a-b83d-ffae89ce5b2f@ipfire.org> (raw)
In-Reply-To: <c57fdce4-4ef3-4c2b-b3e6-3a2356265cf6@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]

Hi All,

Please ignore this patch submission. I have closed the bug as an errata.

I managed to evaluate CU187 Testing on my vm systems without remembering to actually run the update to Testing. So I have been evaluating CU187 Testing on two CU186 systems for the last few days since the release was made.

Duuuuh.

Doing the actual update to CU187 Testing, I found that the ipblocklist sources file had been updated with the new sources.

Sorry for the noise.

I will also clear out the patch submission in patchwork.

Really sorry,

Adolf.


On 15/07/2024 15:00, Adolf Belka wrote:
> Fixes: Bug13726
>
> On 15/07/2024 14:29, Adolf Belka wrote:
>> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
>> ---
>>   config/rootfiles/core/187/filelists/files               | 1 +
>>   config/rootfiles/core/187/filelists/ipblocklist-sources | 1 -
>>   2 files changed, 1 insertion(+), 1 deletion(-)
>>   delete mode 120000 config/rootfiles/core/187/filelists/ipblocklist-sources
>>
>> diff --git a/config/rootfiles/core/187/filelists/files b/config/rootfiles/core/187/filelists/files
>> index d234de053..dda00abc1 100644
>> --- a/config/rootfiles/core/187/filelists/files
>> +++ b/config/rootfiles/core/187/filelists/files
>> @@ -6,3 +6,4 @@ srv/web/ipfire/cgi-bin/firewall.cgi
>>   srv/web/ipfire/cgi-bin/vpnmain.cgi
>>   usr/lib/firewall/rules.pl
>>   var/ipfire/header.pl
>> +var/ipfire/ipblocklist/sources
>> diff --git a/config/rootfiles/core/187/filelists/ipblocklist-sources b/config/rootfiles/core/187/filelists/ipblocklist-sources
>> deleted file mode 120000
>> index 31e200d14..000000000
>> --- a/config/rootfiles/core/187/filelists/ipblocklist-sources
>> +++ /dev/null
>> @@ -1 +0,0 @@
>> -../../../common/ipblocklist-sources
>> \ No newline at end of file
>

      reply	other threads:[~2024-07-16 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 12:29 Adolf Belka
2024-07-15 13:00 ` Adolf Belka
2024-07-16 11:51   ` Adolf Belka [this message]

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=5e33337b-a0df-462a-b83d-ffae89ce5b2f@ipfire.org \
    --to=adolf.belka@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