[Bug 2097467] [NEW] live-build removes /e/a/preferences.d/proposed.pref, preventing >= Noble builds with -proposed

[Paride Legovini]

Public bug reported:

Starting from Noble, the -proposed pocket is configured as NotAutomatic:
yes.

When building Ubuntu daily ISO images, we often want to include packages
from -proposed for testing purposes. For this reason, livecd-rootfs adds
and APT preference file (or "pin") to neutralize NotAutomatic, see live-
build/auto/config, relevant excerpt:

        cat > config/chroot_apt/proposed.pref <<EOF
# override for NotAutomatic: yes
Package: *
Pin: release a=*-proposed
Pin-Priority: 500
EOF

However, this preference file appears to get removed during the image
build by live-build. From a Launchpad livefs build log (full log at
[2]):

P: Backing up packaged preferences.d/* files ...
'chroot/etc/apt/preferences.d' -> 'chroot/etc/apt/preferences.d.save'
'chroot/etc/apt/preferences.d/ubuntu-pro-esm-apps' -> 'chroot/etc/apt/preferences.d.save/ubuntu-pro-esm-apps'
'chroot/etc/apt/preferences.d/ubuntu-pro-esm-infra' -> 'chroot/etc/apt/preferences.d.save/ubuntu-pro-esm-infra'
'chroot/etc/apt/preferences.d/proposed.pref' -> 'chroot/etc/apt/preferences.d.save/proposed.pref'

It is my understanding that live-build tries to _not_ propagate apt
preferences to the chroot to work with a clean environment. However, not
having proposed.pref precludes -proposed from being used. This can
prevent proper SRU verification of bugs that require an ISO build to be
properly verified, e.g. [3].

In the specific case of [3], have for rmadison plasma-desktop:

 plasma-desktop | 4:5.27.11-0ubuntu2    | noble/universe
 plasma-desktop | 4:5.27.12-0ubuntu0.1  | noble-proposed/universe

We would like 4:5.27.12-0ubuntu0.1 to be used, but [2] shows that
4:5.27.11-0ubuntu2 is used instead. In my understanding, this is because
proposed.pref gets moved away, while it should not be.

[1] See https://archive.ubuntu.com/ubuntu/dists/noble-proposed/Release and apt_preferences(5) for what that entails
[2] https://launchpadlibrarian.net/774654462/buildlog_ubuntu_noble_amd64_kubuntu_BUILDING.txt.gz
[3] https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/2093184

** Affects: live-build (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Starting from Noble, the -proposed pocket is configured as NotAutomatic:
  yes.
  
- When building Ubuntu daily ISO image, we often want to include packages
+ When building Ubuntu daily ISO images, we often want to include packages
  from -proposed for testing purposes. For this reason, livecd-rootfs adds
  and APT preference file (or "pin") to neutralize NotAutomatic, see live-
  build/auto/config, relevant excerpt:
  
- 
-         cat > config/chroot_apt/proposed.pref <<EOF
+         cat > config/chroot_apt/proposed.pref <<EOF
  # override for NotAutomatic: yes
  Package: *
  Pin: release a=*-proposed
  Pin-Priority: 500
  EOF
  
  However, this preference file appears to get removed during the image
  build by live-build. From a Launchpad livefs build log (full log at
  [2]):
  
  P: Backing up packaged preferences.d/* files ...
  'chroot/etc/apt/preferences.d' -> 'chroot/etc/apt/preferences.d.save'
  'chroot/etc/apt/preferences.d/ubuntu-pro-esm-apps' -> 'chroot/etc/apt/preferences.d.save/ubuntu-pro-esm-apps'
  'chroot/etc/apt/preferences.d/ubuntu-pro-esm-infra' -> 'chroot/etc/apt/preferences.d.save/ubuntu-pro-esm-infra'
  'chroot/etc/apt/preferences.d/proposed.pref' -> 'chroot/etc/apt/preferences.d.save/proposed.pref'
  
  It is my understanding that live-build tries to _not_ propagate apt
  preferences to the chroot to work with a clean environment. However, not
  having proposed.pref precludes -proposed from being used. This can
  prevent proper SRU verification of bugs that require an ISO build to be
  properly verified, e.g. [3].
  
  In the specific case of [3], have for rmadison plasma-desktop:
  
-  plasma-desktop | 4:5.27.11-0ubuntu2    | noble/universe
-  plasma-desktop | 4:5.27.12-0ubuntu0.1  | noble-proposed/universe
+  plasma-desktop | 4:5.27.11-0ubuntu2    | noble/universe
+  plasma-desktop | 4:5.27.12-0ubuntu0.1  | noble-proposed/universe
  
  We would like 4:5.27.12-0ubuntu0.1 to be used, but [2] shows that
  4:5.27.11-0ubuntu2 is used instead. In my understanding, this is because
  proposed.pref gets moved away, while it should not be.
  
  [1] See https://archive.ubuntu.com/ubuntu/dists/noble-proposed/Release and apt_preferences(5) for what that entails
  [2] https://launchpadlibrarian.net/774654462/buildlog_ubuntu_noble_amd64_kubuntu_BUILDING.txt.gz
  [3] https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/2093184

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

Title:
  live-build removes /e/a/preferences.d/proposed.pref, preventing >=
  Noble builds with -proposed

Status in live-build package in Ubuntu:
  New

Bug description:
  Starting from Noble, the -proposed pocket is configured as
  NotAutomatic: yes.

  When building Ubuntu daily ISO images, we often want to include
  packages from -proposed for testing purposes. For this reason, livecd-
  rootfs adds and APT preference file (or "pin") to neutralize
  NotAutomatic, see live-build/auto/config, relevant excerpt:

          cat > config/chroot_apt/proposed.pref <<EOF
  # override for NotAutomatic: yes
  Package: *
  Pin: release a=*-proposed
  Pin-Priority: 500
  EOF

  However, this preference file appears to get removed during the image
  build by live-build. From a Launchpad livefs build log (full log at
  [2]):

  P: Backing up packaged preferences.d/* files ...
  'chroot/etc/apt/preferences.d' -> 'chroot/etc/apt/preferences.d.save'
  'chroot/etc/apt/preferences.d/ubuntu-pro-esm-apps' -> 'chroot/etc/apt/preferences.d.save/ubuntu-pro-esm-apps'
  'chroot/etc/apt/preferences.d/ubuntu-pro-esm-infra' -> 'chroot/etc/apt/preferences.d.save/ubuntu-pro-esm-infra'
  'chroot/etc/apt/preferences.d/proposed.pref' -> 'chroot/etc/apt/preferences.d.save/proposed.pref'

  It is my understanding that live-build tries to _not_ propagate apt
  preferences to the chroot to work with a clean environment. However,
  not having proposed.pref precludes -proposed from being used. This can
  prevent proper SRU verification of bugs that require an ISO build to
  be properly verified, e.g. [3].

  In the specific case of [3], have for rmadison plasma-desktop:

   plasma-desktop | 4:5.27.11-0ubuntu2    | noble/universe
   plasma-desktop | 4:5.27.12-0ubuntu0.1  | noble-proposed/universe

  We would like 4:5.27.12-0ubuntu0.1 to be used, but [2] shows that
  4:5.27.11-0ubuntu2 is used instead. In my understanding, this is
  because proposed.pref gets moved away, while it should not be.

  [1] See https://archive.ubuntu.com/ubuntu/dists/noble-proposed/Release and apt_preferences(5) for what that entails
  [2] https://launchpadlibrarian.net/774654462/buildlog_ubuntu_noble_amd64_kubuntu_BUILDING.txt.gz
  [3] https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/2093184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/2097467/+subscriptions