On
root@known-seal:~# apt policy debootstrap debootstrap: Installed: 1.0.126+nmu1ubuntu0.7 Candidate: 1.0.126+nmu1ubuntu0.7 Version table: *** 1.0.126+nmu1ubuntu0.7 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.0.126+nmu1ubuntu0.5 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 - debootstrap {focal,jammy,mantic,noble} - mk-sbuild {focal,jammy,mantic,noble} - pbuilder-dist {focal,jammy,mantic,noble} create
and with the ubuntu-image run from upils I think we can call that verified.
On
root@known-seal:~# apt policy debootstrap nmu1ubuntu0. 7 nmu1ubuntu0. 7 nmu1ubuntu0. 7 500 archive. ubuntu. com/ubuntu jammy-proposed/main amd64 Packages security. ubuntu. com/ubuntu jammy-proposed/main amd64 Packages dpkg/status 0.126+nmu1ubunt u0.5 500 archive. ubuntu. com/ubuntu jammy-updates/main amd64 Packages archive. ubuntu. com/ubuntu jammy/main amd64 Packages
debootstrap:
Installed: 1.0.126+
Candidate: 1.0.126+
Version table:
*** 1.0.126+
500 http://
500 http://
100 /var/lib/
1.
500 http://
1.0.126+nmu1 500
500 http://
I ran jammy,mantic, noble} jammy,mantic, noble} jammy,mantic, noble} create
- debootstrap {focal,
- mk-sbuild {focal,
- pbuilder-dist {focal,
and with the ubuntu-image run from upils I think we can call that verified.