Merge ~nacc/git-ubuntu:lp1741949-unset-snap-in-lxc-env into git-ubuntu:master
Proposed by
Nish Aravamudan
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Robie Basak | ||||
Approved revision: | 467d0f591f7fcd79b7fb7a99ca6be12585ffc3ef | ||||
Merged at revision: | 699b0185f4ed61eceb754e95568de12417ad3ad5 | ||||
Proposed branch: | ~nacc/git-ubuntu:lp1741949-unset-snap-in-lxc-env | ||||
Merge into: | git-ubuntu:master | ||||
Diff against target: |
217 lines (+75/-46) 2 files modified
gitubuntu/build.py (+36/-46) gitubuntu/run.py (+39/-0) |
||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robie Basak | Approve | ||
Andreas Hasenack | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
Nish Aravamudan | Pending | ||
Review via email: mp+336391@code.launchpad.net |
This proposal supersedes a proposal from 2018-01-18.
Commit message
Make Jenkins happy.
Description of the change
Make Jenkins happy.
To post a comment you must log in.
Why are we unsetting SNAP for some calls to lxc, but not all of them? Is there some criteria we have to use to decide this? Or are you just working around the calls that happen to break for now?
As long as we have to work around some other project's bug, I'd like to have a bug reference in a comment in our code which shows us why the workaround is present and what its status is for us to get rid of it. So when I asked for a bug against this, I meant I wanted an open bug task against the project which we are working around (whether that is snapd or lxd I'm not sure).