Skip to contentSkip to conversation

package/tar: bump target version to 1.32 (host is kept at 1.29)

PATCH Superseded unixmania at gmail.com 2 participants 5 messages Nov 19, 2019 – Jan 18, 2020

v3 of 5 Superseded Latest is v5 →

lore
Share & tools
lore
#0 lore raw

PATCH v3 1/1 package/tar: bump target version to 1.32 (host is kept at 1.29)

From: Luc Creti <[email protected]>

The host tar is used to create the archives in the VCS download backends (git, cvs, svn, hg...) and tar 1.30 and forward have changed the way they generate the archives.

So, all the archives that have been generated before 1.30 was released are not bit-for-bit reproducible (even though the extracted content would be), so the hashes we have for those archives would not match.

Hence host-tar must be kept at version 1.29.

For the target variant, this is less important, so bump it to the latest version.

---
Changes v0->v1:
- Commit message rewritten based on comment from Yann E. MORIN
Changes v1->v2:
- Title modified to enphasize that host-tar is kept at 1.29
Changes v2->v3
- Add a comment in the .mk file that explains why the host-tar package is kept at 1.29 and not bumped to any higher version
- Add missing spaces around '='
- Spell Author name as 'Luc Creti'

---
 package/tar/tar.hash |  2 +-
 package/tar/tar.mk   | 13 +++++++++----
 2 files changed, 10 insertions(+), 5 deletions(-)
package/tar/tar.hash +1 -1
index 60309bab8f..90beb26094 100644
@@ -1,4 +1,4 @@
 # Locally calculated after checking signature
-sha256	402dcfd0022fd7a1f2c5611f5c61af1cd84910a760a44a688e18ddbff4e9f024	tar-1.29.tar.xz
+sha256	d0d3ae07f103323be809bc3eac0dcc386d52c5262499fe05511ac4788af1fdd8	tar-1.32.tar.xz
 sha256	9173f222464dd3676118408840da5990527062b5c7daf6487bed7c396c45bfb1	tar-1.29.cpio.gz
 sha256	8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903	COPYING
package/tar/tar.mk +9 -4
index 6f609d7a02..e79e26f8c4 100644
@@ -4,7 +4,12 @@
 #
 ################################################################################
 
-TAR_VERSION = 1.29
+# host-tar is used to create the archives in the VCS download backends and tar
+# 1.30 and forward have changed the archive format. So archives generated with
+# earlier versions are not bit-for-bit reproducible and the hashes would not
+# match. Hence host-tar must be kept at version 1.29.
+HOST_TAR_VERSION = 1.29
+TAR_VERSION = 1.32
 TAR_SOURCE = tar-$(TAR_VERSION).tar.xz
 TAR_SITE = $(BR2_GNU_MIRROR)/tar
 # busybox installs in /bin, so we need tar to install as well in /bin
@@ -31,13 +36,13 @@ $(eval $(autotools-package))
 
 # host-tar: use cpio.gz instead of tar.gz to prevent chicken-egg problem
 # of needing tar to build tar.
-HOST_TAR_SOURCE = tar-$(TAR_VERSION).cpio.gz
+HOST_TAR_SOURCE = tar-$(HOST_TAR_VERSION).cpio.gz
 define HOST_TAR_EXTRACT_CMDS
 	mkdir -p $(@D)
 	cd $(@D) && \
 		$(call suitable-extractor,$(HOST_TAR_SOURCE)) $(TAR_DL_DIR)/$(HOST_TAR_SOURCE) | cpio -i --preserve-modification-time
