| 2024-02-25 13:11:16 |
Åka Sikrom |
bug |
|
|
added bug |
| 2024-02-25 13:11:16 |
Åka Sikrom |
attachment added |
|
Output of debootstrap and debootstrap.log https://bugs.launchpad.net/bugs/2054925/+attachment/5749150/+files/2024.02.25_debootstrap_base-files.13ubuntu7.vs.13ubuntu6.log |
|
| 2024-02-25 13:15:41 |
Åka Sikrom |
attachment removed |
Output of debootstrap and debootstrap.log https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+attachment/5749150/+files/2024.02.25_debootstrap_base-files.13ubuntu7.vs.13ubuntu6.log |
|
|
| 2024-02-25 13:16:01 |
Åka Sikrom |
attachment added |
|
Output of debootstrap and debootstrap.log https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054925/+attachment/5749151/+files/2024.02.25_debootstrap_base-files.13ubuntu7.vs.13ubuntu6.log |
|
| 2024-02-25 16:08:27 |
Steve Langasek |
base-files (Ubuntu): assignee |
|
Julian Andres Klode (juliank) |
|
| 2024-02-25 17:17:37 |
Steve Langasek |
tags |
|
rls-nn-incoming |
|
| 2024-02-25 19:22:32 |
Julian Andres Klode |
base-files (Ubuntu): status |
New |
Incomplete |
|
| 2024-02-25 19:22:56 |
Julian Andres Klode |
bug task added |
|
debootstrap (Ubuntu) |
|
| 2024-02-25 19:23:12 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Focal |
|
| 2024-02-25 19:23:12 |
Julian Andres Klode |
bug task added |
|
base-files (Ubuntu Focal) |
|
| 2024-02-25 19:23:12 |
Julian Andres Klode |
bug task added |
|
debootstrap (Ubuntu Focal) |
|
| 2024-02-25 19:23:12 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-02-25 19:23:12 |
Julian Andres Klode |
bug task added |
|
base-files (Ubuntu Jammy) |
|
| 2024-02-25 19:23:12 |
Julian Andres Klode |
bug task added |
|
debootstrap (Ubuntu Jammy) |
|
| 2024-02-25 19:23:17 |
Julian Andres Klode |
bug task deleted |
base-files (Ubuntu Focal) |
|
|
| 2024-02-25 19:23:22 |
Julian Andres Klode |
bug task deleted |
base-files (Ubuntu Jammy) |
|
|
| 2024-02-25 19:23:26 |
Julian Andres Klode |
debootstrap (Ubuntu): status |
New |
Fix Released |
|
| 2024-02-25 19:24:29 |
Julian Andres Klode |
debootstrap (Ubuntu Focal): status |
New |
Triaged |
|
| 2024-02-25 19:24:32 |
Julian Andres Klode |
debootstrap (Ubuntu Jammy): status |
New |
Triaged |
|
| 2024-02-25 19:59:59 |
Julian Andres Klode |
base-files (Ubuntu): status |
Incomplete |
Won't Fix |
|
| 2024-02-25 20:44:25 |
Åka Sikrom |
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 against any up-to-date Ubuntu public archive mirror as of today.
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. |
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
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. |
|
| 2024-02-26 10:21:15 |
Julian Andres Klode |
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
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. |
[Impact]
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
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
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
both in buildd and normal variant.
[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. |
|
| 2024-02-26 10:32:05 |
Julian Andres Klode |
debootstrap (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2024-02-26 10:37:22 |
Julian Andres Klode |
description |
[Impact]
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
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
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
both in buildd and normal variant.
[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. |
[Impact]
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
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
- debootstrap focal
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
both in buildd and normal variant.
[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. |
|
| 2024-02-26 10:42:10 |
Julian Andres Klode |
description |
[Impact]
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
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
- debootstrap focal
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
both in buildd and normal variant.
[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. |
[Impact]
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
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
- debootstrap focal
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
both in buildd and normal variant, also specifically for noble, --merged-usr should be ignored.
[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. |
|
| 2024-02-26 10:42:24 |
Julian Andres Klode |
description |
[Impact]
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
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
- debootstrap focal
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
both in buildd and normal variant, also specifically for noble, --merged-usr should be ignored.
[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. |
[Impact]
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
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
- debootstrap focal
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
- debootstrap noble --merged-usr
both in buildd and normal variant, also specifically for noble, --merged-usr should be ignored.
[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. |
|
| 2024-02-26 15:22:22 |
Julian Andres Klode |
debootstrap (Ubuntu Focal): status |
Triaged |
In Progress |
|
| 2024-02-26 15:34:18 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2024-02-26 16:13:40 |
Julian Andres Klode |
description |
[Impact]
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
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
- debootstrap focal
- debootstrap jammy
- debootstrap mantic
- debootstrap noble
- debootstrap noble --merged-usr
both in buildd and normal variant, also specifically for noble, --merged-usr should be ignored.
[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. |
[Impact]
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
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. |
|
| 2024-02-26 21:49:08 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Julian Andres Klode |
| 2024-02-26 22:13:04 |
Julian Andres Klode |
nominated for series |
|
Ubuntu Mantic |
|
| 2024-02-26 22:13:04 |
Julian Andres Klode |
bug task added |
|
base-files (Ubuntu Mantic) |
|
| 2024-02-26 22:13:04 |
Julian Andres Klode |
bug task added |
|
debootstrap (Ubuntu Mantic) |
|
| 2024-02-26 22:13:09 |
Julian Andres Klode |
debootstrap (Ubuntu Mantic): status |
New |
Fix Released |
|
| 2024-02-26 22:50:30 |
Mauricio Faria de Oliveira |
debootstrap (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2024-02-26 22:50:33 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-02-26 22:50:39 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber SRU Verification |
| 2024-02-26 22:50:49 |
Mauricio Faria de Oliveira |
tags |
rls-nn-incoming |
rls-nn-incoming verification-needed verification-needed-jammy |
|
| 2024-02-27 16:03:36 |
Talha Can Havadar |
bug |
|
|
added subscriber Talha Can Havadar |
| 2024-02-27 19:01:12 |
Dan Watkins |
bug |
|
|
added subscriber Dan Watkins |
| 2024-02-28 07:17:17 |
Steve Langasek |
description |
[Impact]
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
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. |
[Impact]
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
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
- mk-sbuild
- pbuilder-dist $release create
- 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. |
|
| 2024-02-28 07:18:16 |
Paul Mars |
bug |
|
|
added subscriber Paul Mars |
| 2024-02-28 10:40:59 |
Taihsiang Ho |
bug |
|
|
added subscriber Taihsiang Ho |
| 2024-02-29 17:35:37 |
Julian Andres Klode |
tags |
rls-nn-incoming verification-needed verification-needed-jammy |
verification-done verification-done-jammy |
|
| 2024-02-29 17:50:06 |
Launchpad Janitor |
debootstrap (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-02-29 17:50:13 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2024-03-04 21:21:03 |
Mauricio Faria de Oliveira |
debootstrap (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2024-03-04 21:21:06 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-03-04 21:21:17 |
Mauricio Faria de Oliveira |
tags |
verification-done verification-done-jammy |
verification-done-jammy verification-needed verification-needed-focal |
|
| 2024-03-04 21:22:52 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Mauricio Faria de Oliveira |
| 2024-03-07 09:15:53 |
Hector CAO |
bug |
|
|
added subscriber Hector CAO |
