snapcraft images contain backports repo by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
New
|
Undecided
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
It seems some snapcraft images contain the backports repo by default. Verified for current version of snapcraft:core20 at least.
This causes issues at snapcraft build time, as a new repo config is installed when snapcraft runs which doesn't include backports. [ probably by snapcraft itself ].
There is a bug about it here: https:/
I thought I would log an issue here too to discuss, as including backpacks by default seems like a slightly odd decision, and could even be a mistake.
Ideally, /etc/apt/
## Test ##
multipass launch -n test-20 -d 10g snapcraft:core20
root@test-20:~# dpkg -l |grep devmapper
ii libdevmapper1.
root@test-20:~# apt-get update
root@test-20:~# cat /etc/apt/
Package: *
Pin: release a=*-backports
Pin-Priority: 500
root@test-20:~# apt-cache policy libdevmapper1.02.1
libdevmapper1.02.1:
Installed: 2:1.02.
Candidate: 2:1.02.
Version table:
*** 2:1.02.
500 http://
100 /var/lib/
2:
500 http://
Cheers,
Just
FYI, in case it's not clear, the "snapcraft" images are the buildd images at https:/ /cloud- images. ubuntu. com/buildd/.