Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
The charm snap fails to build charm. #276
Comments
|
It looks like the new pip version is causing this problem. We should still consider a fix in the snap package so new python packages do not generate these errors. |
johnsca
added
charm-build
packaging
ux
labels
Nov 9, 2016
|
This is a critical bug, since the snap package is automatically updated. |
|
I'm simply unable to replicate this bug which blocks me from patching it |
|
Looking at the error, it appears I have/had an older version of pip installed and attempted to do a |
marcoceppi
removed
the
ux
label
Nov 14, 2016
|
I'm able to reproduce it. Here is the log with
The issue seems to be that 0637e546/tactics.py#L775 is still trying to upgrade the system pip instead of the venv's pip. |
|
Note: the log in the above is a bit misleading, in that the |
|
Would it help if I just re-rolled the snap with the latest version of pip while a fix is worked up so that it doesn't do a system wide pip upgrade? |
added a commit
that referenced
this issue
Nov 14, 2016
johnsca
referenced this issue
Nov 14, 2016
Merged
Actually activate the venv when building the wheelhouse #282
added a commit
that referenced
this issue
Nov 14, 2016
added a commit
that referenced
this issue
Nov 14, 2016
added a commit
that referenced
this issue
Nov 14, 2016
marcoceppi
closed this
in
#282
Nov 14, 2016
added a commit
that referenced
this issue
Nov 14, 2016
added a commit
that referenced
this issue
Nov 14, 2016
|
This is in revision 8 of the charm snap, in the stable channel |
mbruzek commentedNov 2, 2016
Checklist
What version am I running?
I am using: Ubuntu Xenial
Issue/Feature
I snap installed charm and tried to build the Kubernetes layers. I encountered an error during the build involving a read-only file system
I expect/expected the following
The snap should be able to build and handle dependencies without errors.
What I got