Hi,
I wanted to report that archives provided for new Whatpulse version 2.6.2 in http://whatpulse.org/downloads/ for linux (all 4 of them) are badly packaged (gzipped twice) which makes them not directly openable after clicking on them in the browser (using standard file-roller app).
After manual gunzip, archives are OK.
Hi,
The packages are tarred and then gzipped, but I don’t recognise the double gzip what you’re indicating. The test Ubuntu systems I use do recognise that format and open the archive right away after opening the downloaded file.
This can be certainly different for other distros, but I don’t plan to keep every distro into account. 
Hello,
Thank you for your answer, just saw it now. I got the same problem with version 2.6.3, but after some extra tests, I realized that I fall into this Firefozx bug : https://bugzilla.mozilla.org/show_bug.cgi?id=610679
It might be linked to some headers combination, and maybe the fact that the transfer is gzipped ?
However, it might be some server bad configuration, because I get the same behaviour with Chromium…
curl correctly transpose the content if used with --compressed option. I can’t say why Firefox and Chromium would fail is saving this file correctly…
Which browser do you use with your ubuntu distribution ?
So if there is a problem (I’m not expert enough in HTTP encoding to decided wheather the problem comes from my clients or not), it is not linked to the packaging, but to the server configuration.
As an aside comment, since the archive is already compressed, having the server use the gzip encoding in that case is kind of useless (and CPU consuming) anyway.
The default on Ubuntu…I think it’s Firefox. Maybe an older or newer version that doesn’t have that bug.
In any case, I still don’t see a problem, just a browser bug. 