[Bug 2054925] Re: Debootstrap fails for Noble with base-files 13ubuntu7

[Mauricio Faria de Oliveira]

I confirmed that the resulting target dir of debootstrap in Jammy (with
patch/MERGED_USR=no) and Mantic is the same, with a comparison of `ls
-lR` (normalized for Month/Day/Time fields).

...

Test command for Jammy (patched) and Mantic:

# debootstrap --arch=amd64 --variant=minbase --keyring
/usr/share/keyrings/ubuntu-archive-keyring.gpg noble /tmp/nobletest
http://archive.ubuntu.com/ubuntu

Dir listing for Jammy (patched) and Mantic:

deboostrap-jammy # ls -lR /tmp/nobletest/ > list.jammy
deboostrap-mantic # ls -lR /tmp/nobletest/ > list.mantic

Normalization and comparison:

$ sed -i 's/[A-Z][a-z][a-z] .[0-9] [0-9][0-9]:[0-9][0-9]/DATETIME/'
list.jammy list.mantic

$ diff -U0 list.jammy list.mantic
--- list.jammy	2024-02-26 19:39:49.102864808 -0300
+++ list.mantic	2024-02-26 19:39:49.114864569 -0300
@@ -76 +76 @@
--rw-r--r-- 1 root root      18 DATETIME hostname
+-rw-r--r-- 1 root root      19 DATETIME hostname
@@ -7093 +7093 @@
--rw-r--r-- 1 root root 60238 DATETIME bootstrap.log
+-rw-r--r-- 1 root root 60045 DATETIME bootstrap.log

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

Title:
  Debootstrap fails for Noble with base-files 13ubuntu7

Status in base-files package in Ubuntu:
  Won't Fix
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debootstrap source package in Focal:
  In Progress
Status in debootstrap source package in Jammy:
  In Progress
Status in base-files source package in Mantic:
  New
Status in debootstrap source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  The last couple of days, I have been unable to run a successful debootstrap for Noble Numbat.

  Apparently this is caused by the addition of symlinks (/bin, /lib,
  /lib64 and /sbin) in base-files 13ubuntu7. According to
  debootstrap.log, it fails to extract said symlinks because they
  already exist at that point.

  This can be reproduced on build hosts running Jammy Jellyfish against
  any up-to-date Ubuntu public archive mirror as of today.

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:	Ubuntu
  Description:	Ubuntu 22.04.4 LTS
  Release:	22.04
  Codename:	jammy

  # apt-cache policy debootstrap
  debootstrap:
    Installed: 1.0.126+nmu1ubuntu0.5
    Candidate: 1.0.126+nmu1ubuntu0.5
    Version table:
   *** 1.0.126+nmu1ubuntu0.5 500
          500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
          500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
          100 /var/lib/dpkg/status
       1.0.126+nmu1 500
          500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
          500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages

  Attached shell output of two runs of debootstrap. First run uses
  mirror archive.ubuntu.com (which as of this report serves base-files
  version 13ubuntu7), and second run uses a local custom mirror (which
  serves base-files 13ubuntu6). First run fails, second run succeeds.

  [Test plan]
  Successfully for each of focal, jammy, mantic, noble
  - debootstrap
  - mksbuild
  - pbuilder whatever chroot management tool it has
  - ubuntu-image, if we can pull debootstrap from proposed for this

  as well as

  - debootstrap noble --merged-usr

  
  [Where problems could occur]
  We do not anticipate any regressions as we replace the previous *) case for usrmerge for post-hirsute with a new jammy|kinetic|lunar|mantic one, and the new solution will only impact noble and onward.

  That said, this is a different approach than mantic and newer take,
  and a different approach than Debian takes, where they moved to
  merging post-extraction, even in stable releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+subscriptions