-	mv $(@D)/tar-$(TAR_VERSION)/* $(@D)
-	rmdir $(@D)/tar-$(TAR_VERSION)
+	mv $(@D)/tar-$(HOST_TAR_VERSION)/* $(@D)
+	rmdir $(@D)/tar-$(HOST_TAR_VERSION)
 endef
 
 HOST_TAR_CONF_OPTS = --without-selinux
Signature · 1 line
2.18.1
#1 lore raw

PATCH v3 1/1 package/tar: bump target version to 1.32 (host is kept at 1.29)

Luc, Carlos, All,

On 2019-11-19 09:18 -0300, unixmania at gmail.com spake thusly:

Quoted 12 lines

From: Luc Creti <[email protected]>

The host tar is used to create the archives in the VCS download backends (git, cvs, svn, hg...) and tar 1.30 and forward have changed the way they generate the archives.

So, all the archives that have been generated before 1.30 was released are not bit-for-bit reproducible (even though the extracted content would be), so the hashes we have for those archives would not match.

Hence host-tar must be kept at version 1.29.

Quoted 7 lines

For the target variant, this is less important, so bump it to the latest version.

Thanks for the reiterated attempts at bumping tar. I've now applied this version of the patch, which has the great advantage of not patching tar.

Applied to master, with all the host-related commentsd and variables moved down to gether. Thanks.

Regards,
Yann E. MORIN.

Quoted 67 lines

---
Changes v0->v1:
- Commit message rewritten based on comment from Yann E. MORIN
Changes v1->v2:
- Title modified to enphasize that host-tar is kept at 1.29
Changes v2->v3
- Add a comment in the .mk file that explains why the host-tar package is kept at 1.29 and not bumped to any higher version
- Add missing spaces around '='
- Spell Author name as 'Luc Creti'

---
 package/tar/tar.hash |  2 +-
 package/tar/tar.mk   | 13 +++++++++----
 2 files changed, 10 insertions(+), 5 deletions(-)
package/tar/tar.hash +1 -1
index 60309bab8f..90beb26094 100644
@@ -1,4 +1,4 @@
 # Locally calculated after checking signature
-sha256	402dcfd0022fd7a1f2c5611f5c61af1cd84910a760a44a688e18ddbff4e9f024	tar-1.29.tar.xz
+sha256	d0d3ae07f103323be809bc3eac0dcc386d52c5262499fe05511ac4788af1fdd8	tar-1.32.tar.xz
 sha256	9173f222464dd3676118408840da5990527062b5c7daf6487bed7c396c45bfb1	tar-1.29.cpio.gz
 sha256	8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903	COPYING
package/tar/tar.mk +9 -4
index 6f609d7a02..e79e26f8c4 100644
@@ -4,7 +4,12 @@
 #
 ################################################################################
 
-TAR_VERSION = 1.29
+# host-tar is used to create the archives in the VCS download backends and tar
+# 1.30 and forward have changed the archive format. So archives generated with
+# earlier versions are not bit-for-bit reproducible and the hashes would not
+# match. Hence host-tar must be kept at version 1.29.
+HOST_TAR_VERSION = 1.29
+TAR_VERSION = 1.32
 TAR_SOURCE = tar-$(TAR_VERSION).tar.xz
 TAR_SITE = $(BR2_GNU_MIRROR)/tar
 # busybox installs in /bin, so we need tar to install as well in /bin
@@ -31,13 +36,13 @@ $(eval $(autotools-package))
 
 # host-tar: use cpio.gz instead of tar.gz to prevent chicken-egg problem
 # of needing tar to build tar.
-HOST_TAR_SOURCE = tar-$(TAR_VERSION).cpio.gz
+HOST_TAR_SOURCE = tar-$(HOST_TAR_VERSION).cpio.gz
 define HOST_TAR_EXTRACT_CMDS
 	mkdir -p $(@D)
 	cd $(@D) && \
 		$(call suitable-extractor,$(HOST_TAR_SOURCE)) $(TAR_DL_DIR)/$(HOST_TAR_SOURCE) | cpio -i --preserve-modification-time
-	mv $(@D)/tar-$(TAR_VERSION)/* $(@D)
-	rmdir $(@D)/tar-$(TAR_VERSION)
+	mv $(@D)/tar-$(HOST_TAR_VERSION)/* $(@D)
+	rmdir $(@D)/tar-$(HOST_TAR_VERSION)
 endef
 
 HOST_TAR_CONF_OPTS = --without-selinux
Signature · 6 lines
2.18.1

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
#2 lore raw

PATCH v3 1/1 package/tar: bump target version to 1.32 (host is kept at 1.29)

Quoted 21 lines · Yann E. MORIN

Luc, Carlos, All,

On 2019-11-19 09:18 -0300, unixmania at gmail.com spake thusly:

Quoted 17 lines

From: Luc Creti <[email protected]>

The host tar is used to create the archives in the VCS download backends (git, cvs, svn, hg...) and tar 1.30 and forward have changed the way they generate the archives.

So, all the archives that have been generated before 1.30 was released are not bit-for-bit reproducible (even though the extracted content would be), so the hashes we have for those archives would not match.

Hence host-tar must be kept at version 1.29.

For the target variant, this is less important, so bump it to the latest version.

Quoted 8 lines
Quoted 2 lines

Thanks for the reiterated attempts at bumping tar. I've now applied this version of the patch, which has the great advantage of not patching tar.

Applied to master, with all the host-related commentsd and variables moved down to gether. Thanks.

Can't we at least get rid of the cpio thing, as done in v5?

Signature · 1 line
Carlos Santos <[email protected]>
#3 lore raw

PATCH v3 1/1 package/tar: bump target version to 1.32 (host is kept at 1.29)

Carlos, All,

On 2020-01-18 11:12 -0300, Carlos Santos spake thusly:

Quoted 3 lines · Yann E. MORIN
Quoted 2 lines

On 2019-11-19 09:18 -0300, unixmania at gmail.com spake thusly:

Quoted 1 line

From: Luc Creti <[email protected]>

[--SNIP--]

Quoted 1 line
Quoted 1 line
Quoted 1 line

Hence host-tar must be kept at version 1.29.

[--SNIP--]

Quoted 3 lines
Quoted 2 lines

Applied to master, with all the host-related commentsd and variables moved down to gether. Thanks.

Can't we at least get rid of the cpio thing, as done in v5?

Why? We can't ensure that the host has tar, and if it does, we can't be sure we can rely on it to extract the tarball.

cpio is present virtually everywhere, and its format has been stable for the longest time.

Regards,
Yann E. MORIN.

Signature · 6 lines
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
#4 lore raw

PATCH v3 1/1 package/tar: bump target version to 1.32 (host is kept at 1.29)

Quoted 14 lines · Yann E. MORIN

Carlos, All,

On 2020-01-18 11:12 -0300, Carlos Santos spake thusly:

Quoted 3 lines · Yann E. MORIN
Quoted 2 lines

On 2019-11-19 09:18 -0300, unixmania at gmail.com spake thusly:

Quoted 1 line

From: Luc Creti <[email protected]>

[--SNIP--]

Quoted 1 line
Quoted 1 line
Quoted 1 line

Hence host-tar must be kept at version 1.29.

[--SNIP--]

Quoted 3 lines
Quoted 2 lines

Applied to master, with all the host-related commentsd and variables moved down to gether. Thanks.

Can't we at least get rid of the cpio thing, as done in v5?

Quoted 8 lines

Why? We can't ensure that the host has tar, and if it does, we can't be sure we can rely on it to extract the tarball.

cpio is present virtually everywhere, and its format has been stable for the longest time.

Regards,
Yann E. MORIN.

CPIO(1L) CPIO(1L)

NAME
cpio - copy files to and from archives

__WARNING__
The cpio utility is considered LEGACY based on POSIX specifica? tion. Users are encouraged to use other archiving tools for archive creation.

Signature · 1 line
Carlos Santos <[email protected]>