gzip: stdin: not in gzip format

[gabrielmancini]

Hi Guys,

I am trying upping the version of nodejs in heroku
so following the steps to hack the buildpack, i made the necessary changes, but when i push the project the deploy show me this error:

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Exiting with failure status due to previous errors

 !     Push rejected, failed to compile Node.js app

any one pass thru for this?

[gabrielmancini]

Ohh, that error occur when you make some dumb ass on your buildpack, and the process can't download the nodejs from your bucket.

[lancetipton]

I know this is closed, but can you expand on this? I am having the same problem and can't figure it out.

[hunterloftis]

@lancetipton04 could you provide your full output? Are you using the master branch of the heroku buildpack or a fork?

[volkanunsal]

Having the same problem today. Any update on this?

[volkanunsal]

If anyone is having the same problem, I ended up using version 63 and that worked well.

heroku config:set "BUILDPACK_URL=https://github.com/heroku/heroku-buildpack-nodejs#v63"

[hunterloftis]

@volkanunsal can you open a ticket (help.heroku.com) or paste your full output? It's difficult to figure out what's up without any context.

[hunterloftis]

I just did a quick search of our logs; the only instances of this error I see are people trying to install really old versions of Node (that we don't support anymore - like 0.6.11). I'll add some code to detect this either in semver or in the buildpack, but if you're specifying < 0.8.5 in package.json and you've found this thread - update your node engine! :)

[volkanunsal]

Nope, I'm using 0.11.33.

On Tue, Jan 13, 2015 at 2:20 PM, Hunter Loftis [email protected]
wrote:

I just did a quick search of our logs; the only instances of this error I
see are people trying to install really old versions of Node (that we don't
support anymore - like 0.6.11). I'll add some code to detect this either in
semver or in the buildpack, but if you're specifying < 0.8.5 in
package.json and you've found this thread - update your node engine! :)

—
Reply to this email directly or view it on GitHub
#44 (comment)
.

Volkan Unsal
web and mobile development
volkanunsal.com http://bit.ly/1h1ebjy

[hunterloftis]

@volkanunsal That would be why then - 0.11.33 doesn't exist:

http://nodejs.org/dist/

[volkanunsal]

You're right. Huh. I guess it was always resolving to 0.10.35 before.

[hunterloftis]

Yeah #v63 always uses semver to resolve, while the later branches skip resolution if you specify an exact version (since we don't want to change versions on someone who is specifying exactly what they want).

[alexandre-mbm]

I found that I needed specify an old version for the node.

First I tried:

"engines" : { "node" : "0.6.21" }

After:

"engines" : { "node" : "0.8.5" }

This worked:

"engines" : { "node" : "~0.8.5" }

There are nodejs.org/dist/v0.8.5 and nodejs.org/dist/v0.6.21 but the first was OK for me.

[PanMan]

I had this error twice today, but just pushing again works.

[hunterloftis]

@PanManAms likely means the node binary was unavailable initially and then became available.

I'll separate the download from the parsing so in between the two I can check whether or not the download succeeded.

[saru2020]

After so many years and still, this issue occurs.
Btw: My fix was to pin to a specific version as mentioned here:
heroku buildpacks:set https://github.com/heroku/heroku-buildpack-nodejs#v75 -a my-app