Skip to contentSkip to conversation

pigz: use archive tarball instead of Github generated tarball

PATCH In review Tim Orling 2 participants 2 messages Oct 27, 2017 – Oct 30, 2017

lore
Share & tools
lore

Tim Orling

author
#0 lore raw

PATCH 1/1 pigz: use archive tarball instead of Github generated tarball

Github-generated tarballs are known to change over time, so use an archive tarball provided by zlib.net instead.

---
 meta/recipes-extended/pigz/pigz_2.3.4.bb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
meta/recipes-extended/pigz/pigz_2.3.4.bb +3 -3
index f4832dffe1..3dc4de3710 100644
@@ -3,9 +3,9 @@ LIC_FILES_CHKSUM = "file://pigz.c;beginline=7;endline=21;md5=a21d4075cb00ab4ca17
 
 UPSTREAM_CHECK_URI = "http://zlib.net/${BPN}/"
 UPSTREAM_CHECK_REGEX = "pigz-(?P<pver>.*)\.tar"
-SRC_URI = "https://github.com/madler/pigz/archive/v${PV}.tar.gz;downloadfilename=${BP}.tar.gz"
-SRC_URI[md5sum] = "c109057050b15edf3eb9bb4d0805235e"
-SRC_URI[sha256sum] = "763f2fdb203aa0b7b640e63385e38e5dd4e5aaa041bc8e42aa96f2ef156b06e8"
+SRC_URI = "https://zlib.net/pigz/${BP}.tar.gz"
+SRC_URI[md5sum] = "08e6b2e682bbf65ccf12c8966d633fc6"
+SRC_URI[sha256sum] = "6f031fa40bc15b1d80d502ff91f83ba14f4b079e886bfb83221374f7bf5c8f9a"
 
 BBCLASSEXTEND = "native nativesdk"
 
Signature · 1 line
2.13.5
#1 lore raw
Quoted 3 lines · Tim Orling

Github-generated tarballs are known to change over time, so use an archive tarball provided by zlib.net instead.

Looks like a good idea but the maintainer removes the old releases:

$ wget https://zlib.net/pigz/pigz-2.3.4.tar.gz
--2017-10-30 16:28:55--  https://zlib.net/pigz/pigz-2.3.4.tar.gz
Resolving zlib.net (zlib.net)... 69.73.182.198
Connecting to zlib.net (zlib.net)|69.73.182.198|:443... connected.
HTTP request sent, awaiting response... 200 OK
...
2017-10-30 16:28:56 (302 KB/s) - ‘pigz-2.3.4.tar.gz’ saved [105412/105412]

ross@flashheart ~/Programming/libsoup (master %)

$ wget https://zlib.net/pigz/pigz-2.3.3.tar.gz
--2017-10-30 16:28:58--  https://zlib.net/pigz/pigz-2.3.3.tar.gz
Resolving zlib.net (zlib.net)... 69.73.182.198
Connecting to zlib.net (zlib.net)|69.73.182.198|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-10-30 16:28:59 ERROR 404: Not Found.

The moment a new tarball comes out we'll need to fix all previous oe-core releases... maybe the author has a secret directory of all releases, or could be talked into not deleting future releases?

Ross