public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] tar: Update to 1.30
Date: Mon, 28 May 2018 19:40:18 +0200	[thread overview]
Message-ID: <ce0e1b93-3fb4-24ac-0132-72c8e1c34d70@ipfire.org> (raw)
In-Reply-To: <b725ff06081fe20d924ab20f8d46c1fed191f6c0.camel@ipfire.org>

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

Hi,

On 28.05.2018 12:32, Michael Tremer wrote:
> Arne did that already.

Thanks and sorry for the noise.

I don't know why, but at first it looked as if 'tar 1.30'
would work - somehow between my test builds I must have
overlooked something.

Same applies for the forgotten 'xz'-rootfile: thanks to Arne. ;-)

Regarding 'tar 1.30':
Marcus sent me his modifications from
https://git.ipfire.org/?p=people/mlorenz/ipfire-2.x.git;a=commitdiff;h=44e836b9f941113a61ba4fe1d85452541a2fcde7

I'd like to get this thing running, so right I'm about to
rework that 'tar'-patch, first test build is looking good.

Best,
Matthias

> Best,
> -Michael
> 
> On Sun, 2018-05-27 at 20:35 +0200, Matthias Fischer wrote:
>> Hi,
>> 
>> Please drop this patch - it must be reworked...
>> 
>> Best,
>> Matthias
>> 
>> On 26.05.2018 18:15, Matthias Fischer wrote:
>> > For details see:
>> > https://www.gnu.org/software/tar/
>> > 
>> > Best,
>> > Matthias
>> > 
>> > Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
>> > ---
>> >  lfs/tar | 6 +++---
>> >  1 file changed, 3 insertions(+), 3 deletions(-)
>> > 
>> > diff --git a/lfs/tar b/lfs/tar
>> > index 6a949a003..4e914b535 100644
>> > --- a/lfs/tar
>> > +++ b/lfs/tar
>> > @@ -1,7 +1,7 @@
>> >  ###########################################################################
>> > ####
>> >  #                                                                          
>> >    #
>> >  # IPFire.org - A linux based
>> > firewall                                         #
>> > -# Copyright (C) 2007  Michael Tremer & Christian
>> > Schmidt                      #
>> > +# Copyright (C) 2018  Michael Tremer & Christian
>> > Schmidt                      #
>> >  #                                                                          
>> >    #
>> >  # This program is free software: you can redistribute it and/or
>> > modify        #
>> >  # it under the terms of the GNU General Public License as published
>> > by        #
>> > @@ -24,7 +24,7 @@
>> >  
>> >  include Config
>> >  
>> > -VER        = 1.28
>> > +VER        = 1.30
>> >  
>> >  THISAPP    = tar-$(VER)
>> >  DL_FILE    = $(THISAPP).tar.bz2
>> > @@ -50,7 +50,7 @@ objects = $(DL_FILE)
>> >  
>> >  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>> >  
>> > -$(DL_FILE)_MD5 = 8f32b2bc1ed7ddf4cf4e4a39711341b0
>> > +$(DL_FILE)_MD5 = 8404e4c1fc5a3000228ab2b8ad674a65
>> >  
>> >  install : $(TARGET)
>> >  
>> > 
>> 
>> 
> 


      reply	other threads:[~2018-05-28 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26 16:15 Matthias Fischer
2018-05-27 18:35 ` Matthias Fischer
2018-05-28 10:32   ` Michael Tremer
2018-05-28 17:40     ` Matthias Fischer [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=ce0e1b93-3fb4-24ac-0132-72c8e1c34d70@ipfire.org \
    --to=matthias.fischer@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