tar: upgrade to version 1.25
PATCH 1/1 tar: upgrade to version 1.25
--- 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
recipes/tar/tar_1.23.bb deleted +0 -6
@@ -1,6 +0,0 @@ -require tar.inc - -PR = "${INC_PR}" - -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e" -SRC_URI[sha256sum] = "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
recipes/tar/tar_1.25.bb new file +6 -0
@@ -0,0 +1,6 @@ +require tar.inc + +PR = "${INC_PR}" + +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b" +SRC_URI[sha256sum] = "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"
Signature · 1 line
1.7.1
Quoted 26 lines · Scott Garman
Signed-off-by Scott Garman<[email protected]>--- 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.bbrecipes/tar/tar_1.23.bb deleted +0
-6@@ -1,6 +0,0 @@ -require tar.inc - -PR = "${INC_PR}" - -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e" -SRC_URI[sha256sum] = "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"recipes/tar/tar_1.25.bb new file +0
-0
recipes/tar/tar_1.25.bb line 6
Quoted 6 lines
recipes/tar/tar_1.25.bb new file +6
-0@@ -0,0 +1,6 @@ +require tar.inc + +PR = "${INC_PR}" + +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b" +SRC_URI[sha256sum] = "f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"
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
Quoted 39 lines · Philip Balister
Quoted 33 lines · Scott Garman
Signed-off-by Scott Garman<[email protected]>---
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.bbrecipes/tar/tar_1.23.bb deleted +0
-6@@ -1,6 +0,0 @@ -require tar.inc - -PR = "${INC_PR}" - -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e" -SRC_URI[sha256sum] ="
c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"recipes/tar/tar_1.25.bb new file +6
-0@@ -0,0 +1,6 @@ +require tar.inc + +PR = "${INC_PR}" + +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b" +SRC_URI[sha256sum] =Quoted 1 line
"
f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"Acked-by Philip Balister <[email protected]>
Quoted 2 lines
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
Quoted 43 lines · Scott Garman
Quoted 39 lines · Philip Balister
Quoted 33 lines · Scott Garman
Signed-off-by Scott Garman<[email protected]>---
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.bbrecipes/tar/tar_1.23.bb deleted +0
-6@@ -1,6 +0,0 @@ -require tar.inc - -PR = "${INC_PR}" - -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e" -SRC_URI[sha256sum] ="
c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"recipes/tar/tar_1.25.bb new file +6
-0@@ -0,0 +1,6 @@ +require tar.inc + +PR = "${INC_PR}" + +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b" +SRC_URI[sha256sum] =Quoted 1 line
"
f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"Acked-by Philip Balister <[email protected]>Quoted 2 lines
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.
Quoted 6 lines
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
Quoted 8 lines
Scott
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 52 lines · Philip Balister
Quoted 51 lines · Scott Garman
Quoted 41 lines · Philip Balister
Quoted 34 lines · Scott Garman
Signed-off-by Scott Garman<[email protected]>---
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.bbrecipes/tar/tar_1.23.bb deleted +0
-6@@ -1,6 +0,0 @@ -require tar.inc - -PR = "${INC_PR}" - -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e" -SRC_URI[sha256sum] ="
c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"recipes/tar/tar_1.25.bb new file +6
-0@@ -0,0 +1,6 @@ +require tar.inc + +PR = "${INC_PR}" + +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b" +SRC_URI[sha256sum] =Quoted 1 line
"
f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"Acked-by Philip Balister <[email protected]>Quoted 2 lines
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.
Quoted 9 lines
Quoted 1 line
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.
Quoted 16 lines
Philip
Quoted 8 lines
Scott
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Quoted 63 lines · Khem Raj
Quoted 52 lines · Philip Balister
Quoted 51 lines · Scott Garman
Quoted 41 lines · Philip Balister
Quoted 34 lines · Scott Garman
Signed-off-by Scott Garman<[email protected]>---
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.bbrecipes/tar/tar_1.23.bb deleted +0
-6@@ -1,6 +0,0 @@ -require tar.inc - -PR = "${INC_PR}" - -SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e" -SRC_URI[sha256sum] ="
c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"recipes/tar/tar_1.25.bb new file +6
-0@@ -0,0 +1,6 @@ +require tar.inc + +PR = "${INC_PR}" + +SRC_URI[md5sum] = "6e497f861c77bbba2f7da4e10270995b" +SRC_URI[sha256sum] =Quoted 1 line
"
f3f6ce41b8e0f327abd05c95990f113ddafbae131e10f79a99728ed46458494b"Acked-by Philip Balister <[email protected]>Quoted 2 lines
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.
Quoted 9 lines
Quoted 1 line
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.
Quoted 3 lines
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,
Quoted 22 lines · Martin Jansa
Quoted 18 lines
Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
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.
Quoted 9 lines
Quoted 1 line
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.
Quoted 3 lines
Yeah probably a sane thing. Make 1.25 default and let 1.23 linger around for a while
just in case.
Quoted 6 lines
Gentoo already has serious bug reported against 1.25
http://bugs.gentoo.org/342983
resulting in added 1.25 being masked now thereMaybe 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
Signature · 2 lines
Scott Garman sgarman at zenlinux dot com