| 2023-05-23 15:05:12 |
Renan Rodrigo |
bug |
|
|
added bug |
| 2023-05-23 15:06:11 |
Renan Rodrigo |
description |
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-26 20:59:43 |
Steve Langasek |
summary |
Add Ubuntu Mantic as a known release |
The debootstrap SRU to end all debootstrap SRUs |
|
| 2023-05-26 21:04:10 |
Steve Langasek |
description |
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when running on Ubuntu, and if it is, to default to the common Ubuntu bootstrap script for release names that it does not recognize. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-26 21:04:15 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2023-05-26 21:36:29 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when running on Ubuntu, and if it is, to default to the common Ubuntu bootstrap script for release names that it does not recognize. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when running on Ubuntu, and if it is, to default to the common Ubuntu bootstrap script for release names that it does not recognize. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names.
[Test case]
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
sudo diff -uNr ${series}-old ${series}-new
done
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-26 21:42:53 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when running on Ubuntu, and if it is, to default to the common Ubuntu bootstrap script for release names that it does not recognize. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names.
[Test case]
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
sudo diff -uNr ${series}-old ${series}-new
done
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-26 21:43:01 |
Steve Langasek |
debootstrap (Ubuntu): status |
New |
Fix Released |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
bug task added |
|
debootstrap (Ubuntu Lunar) |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
bug task added |
|
debootstrap (Ubuntu Jammy) |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
nominated for series |
|
Ubuntu Focal |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
bug task added |
|
debootstrap (Ubuntu Focal) |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
nominated for series |
|
Ubuntu Kinetic |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
bug task added |
|
debootstrap (Ubuntu Kinetic) |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
nominated for series |
|
Ubuntu Bionic |
|
| 2023-05-26 21:43:07 |
Steve Langasek |
bug task added |
|
debootstrap (Ubuntu Bionic) |
|
| 2023-05-26 22:17:52 |
Steve Langasek |
debootstrap (Ubuntu Lunar): status |
New |
In Progress |
|
| 2023-05-26 22:17:54 |
Steve Langasek |
debootstrap (Ubuntu Kinetic): status |
New |
In Progress |
|
| 2023-05-26 22:25:39 |
Brian Murray |
debootstrap (Ubuntu Kinetic): status |
In Progress |
Fix Committed |
|
| 2023-05-26 22:25:40 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-05-26 22:25:42 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2023-05-26 22:25:46 |
Steve Langasek |
debootstrap (Ubuntu Jammy): status |
New |
In Progress |
|
| 2023-05-26 22:25:47 |
Brian Murray |
tags |
|
verification-needed verification-needed-kinetic |
|
| 2023-05-26 22:26:10 |
Steve Langasek |
debootstrap (Ubuntu Focal): status |
New |
In Progress |
|
| 2023-05-26 22:27:41 |
Steve Langasek |
debootstrap (Ubuntu Bionic): status |
New |
In Progress |
|
| 2023-05-26 22:27:46 |
Brian Murray |
debootstrap (Ubuntu Lunar): status |
In Progress |
Fix Committed |
|
| 2023-05-26 22:27:49 |
Brian Murray |
tags |
verification-needed verification-needed-kinetic |
verification-needed verification-needed-kinetic verification-needed-lunar |
|
| 2023-05-26 22:28:34 |
Brian Murray |
debootstrap (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-05-26 22:28:38 |
Brian Murray |
tags |
verification-needed verification-needed-kinetic verification-needed-lunar |
verification-needed verification-needed-jammy verification-needed-kinetic verification-needed-lunar |
|
| 2023-05-26 22:30:05 |
Brian Murray |
debootstrap (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2023-05-26 22:30:09 |
Brian Murray |
tags |
verification-needed verification-needed-jammy verification-needed-kinetic verification-needed-lunar |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic verification-needed-lunar |
|
| 2023-05-27 02:34:59 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic]; then continue; fi
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 02:35:18 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic]; then continue; fi
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 02:35:43 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 02:36:53 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${series}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${series}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${series}-old ${series}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 04:42:14 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a character special file|Binary files .*\.pyc differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 04:43:14 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a character special file|Binary files .*\.pyc differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*\.pyc differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 04:44:20 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*\.pyc differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*\.pyc differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 04:45:03 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*\.pyc differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-27 04:47:05 |
Steve Langasek |
tags |
verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic verification-needed-lunar |
verification-done-lunar verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
|
| 2023-05-27 05:37:58 |
Steve Langasek |
tags |
verification-done-lunar verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
verification-done-kinetic verification-done-lunar verification-needed verification-needed-focal verification-needed-jammy |
|
| 2023-05-27 16:46:14 |
Steve Langasek |
tags |
verification-done-kinetic verification-done-lunar verification-needed verification-needed-focal verification-needed-jammy |
verification-done-jammy verification-done-kinetic verification-done-lunar verification-needed verification-needed-focal |
|
| 2023-05-27 18:40:12 |
Steve Langasek |
tags |
verification-done-jammy verification-done-kinetic verification-done-lunar verification-needed verification-needed-focal |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar verification-needed |
|
| 2023-05-27 18:40:17 |
Steve Langasek |
tags |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar verification-needed |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar |
|
| 2023-05-27 19:34:07 |
Brian Murray |
debootstrap (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2023-05-27 19:34:11 |
Brian Murray |
tags |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar verification-needed verification-needed-bionic |
|
| 2023-05-28 01:35:22 |
Steve Langasek |
tags |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar verification-needed verification-needed-bionic |
verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar |
|
| 2023-05-30 14:27:32 |
Dimitri John Ledkov |
bug task added |
|
ubuntu-dev-tools (Ubuntu) |
|
| 2023-05-30 14:28:06 |
Dimitri John Ledkov |
ubuntu-dev-tools (Ubuntu Kinetic): status |
New |
Fix Released |
|
| 2023-05-30 14:28:13 |
Dimitri John Ledkov |
ubuntu-dev-tools (Ubuntu Lunar): status |
New |
Fix Released |
|
| 2023-05-30 14:28:21 |
Dimitri John Ledkov |
ubuntu-dev-tools (Ubuntu Jammy): status |
New |
Confirmed |
|
| 2023-05-30 14:28:28 |
Dimitri John Ledkov |
ubuntu-dev-tools (Ubuntu Focal): status |
New |
Confirmed |
|
| 2023-05-30 14:28:35 |
Dimitri John Ledkov |
ubuntu-dev-tools (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2023-05-30 14:28:42 |
Dimitri John Ledkov |
ubuntu-dev-tools (Ubuntu): status |
New |
Fix Released |
|
| 2023-05-30 14:32:14 |
Dimitri John Ledkov |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
NB! verification failed on jammy and lower see https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/2020530/comments/16
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-30 14:32:29 |
Dimitri John Ledkov |
tags |
verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-failed-focal verification-failed-jammy |
|
| 2023-05-30 16:32:56 |
Kamal Mostafa |
bug |
|
|
added subscriber Kamal Mostafa |
| 2023-05-31 04:40:21 |
Steve Langasek |
ubuntu-dev-tools (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2023-05-31 04:40:29 |
Steve Langasek |
ubuntu-dev-tools (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2023-05-31 04:40:43 |
Steve Langasek |
description |
NB! verification failed on jammy and lower see https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/2020530/comments/16
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-05-31 04:45:49 |
Steve Langasek |
ubuntu-dev-tools (Ubuntu Jammy): status |
Confirmed |
In Progress |
|
| 2023-06-01 08:14:28 |
Łukasz Zemczak |
debootstrap (Ubuntu Bionic): status |
Fix Committed |
Won't Fix |
|
| 2023-06-05 09:12:18 |
Launchpad Janitor |
debootstrap (Ubuntu Kinetic): status |
Fix Committed |
Fix Released |
|
| 2023-06-05 09:12:23 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-06-05 09:14:40 |
Launchpad Janitor |
debootstrap (Ubuntu Lunar): status |
Fix Committed |
Fix Released |
|
| 2023-06-07 04:36:46 |
Chris Halse Rogers |
ubuntu-dev-tools (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2023-06-07 04:36:50 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-06-07 04:36:59 |
Chris Halse Rogers |
tags |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-failed-focal verification-failed-jammy |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-failed-jammy verification-needed verification-needed-focal |
|
| 2023-06-07 04:39:43 |
Chris Halse Rogers |
ubuntu-dev-tools (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-06-07 04:39:51 |
Chris Halse Rogers |
tags |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-failed-jammy verification-needed verification-needed-focal |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy |
|
| 2023-06-07 05:25:15 |
Chris Halse Rogers |
ubuntu-dev-tools (Ubuntu Kinetic): status |
Fix Released |
Fix Committed |
|
| 2023-06-07 05:25:24 |
Chris Halse Rogers |
tags |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy |
verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
|
| 2023-06-07 05:46:39 |
Chris Halse Rogers |
ubuntu-dev-tools (Ubuntu Lunar): status |
Fix Released |
Fix Committed |
|
| 2023-06-07 05:46:46 |
Chris Halse Rogers |
tags |
verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic verification-needed-lunar |
|
| 2023-06-07 15:27:42 |
Steve Langasek |
description |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
[Impact]
Today, debootstrap requires a sourceful change to know about every target name. This means that every 6 months, we have to do an upload of debootstrap as part of the archive opening so that it can build chroots for the new release.
We have done this 30 times.
It causes development drag, because the upload of debootstrap to the devel series is not instantaneous, usually gets hung up on failing autopkgtests of reverse-dependencies related to other aspects of the archive opening, and is slow to get SRUed back to stable series.
And the only code change required in debootstrap is a symlink to the 'gutsy' script which has not changed in 15 years.
In mantic, I have changed the code to detect when the target series is one known to distro-info, and if it is, to default to the common Ubuntu bootstrap script. This removes the need for any further uploads of debootstrap to inform it of new Ubuntu release names (and lets us remove 30 symlinks from the source package).
[Test case]
sudo apt install distro-info debootstrap
series=$((distro-info --supported; distro-info --supported-esm)| sort -u)
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo debootstrap $s ${s}-old
done
install debootstrap from -proposed
for s in $series; do
sudo debootstrap $s ${s}-new
done
for s in $series; do
if [ "$s" = mantic ]; then continue; fi
sudo diff -uNr ${s}-old ${s}-new
done 2>&1 \
| grep -vE 'No such file or directory|is a (character|block) special file|Binary files .*(\.pyc|/var/cache/.*) differ' \
|filterdiff -x '*/etc/machine-id' -x '*/var/lib/dbus/machine-id' -x '*/var/log/**' -x '*/var/lib/dpkg/status*' -x '*/var/cache/**'
(exclude from the diff: dangling (wide) symlinks; device files; compiled pyc files that will differ on each generation; and other text files that are randomly generated or contain timestamp or ordering differences)
sudo apt install ubuntu-dev-tools
sg sbuild -c 'mk-sbuild --skip-proposed mantic'
[Where problems could occur]
Because this adds a new dependency, there could be problems as a result of pulling it in. However, distro-info is part of ubuntu-minimal, so is present on any supported Ubuntu system.
[Original description]
(on Jammy)
# sg sbuild -c mk-sbuild --skip-proposed mantic
Specified release (mantic) not known to debootstrap
Without this update users cannot generate mantic chroots for development. |
|
| 2023-06-07 17:00:37 |
Steve Langasek |
tags |
verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic verification-needed-lunar |
verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
|
| 2023-06-07 17:09:24 |
Steve Langasek |
tags |
verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy verification-needed-kinetic |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy |
|
| 2023-06-08 04:07:50 |
Steve Langasek |
tags |
verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal verification-needed-jammy |
verification-done-jammy verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal |
|
| 2023-06-08 04:31:43 |
Steve Langasek |
tags |
verification-done-jammy verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed |
|
| 2023-06-08 04:31:57 |
Steve Langasek |
ubuntu-dev-tools (Ubuntu Bionic): status |
In Progress |
Won't Fix |
|
| 2023-06-15 17:22:03 |
Launchpad Janitor |
ubuntu-dev-tools (Ubuntu Lunar): status |
Fix Committed |
Fix Released |
|
| 2023-06-15 17:22:29 |
Launchpad Janitor |
ubuntu-dev-tools (Ubuntu Kinetic): status |
Fix Committed |
Fix Released |
|
| 2023-06-15 17:22:55 |
Launchpad Janitor |
ubuntu-dev-tools (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-06-15 17:23:03 |
Launchpad Janitor |
debootstrap (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2023-06-15 17:24:09 |
Launchpad Janitor |
ubuntu-dev-tools (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2023-06-15 17:24:16 |
Launchpad Janitor |
debootstrap (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2023-06-16 17:08:34 |
Steve Langasek |
debootstrap (Ubuntu Focal): status |
Fix Released |
Triaged |
|
| 2023-07-02 21:09:02 |
Andreas Hasenack |
debootstrap (Ubuntu Focal): status |
Triaged |
Fix Committed |
|
| 2023-07-02 21:09:09 |
Andreas Hasenack |
tags |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed |
verification-done-jammy verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal |
|
| 2023-07-07 22:48:44 |
Steve Langasek |
tags |
verification-done-jammy verification-done-kinetic verification-done-lunar verification-failed-bionic verification-needed verification-needed-focal |
verification-done-focal verification-done-jammy verification-done-kinetic verification-done-lunar verification-failed-bionic |
|
| 2023-07-10 11:28:34 |
Launchpad Janitor |
debootstrap (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
