Merge ~alexsander-souza/maas:2_9-fix-snap_build into maas:2.9
Proposed by
Alexsander de Souza
Status: | Merged |
---|---|
Approved by: | Alexsander de Souza |
Approved revision: | 8e59dbfe804d0f854a79cc1524446541de52c926 |
Merge reported by: | MAAS Lander |
Merged at revision: | not available |
Proposed branch: | ~alexsander-souza/maas:2_9-fix-snap_build |
Merge into: | maas:2.9 |
Diff against target: |
13 lines (+0/-2) 1 file modified
snap/snapcraft.yaml (+0/-2) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alexsander de Souza | Approve | ||
MAAS Lander | Approve | ||
Review via email: mp+432215@code.launchpad.net |
Commit message
Don't specify PYTHONPATH when building the snap.
Having a PYTHONPATH there breaks the build if a systemwide pip is
installed.
I tried building it without having build-environment defined. The snap
built ok, and the installed snap started up without any problems.
(cherry picked from commit f25a4b5fe52a2cc
To post a comment you must log in.
UNIT TESTS
-b 2_9-fix-snap_build lp:~alexsander-souza/maas/+git/maas into -b 2.9 lp:~maas-committers/maas
STATUS: FAILED maas-ci. internal: 8080/job/ maas-tester/ 1185/consoleTex t 54a79cc15244465 41de52c926
LOG: http://
COMMIT: 8e59dbfe804d0f8