ubuntu-core 18 amd64+kassel images FTBFS
Bug #1958218 reported by
Łukasz Zemczak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| livecd-rootfs (Ubuntu) |
Invalid
|
High
|
Łukasz Zemczak | ||
| Bionic |
In Progress
|
High
|
Łukasz Zemczak | ||
Bug Description
[Impact]
Currently amd64+kassel ubuntu-core images FTBFS. The reason for that is that the bluez extra-snap that we install for it switched its base to core20 from core18. This requires explicitly pulling in the new base to get the builds working again.
[Test Case]
Make sure the ubuntu-core 18 amd64+kassel image builds correctly on the cdimage infrastructure.
[Regression Potential]
None. The code change only touches the case of extra snaps for kassel and kassel is the only case that can regress. Having 3 base snaps can have consequences of the images being big for no reason, but kassel currently is a dead platform.
[Discussion]
This all begs a question: does it make sense to still build kassel images..?
Related branches
livecd-rootfs:fix-kassel
- Brian Murray: Disapprove
-
Diff: 29 lines (+9/-1)2 files modifieddebian/changelog (+8/-0)
live-build/auto/config (+1/-1)
| Changed in livecd-rootfs (Ubuntu Bionic): | |
| assignee: | nobody → Łukasz Zemczak (sil2100) |
| importance: | Undecided → High |
| status: | New → In Progress |
| Changed in livecd-rootfs (Ubuntu): | |
| status: | In Progress → Invalid |
To post a comment you must log in.
