[PATCH] tar: upgrade to version 1.25

[PATCH] tar: upgrade to version 1.25

[Scott Garman]

Signed-off-by: Scott Garman <sgarman@zenlinux.com>
---
 recipes/tar/tar_1.23.bb |    6 ------
 recipes/tar/tar_1.25.bb |    6 ++++++
 2 files changed, 6 insertions(+), 6 deletions(-)
 delete mode 100644 recipes/tar/tar_1.23.bb
 create mode 100644 recipes/tar/tar_1.25.bb

diff --git a/recipes/tar/tar_1.23.bb b/recipes/tar/tar_1.23.bb
deleted file mode 100644
index dc37247..0000000
--- a/recipes/tar/tar_1.23.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-require tar.inc
-
-PR = "${INC_PR}"
-
-SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
-SRC_URI[sha256sum] = "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
diff --git a/recipes/tar/tar_1.25.bb b/recipes/tar/tar_1.25.bb
new file mode 100644
index 0000000..c611f77
--- /dev/null
+++ b/recipes/tar/tar_1.25.bb
@@ -0,0 +1,6 @@
+require tar.inc
+
+PR = "${INC_PR}"
+
+SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b"
+SRC_URI[sha256sum] = "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"
-- 
1.7.1

Re: [PATCH] tar: upgrade to version 1.25

[Philip Balister]

On 11/17/2010 06:13 PM, Scott Garman wrote:
> Signed-off-by: Scott Garman<sgarman@zenlinux.com>
> ---
>   recipes/tar/tar_1.23.bb |    6 ------
>   recipes/tar/tar_1.25.bb |    6 ++++++
>   2 files changed, 6 insertions(+), 6 deletions(-)
>   delete mode 100644 recipes/tar/tar_1.23.bb
>   create mode 100644 recipes/tar/tar_1.25.bb
>
> diff --git a/recipes/tar/tar_1.23.bb b/recipes/tar/tar_1.23.bb
> deleted file mode 100644
> index dc37247..0000000
> --- a/recipes/tar/tar_1.23.bb
> +++ /dev/null
> @@ -1,6 +0,0 @@
> -require tar.inc
> -
> -PR = "${INC_PR}"
> -
> -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
> -SRC_URI[sha256sum] = "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
> diff --git a/recipes/tar/tar_1.25.bb b/recipes/tar/tar_1.25.bb
> new file mode 100644
> index 0000000..c611f77
> --- /dev/null
> +++ b/recipes/tar/tar_1.25.bb
> @@ -0,0 +1,6 @@
> +require tar.inc
> +
> +PR = "${INC_PR}"
> +
> +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b"
> +SRC_URI[sha256sum] = "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"


Acked-by: Philip Balister <philip@balister.org>

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.

Philip

Re: [PATCH] tar: upgrade to version 1.25

[Scott Garman]

On 11/17/2010 06:18 PM, Philip Balister wrote:
> On 11/17/2010 06:13 PM, Scott Garman wrote:
>> Signed-off-by: Scott Garman<sgarman@zenlinux.com>
>> ---
>> recipes/tar/tar_1.23.bb | 6 ------
>> recipes/tar/tar_1.25.bb | 6 ++++++
>> 2 files changed, 6 insertions(+), 6 deletions(-)
>> delete mode 100644 recipes/tar/tar_1.23.bb
>> create mode 100644 recipes/tar/tar_1.25.bb
>>
>> diff --git a/recipes/tar/tar_1.23.bb b/recipes/tar/tar_1.23.bb
>> deleted file mode 100644
>> index dc37247..0000000
>> --- a/recipes/tar/tar_1.23.bb
>> +++ /dev/null
>> @@ -1,6 +0,0 @@
>> -require tar.inc
>> -
>> -PR = "${INC_PR}"
>> -
>> -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
>> -SRC_URI[sha256sum] =
>> "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
>> diff --git a/recipes/tar/tar_1.25.bb b/recipes/tar/tar_1.25.bb
>> new file mode 100644
>> index 0000000..c611f77
>> --- /dev/null
>> +++ b/recipes/tar/tar_1.25.bb
>> @@ -0,0 +1,6 @@
>> +require tar.inc
>> +
>> +PR = "${INC_PR}"
>> +
>> +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b"
>> +SRC_URI[sha256sum] =
>> "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"
>
>
> Acked-by: Philip Balister <philip@balister.org>
>
> 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?

Scott

Re: [PATCH] tar: upgrade to version 1.25

[Philip Balister]

On 11/17/2010 06:48 PM, Scott Garman wrote:
> On 11/17/2010 06:18 PM, Philip Balister wrote:
>> On 11/17/2010 06:13 PM, Scott Garman wrote:
>>> Signed-off-by: Scott Garman<sgarman@zenlinux.com>
>>> ---
>>> recipes/tar/tar_1.23.bb | 6 ------
>>> recipes/tar/tar_1.25.bb | 6 ++++++
>>> 2 files changed, 6 insertions(+), 6 deletions(-)
>>> delete mode 100644 recipes/tar/tar_1.23.bb
>>> create mode 100644 recipes/tar/tar_1.25.bb
>>>
>>> diff --git a/recipes/tar/tar_1.23.bb b/recipes/tar/tar_1.23.bb
>>> deleted file mode 100644
>>> index dc37247..0000000
>>> --- a/recipes/tar/tar_1.23.bb
>>> +++ /dev/null
>>> @@ -1,6 +0,0 @@
>>> -require tar.inc
>>> -
>>> -PR = "${INC_PR}"
>>> -
>>> -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
>>> -SRC_URI[sha256sum] =
>>> "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
>>> diff --git a/recipes/tar/tar_1.25.bb b/recipes/tar/tar_1.25.bb
>>> new file mode 100644
>>> index 0000000..c611f77
>>> --- /dev/null
>>> +++ b/recipes/tar/tar_1.25.bb
>>> @@ -0,0 +1,6 @@
>>> +require tar.inc
>>> +
>>> +PR = "${INC_PR}"
>>> +
>>> +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b"
>>> +SRC_URI[sha256sum] =
>>> "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"
>>
>>
>> Acked-by: Philip Balister <philip@balister.org>
>>
>> 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.

