pijul_org / pijul

#293 pijul-0.10.0.tar.gz appears to be compressed twice

Opened by DataWraith2, on July 19, 2018
DataWraith2 commented on July 19, 2018

Since cargo install seems to be broken currently, I wanted to download the source from the website. After downloading the file, tar xavf refused to unpack it. I had to decompress it first using gzip and then change the name back to .tar.gz for tar to unpack the now singly-compressed file.

This is a fairly minor annoyance, but it does not make a good impression, so you might want to fix it.

Cheers, DataWraith

onio commented on July 20, 2018

This is a fairly minor annoyance, but it does not make a good impression, so you might want to fix it.

Releasing a breaking change as a minor change (sanakirja v0.8.16 => v0.8.17) (that's the reason why the cargo install build fail) and then not reacting for a month doesn't make a good impression either.

cdisselkoen commented on July 24, 2018

Yeah, it does give the impression that the maintainers don't care about this project anymore. Which is a shame.

I just heard about this project recently - is this the typical state of things, or is this an unusual anomaly? Is there a large community involvement in contributing to pijul?

vegai commented on July 27, 2018

It's a summer holiday season, perhaps they're just relaxing. Breaking the build like that was a really bad thing to do, though.

pmeunier commented on July 28, 2018

There aren't many maintainers in this project. We do care a lot about it, but don't have time to fix all the issues as fast as we'd like. But you can definitely help by sending us patches!

onio commented on July 28, 2018

@pmeunier there is a patch by @lthms that would make libpijul compile with the latest version of sanakirja.

jmelfi commented on August 5, 2018

Is there a way to get that patch referenced above to be merged in? 0.10.1 does not build either due to this issue within libpijul.

pmeunier commented on October 21, 2018

tar xavf works on my machine. I have tar 1.30 and gzip 1.9. Feel free to reopen if this is still a issue, providing more details about which version cause this to fail.

DataWraith2 commented on October 21, 2018

Hm. I also have tar 1.30 and gzip 1.9.

I think it might be a problem with how the file is served by the webserver -- as Content-Type: text/plain without a Content-Encoding header.

Using wget results in a useable archive, but "Save as" with Firefox (62.0) results in the doubly-compressed archive that tar xavf pijul-0.10.0.tar.gz complains about ("this does not look like a tar archive"). Using the file command on the download results in pijul-0.10.0.tar.gz: gzip compressed data, from Unix, original size 183007. Decompressing that with gunzip yields gzip compressed data, max compression, original size 1017344 and is then decompressible by tar.

I think the problem is that the server sends the file transport-compressed without advertising that as such, and Firefox dutifully downloads the doubly-compressed file as is, while wget is smart enough to strip the first layer of compression.