Yesterday I tried to use debootstrap to create an Ubuntu 24.04 (Noble Numbat) chroot from an Ubuntu 20.04 (Focal Fossa) host which failed with the following error, which is discussed in but not literally quoted in this bug report:
I: Chosen extractor for .deb packages: dpkg-deb I: Extracting base-files... E: Tried to extract package, but file already exists. Exit... I arrived here via askubuntu.com where the literal error message is quoted: https://askubuntu.com/questions/1518091/creating-a-debian-sid-chroot-on- ubuntu-22-04 Based on this bug report I realized that the bug fix was uploaded to the `focal-proposed` repository, where it is still available as of today, but it was never accepted / promoted into `focal-updates` or whichever is the appropriate repository to receive such bug fixes. Anyway, I'm posting here to report that enabling the `focal-proposed` repository and installing the updated `debootstrap` package available there fixed my issue: peter@test-vm:~$ sudo grep proposed /etc/apt/sources.list deb http://nl.archive.ubuntu.com/ubuntu focal-proposed main universe multiverse peter@test-vm:~$ apt-cache policy debootstrap debootstrap: Installed: 1.0.118ubuntu1.11 Candidate: 1.0.118ubuntu1.13 Version table: 1.0.118ubuntu1.13 500 500 http://nl.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages *** 1.0.118ubuntu1.11 500 500 http://nl.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.118ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages After installing the 1.0.118ubuntu1.13 version of debootstrap I reran my debootstrap invocation and this time it completed successfully: debootstrap --arch=amd64 --keyring=/usr/share/keyrings/ubuntu-archive- keyring.gpg noble /tmp/test-chroot http://nl.archive.ubuntu.com/ubuntu I take it that manually invoking debootstrap to construct Ubuntu chroots is not a very popular activity (I use it to create build chroots for a custom built Debian binary package build server), otherwise complaints would have come in here earlier, but it would nevertheless be nice if the updated debootstrap package can still be approved / accepted? (if that is still possible) Thanks to everyone who was involved in fixing this issue and creating and maintaining debootstrap and related tools to begin with! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files 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: Fix Committed Status in debootstrap source package in Jammy: Fix Released Status in base-files source package in Mantic: Won't Fix 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 - mk-sbuild - pbuilder-dist $release create - 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
