Heroku build fails

[TravisTheTechie]

remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Fetching custom git buildpack... done
remote: -----> Lineman app detected
remote: Reusing previous heroku NPM build cache
remote: -----> Resolving engine versions
remote: 
remote:        WARNING: No version of Node.js specified in package.json, see:
remote:        https://devcenter.heroku.com/articles/nodejs-support#versions
remote: 
remote: /tmp/node-bootstrap_node-Z0E2/bin/node: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or director
remote:  !     Requested engine node version  does not match available versions: 0.10.21 [who cares] ... 0.4.7 
remote: 
remote:  !     Push rejected, failed to compile Lineman app

[TravisTheTechie]

Okay, looking at the logs, looks like #27 (comment) is the issue why the site isn't loading, regardless of what it says during git push.

[searls]

keep me posted on your progress debugging this, travis.

in the future (at least with @cabbagejs), i want to accomplish this with the official multipack + official php pack (for nginx) + a small little script we add on top.

managing this buildpack has been a nightmare

On Mon, Jan 19, 2015 at 12:45 PM, Travis Smith [email protected]
wrote:

remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Fetching custom git buildpack... done
remote: -----> Lineman app detected
remote: Reusing previous heroku NPM build cache
remote: -----> Resolving engine versions
remote: 
remote:        WARNING: No version of Node.js specified in package.json, see:
remote:        https://devcenter.heroku.com/articles/nodejs-support#versions
remote: 
remote: /tmp/node-bootstrap_node-Z0E2/bin/node: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or director
remote:  !     Requested engine node version  does not match available versions: 0.10.21 0.10.20 0.10.19 0.10.18 0.10.17 0.10.16 0.10.15 0.10.14 0.10.13 0.10.12 0.10.11 0.10.10 0.10.9 0.10.8 0.10.6 0.10.5 0.10.4 0.10.3 0.10.2 0.10.1 0.10.0 0.8.26 0.8.25 0.8.24 0.8.23 0.8.22 0.8.21 0.8.19 0.8.14 0.8.13 0.8.12 0.8.11 0.8.10 0.8.8 0.8.7 0.8.6 0.8.5 0.8.4 0.8.3 0.8.2 0.8.1 0.8.0 0.6.20 0.6.18 0.6.17 0.6.16 0.6.15 0.6.14 0.6.13 0.6.12 0.6.11 0.6.10 0.6.8 0.6.7 0.6.6 0.6.5 0.6.3 0.4.10 0.4.7 
remote: 
remote:  !     Push rejected, failed to compile Lineman app

---

Reply to this email directly or view it on GitHub:
#36

[TravisTheTechie]

Some googling suggests perhaps it's cedar-14 vs. cedar. However, Heroku is having some downtime currently, so I can't explore it any further.

[searls]

If anyone's interested in a fun weekend project, a clean break from this buildpack that goes the multi-pack route would be an AWESOME thing to behold

On Mon, Jan 19, 2015 at 1:28 PM, Travis Smith [email protected]
wrote:

Some googling suggests perhaps it's cedar-14 vs. cedar. However, Heroku is having some downtime currently, so I can't explore it any further.

Reply to this email directly or view it on GitHub:
#36 (comment)

[TravisTheTechie]

And yep, changing to cedar vs. cedar-14 fixed it.

[searls]

For the next person who gets stuck on this, could you share the command needed to specify a cedar app at a particular version?

On Mon, Jan 19, 2015 at 1:51 PM, Travis Smith [email protected]
wrote:

Closed #36.

Reply to this email directly or view it on GitHub:
#36 (comment)

[TravisTheTechie]

heroku stack:set cedar then git push heroku master to have a new release on that stack. It defaults to cedar-14 now. I'm not sure how long that's been the case, I don't expect much longer than a couple months. Otherwise I would have noticed before.

[searls]

Oh, good. I was worried you were saying folks would need to target old cedar to work. Sounds like a couple cedars were just funky. That would explain the last couple of months of hard-to-repro issues.

On Mon, Jan 19, 2015 at 1:58 PM, Travis Smith [email protected]
wrote:

heroku stack:set cedar then git push heroku master to have a new release on that stack. It defaults to cedar-14 now. I'm not sure how long that's been the case, I don't expect much longer than a couple months. Otherwise I would have noticed before.

Reply to this email directly or view it on GitHub:
#36 (comment)

[kvarga]

remote:  !   Cedar-10 will reach end-of-life on November 4th, 2015.

This will probably need to get solved in the next few months or so.