Add Ubuntu Kinetic as a known release
Bug #1970454 reported by
Graham Inggs
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debootstrap (Ubuntu) |
Fix Released
|
Undecided
|
Graham Inggs | ||
Trusty |
New
|
Undecided
|
Unassigned | ||
Xenial |
New
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Without this update users cannot generate kinetic chroots for development.
[Test Case]
Attempt to debootstrap kinetic.
[Where problems could occur]
Nowhere really, this simply introduces a suite specific script which is not used unless you attempt to create and Ubuntu Kinetic chroot.
Changed in debootstrap (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Graham Inggs (ginggs) |
Changed in debootstrap (Ubuntu Bionic): | |
status: | New → Fix Committed |
Changed in debootstrap (Ubuntu Focal): | |
status: | New → Fix Committed |
Changed in debootstrap (Ubuntu Impish): | |
status: | New → Fix Committed |
Changed in debootstrap (Ubuntu Jammy): | |
status: | New → Fix Committed |
Changed in debootstrap (Ubuntu): | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Hello Graham, or anyone else affected,
Accepted debootstrap into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ debootstrap/ 1.0.126+ nmu1ubuntu0. 1 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/ PerformingSRUVe rification . 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.