Public bug reported:
[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..?
** Affects: livecd-rootfs (Ubuntu)
Importance: High
Assignee: Łukasz Zemczak (sil2100)
Status: Invalid
** Affects: livecd-rootfs (Ubuntu Bionic)
Importance: High
Assignee: Łukasz Zemczak (sil2100)
Status: In Progress
** Also affects: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu Bionic)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
** Changed in: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: livecd-rootfs (Ubuntu Bionic)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu)
Status: In Progress => Invalid
** Merge proposal linked:
https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/414282
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958218
Title:
ubuntu-core 18 amd64+kassel images FTBFS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1958218/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
