Verification for jammy:
ubuntu@jammy-test:~$ apt policy debootstrap
debootstrap:
Installed: 1.0.126+nmu1ubuntu0.9
Candidate: 1.0.126+nmu1ubuntu0.9
Version table:
*** 1.0.126+nmu1ubuntu0.9 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
1.0.126+nmu1ubuntu0.8 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
1.0.126+nmu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
I ran:
- sudo env container=lxc debootstrap stonking ./stonking-chroot
http://archive.ubuntu.com/ubuntu/
- sudo chroot ./stonking-chroot/ cat /etc/os-release
- sudo env container=lxc debootstrap resolute ./resolute-chroot
http://archive.ubuntu.com/ubuntu/
- sudo chroot ./resolute-chroot/ cat /etc/os-release
- sudo env container=lxc debootstrap jammy ./jammy-chroot
http://archive.ubuntu.com/ubuntu/
- sudo chroot ./jammy-chroot cat /etc/os-release
All the commands performed as expected, the chroot creation worked
without any errors and smoke testing the chroot worked for both
stonking, resolute and jammy
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2160111
Title:
Debootstrap fails with stonking due to hardcoded sha256
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/2160111/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
