public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] iana-etc: Update to version 20220207
Date: Tue, 15 Feb 2022 12:31:43 +0000	[thread overview]
Message-ID: <C5167EBF-4850-425B-8BC8-94D2BBE87A3B@ipfire.org> (raw)
In-Reply-To: <4fd67404-5c9f-7d3c-154f-9ce3f9cd0b08@ipfire.org>

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

Oh no! LOL

Acked-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 15 Feb 2022, at 12:30, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I forgot to include the url for the git repository in the commit message.
> 
> https://github.com/Mic92/iana-etc
> 
> Regards,
> Adolf.
> 
> On 15/02/2022 10:36, Adolf Belka wrote:
>> - Update from 2.30 (2011) to 20220207
>> - Update of rootfile not required
>> - After version 2.30 the files from iana are no longer versioned. A git repository is
>>    available (also used by LFS) which creates the required files by an automated script.
>>    So the lfs just needs to copy across the services and protocols files to /etc
>> - There is no Changelog
>> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
>> ---
>>  lfs/iana-etc | 11 +++++------
>>  1 file changed, 5 insertions(+), 6 deletions(-)
>> diff --git a/lfs/iana-etc b/lfs/iana-etc
>> index 8b7156f12..ddcdc9242 100644
>> --- a/lfs/iana-etc
>> +++ b/lfs/iana-etc
>> @@ -24,10 +24,10 @@
>>    include Config
>>  -VER        = 2.30
>> +VER        = 20220207
>>    THISAPP    = iana-etc-$(VER)
>> -DL_FILE    = $(THISAPP).tar.bz2
>> +DL_FILE    = $(THISAPP).tar.gz
>>  DL_FROM    = $(URL_IPFIRE)
>>  DIR_APP    = $(DIR_SRC)/$(THISAPP)
>>  TARGET     = $(DIR_INFO)/$(THISAPP)
>> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>>    $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>>  -$(DL_FILE)_MD5 = 3ba3afb1d1b261383d247f46cb135ee8
>> +$(DL_FILE)_MD5 = 81d865ce7fe4240d5abed48c3ca5fa9f
>>    install : $(TARGET)
>>  @@ -69,8 +69,7 @@ $(subst %,%_MD5,$(objects)) :
>>    $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
>>  	@$(PREBUILD)
>> -	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar jxf $(DIR_DL)/$(DL_FILE)
>> -	cd $(DIR_APP) && make $(MAKETUNING) $(EXTRA_MAKE)
>> -	cd $(DIR_APP) && make install
>> +	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
>> +	cp -avf $(DIR_APP)/{services,protocols} /etc/
>>  	@rm -rf $(DIR_APP)
>>  	@$(POSTBUILD)


      reply	other threads:[~2022-02-15 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  9:36 Adolf Belka
2022-02-15 12:30 ` Adolf Belka
2022-02-15 12:31   ` Michael Tremer [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=C5167EBF-4850-425B-8BC8-94D2BBE87A3B@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