Philip

>
> Scott
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: [PATCH] tar: upgrade to version 1.25

[Khem Raj]

On Wed, Nov 17, 2010 at 6:54 PM, Philip Balister <philip@balister.org> wrote:
> On 11/17/2010 06:48 PM, Scott Garman wrote:
>>
>> On 11/17/2010 06:18 PM, Philip Balister wrote:
>>>
>>> On 11/17/2010 06:13 PM, Scott Garman wrote:
>>>>
>>>> Signed-off-by: Scott Garman<sgarman@zenlinux.com>
>>>> ---
>>>> recipes/tar/tar_1.23.bb | 6 ------
>>>> recipes/tar/tar_1.25.bb | 6 ++++++
>>>> 2 files changed, 6 insertions(+), 6 deletions(-)
>>>> delete mode 100644 recipes/tar/tar_1.23.bb
>>>> create mode 100644 recipes/tar/tar_1.25.bb
>>>>
>>>> diff --git a/recipes/tar/tar_1.23.bb b/recipes/tar/tar_1.23.bb
>>>> deleted file mode 100644
>>>> index dc37247..0000000
>>>> --- a/recipes/tar/tar_1.23.bb
>>>> +++ /dev/null
>>>> @@ -1,6 +0,0 @@
>>>> -require tar.inc
>>>> -
>>>> -PR = "${INC_PR}"
>>>> -
>>>> -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
>>>> -SRC_URI[sha256sum] =
>>>> "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
>>>> diff --git a/recipes/tar/tar_1.25.bb b/recipes/tar/tar_1.25.bb
>>>> new file mode 100644
>>>> index 0000000..c611f77
>>>> --- /dev/null
>>>> +++ b/recipes/tar/tar_1.25.bb
>>>> @@ -0,0 +1,6 @@
>>>> +require tar.inc
>>>> +
>>>> +PR = "${INC_PR}"
>>>> +
>>>> +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b"
>>>> +SRC_URI[sha256sum] =
>>>> "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"
>>>
>>>
>>> Acked-by: Philip Balister <philip@balister.org>
>>>
>>> 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.

> Philip
>
>>
>> Scott
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: [PATCH] tar: upgrade to version 1.25

[Martin Jansa]

On Thu, Nov 18, 2010 at 4:28 AM, Khem Raj <raj.khem@gmail.com> wrote:
> On Wed, Nov 17, 2010 at 6:54 PM, Philip Balister <philip@balister.org> wrote:
>> On 11/17/2010 06:48 PM, Scott Garman wrote:
>>>
>>> On 11/17/2010 06:18 PM, Philip Balister wrote:
>>>>
>>>> On 11/17/2010 06:13 PM, Scott Garman wrote:
>>>>>
>>>>> Signed-off-by: Scott Garman<sgarman@zenlinux.com>
>>>>> ---
>>>>> recipes/tar/tar_1.23.bb | 6 ------
>>>>> recipes/tar/tar_1.25.bb | 6 ++++++
>>>>> 2 files changed, 6 insertions(+), 6 deletions(-)
>>>>> delete mode 100644 recipes/tar/tar_1.23.bb
>>>>> create mode 100644 recipes/tar/tar_1.25.bb
>>>>>
>>>>> diff --git a/recipes/tar/tar_1.23.bb b/recipes/tar/tar_1.23.bb
>>>>> deleted file mode 100644
>>>>> index dc37247..0000000
>>>>> --- a/recipes/tar/tar_1.23.bb
>>>>> +++ /dev/null
>>>>> @@ -1,6 +0,0 @@
>>>>> -require tar.inc
>>>>> -
>>>>> -PR = "${INC_PR}"
>>>>> -
>>>>> -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
>>>>> -SRC_URI[sha256sum] =
>>>>> "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
>>>>> diff --git a/recipes/tar/tar_1.25.bb b/recipes/tar/tar_1.25.bb
>>>>> new file mode 100644
>>>>> index 0000000..c611f77
>>>>> --- /dev/null
>>>>> +++ b/recipes/tar/tar_1.25.bb
>>>>> @@ -0,0 +1,6 @@
>>>>> +require tar.inc
>>>>> +
>>>>> +PR = "${INC_PR}"
>>>>> +
>>>>> +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b"
>>>>> +SRC_URI[sha256sum] =
>>>>> "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"
>>>>
>>>>
>>>> Acked-by: Philip Balister <philip@balister.org>
>>>>
>>>> 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.

Regards,

Re: [PATCH] tar: upgrade to version 1.25

[Scott Garman]

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