Make ubuntu-image a classic snap
Bug #1638645 reported by
Barry Warsaw
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Image |
Fix Released
|
High
|
Barry Warsaw |
Bug Description
Building the snap with confinement: devmode is a pain because it makes the ubuntu-image snap much less discoverable (by design of snapd). Why do we need devmode anyway? We ship our own mkfs.ext4 so we shouldn't need sudo in the snap.
Let's try to get rid of it.
Changed in ubuntu-image: | |
assignee: | nobody → Barry Warsaw (barry) |
Changed in ubuntu-image: | |
status: | New → In Progress |
Changed in ubuntu-image: | |
status: | In Progress → Confirmed |
Changed in ubuntu-image: | |
milestone: | none → 1.0 |
Changed in ubuntu-image: | |
status: | Confirmed → In Progress |
importance: | Medium → High |
Changed in ubuntu-image: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-image: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
when setting up the snap build on launchpad you can use the ubuntu-image PPA as default archive and put the e2fslibs (that cause this requirement) into stage-packages, that way devmode should be avoidable since the snap will ship its own version of e2fslibs so no sudo will be needed.