Haowen Liu: 1
ubuntu/noble starts development
5 files changed, 11 insertions(+), 4 deletions(-)
Hi Conrad,
Could you please check this patch once again? With this [1] commit, this
Can you please re-submit the patch and include a link to a successful
build log?
Cheers,
Conrad
patch should be good to go.
Haowen
[1]
https://git.sr.ht/~sircmpwn/builds.sr.ht/commit/1b21add920b56007b8597db667e858a403a88b1d
Is there a plan to bring Ubuntu builds back in good working order?
When building a new jammy image, debootstrap by default only includes
the main jammy APT suite, and then the genimg script then adds extra
suites (for example jammy-security and jammy-updates) to the
sources.list file later to be used for any future apt commands.
However to build a mantic image on jammy, you need the distro-info-data
package from jammy-updates[0]. debootstrap pulls down the
distro-info-data package from the jammy suite as a part of the base
image for some reason, and the manual `sudo apt update && sudo apt
upgrade -y` you tried pulls the newer version from `jammy-updates` which
explains why it fixes the build.
[0]: https://packages.ubuntu.com/source/jammy-updates/distro-info-data
Taavi
Thanks for explaining this! Do you know how to make deboostrap add
jammy-security and jammy-updates to the list of repos it pulls from? Or
should I just run apt-get upgrade at the end of genimg?
Haowen
According to its manpage, you can pass --extra-suites= to specify a
comma-separated list of additional suites. I've never tried it though,
and I don't ever recall seeing the same issue on the Debian image.
Taavi
Thank you! I checked how genimg is doing things and it seems it
currently overrides the source list after bootstrapping. I chose the
route of less disruptive change and simply added an extra upgrade in the
genimg process.
See [1].
[1] https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/47411.
Haowen
On 1/23/2024 6:19 AM, Conrad Hoffmann wrote:>