From: Scott Garman <sgarman@zenlinux.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] tar: upgrade to version 1.25
Date: Thu, 18 Nov 2010 08:35:20 -0800 [thread overview]
Message-ID: <4CE555C8.5000503@zenlinux.com> (raw)
In-Reply-To: <AANLkTikWQH5fqT3VuOyrPjmevfOGtP2bHxU1Kat2cjTX@mail.gmail.com>
On 11/18/2010 12:34 AM, Martin Jansa wrote:
>>>>> Can you add tar-1.23 to the removal.txt file? Ask it be removed in a
>>>>> couple of months. This way we have a schedule to delete the older recipe.
>>>>
>>>> Thanks for the quick ack, Philip. Question though on the removal.txt
>>>> addition - this patch deletes the v1.23 version already. Does it need to
>>>> be kept around instead? I would think not given that this is a pretty
>>>> trivial update.
>>>>
>>>> Perhaps you meant tar v1.18 and/or v1.20, which are still there?
>>>
>>> Oops, I wasn't paying that close attention. I'd still leave 1.23 around for
>>> a couple of months, just in case there is some weird issue with 1.25. We
>>> should check on the older ones and add them to removal.txt also. I'd like to
>>> see us get into a sane clean up old stuff cycle, instead of the delete
>>> everything at once approach. Of course checking to see if any in tree
>>> distros use them is good thing.
>>>
>>
>> Yeah probably a sane thing. Make 1.25 default and let 1.23 linger
>> around for a while
>> just in case.
>
> Gentoo already has serious bug reported against 1.25
> http://bugs.gentoo.org/342983
> resulting in added 1.25 being masked now there
>
> Maybe we should keep 1.23 default until it's resolved or confirmed
> that OE is not affected by this.
Thanks Martin for that research. I'm going to remove my patch from
patchwork and look into this further. If the bug against 1.25 doesn't
look like it will affect us, I will re-submit the patch such that 1.23
is kept around. Otherwise we may be better off simply waiting for
another release of tar.
FWIW tar 1.25 came out only two weeks after 1.24, which implies to me
that they were fixing some relatively urgent bugs. As mentioned on the
tar home page, these issues were reportedly fixed in 1.25:
* Fix extraction of empty directories with the -C option in effect
* Fix extraction of device nodes
* Make sure name matching occurs before eventual name transformation
* Fix the behavior of tar -x --overwrite on hosts lacking O_NOFOLLOW.
* Improve the testsuite
I also maintain the tar recipe for Poky, so I'll investigate further.
Scott
--
Scott Garman
sgarman at zenlinux dot com
prev parent reply other threads:[~2010-11-18 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 2:13 [PATCH] tar: upgrade to version 1.25 Scott Garman
2010-11-18 2:18 ` Philip Balister
2010-11-18 2:48 ` Scott Garman
2010-11-18 2:54 ` Philip Balister
2010-11-18 3:28 ` Khem Raj
2010-11-18 8:34 ` Martin Jansa
2010-11-18 16:35 ` Scott Garman [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=4CE555C8.5000503@zenlinux.com \
--to=sgarman@zenlinux.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.