Hello Åka, or anyone else affected,

Accepted debootstrap into jammy-proposed. The package will build now and
be available at
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: debootstrap (Ubuntu Jammy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.

  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:
  Fix Committed
Status in base-files source package in Mantic:
Status in debootstrap source package in Mantic:
  Fix Released

Bug description:
  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
    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:

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

Reply via email to