[Bug 2009871] Re: snapcraft images contain backports repo by default

[Justin Cattle]

Just in case anyone is questioning why it matters.  It really boils down
to two primary things IMO:

1 - Backports is not used by default in most situations, as the packages
there don't have the same support or release process guarantees as far
as I understand it [ https://help.ubuntu.com/community/UbuntuBackports ]

2 - If something manages the apt sources after system bootstrap using
the image, and they don't included backports, they can find dependency
issues that apt can't resolve automatically [ as the resolution may
require a package downgrade ].


The second issue is one I actually hit [ mentioned in the main body above ].

Hope that helps give some context.


Cheers,
Just

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2009871

Title:
  snapcraft images contain backports repo by default

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  New

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://bugs.launchpad.net/snapcraft/+bug/1982420

  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/preferences.d/backports would not be included in the
  image setup process at all by default, so backport packages are never
  included by default.  Or, if it's there to help fix an issue, perhaps
  the apt pinning config with lower priority and take care the required
  package installation specifically.

  
  ## Test ##

  multipass launch -n test-20 -d 10g snapcraft:core20

  root at test-20:~# dpkg -l |grep devmapper
  ii  libdevmapper1.02.1:amd64       2:1.02.175-2ubuntu4~ubuntu20.04.1 amd64        Linux Kernel Device Mapper userspace library

  root at test-20:~# apt-get update

  root at test-20:~# cat /etc/apt/preferences.d/backports 
  Package: *
  Pin: release a=*-backports
  Pin-Priority: 500

  root at test-20:~# apt-cache policy libdevmapper1.02.1
  libdevmapper1.02.1:
    Installed: 2:1.02.175-2ubuntu4~ubuntu20.04.1
    Candidate: 2:1.02.175-2ubuntu4~ubuntu20.04.1
    Version table:
   *** 2:1.02.175-2ubuntu4~ubuntu20.04.1 500
          500 http://archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages
          100 /var/lib/dpkg/status
       2:1.02.167-1ubuntu1 500
          500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages


  
  Cheers,
  Just

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2009871/+subscriptions