Snapcraft

node-engine: 8.1.3 is not happy

Bug #1703643 reported by Evan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Confirmed
Undecided
Unassigned

Bug Description

Possibly related to or a duplicate of #1702661.

Setting `node-engine: 8.1.3` and then running `snapcraft cleanbuild` explodes, but `node-engine: 7.10.0` works fine:

https://gist.github.com/evandandrea/be30a0b769a3739c81dc95da6bce5e9b

I suggested it might be a duplicate of #1702661 because outside cleanbuild, the error is the same as #1702661:

https://gist.github.com/evandandrea/24fb22f894c8102a9c5a87c7c1eccf29

See original description
Tags: plugin
Evan (ev)
description: updated
Evan (ev)
description: updated
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

Mind verifying this is not a duplicate?

Changed in snapcraft:
status: New → Incomplete
Revision history for this message
Leo Arias (elopio) wrote :

This is not a duplicate because the other one was released with 2.33, and this one still fails with 2.34.

Changed in snapcraft:
status: Incomplete → Confirmed
tags: added: plugin
Revision history for this message
Leo Arias (elopio) wrote :

Debugging on the container, there is not /root/build_heroku/parts/hello-node-snap/install/lib/node_modules/.staging/@heroku/, so chown /root/build_heroku/parts/hello-node-snap/install/lib/node_modules/.staging/@heroku/linewrap-6d8b1b65 of course fails.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.