On 11/30/2023 8:33 AM, Conrad Hoffmann wrote:
> I tried to apply this, but the image does not build (on /lts, at least?):> > https://builds.sr.ht/~bitfehler/job/1104224
That is correct. But that is unfortunately not caused by the genimg
script. The current ubuntu/next is also failing [1].
This is caused by the ubuntu/lts image being VERY VERY out of date.
Inserting `sudo apt update && sudo apt upgrade -y` fixed the issue. This
is a repro [2] on the current ubuntu/next 4 months ago. It's fair to say
that ubuntu/lts hasn't been updated, for some unknown reason, for at
least 4 months now.
[1] https://builds.sr.ht/~sircmpwn/job/1104523
[2] https://builds.sr.ht/~haowenl/job/1028259
On 12/1/23 01:02, Haowen Liu wrote:
> On 11/30/2023 8:33 AM, Conrad Hoffmann wrote:>> I tried to apply this, but the image does not build (on /lts, at least?):>>>> https://builds.sr.ht/~bitfehler/job/1104224> > That is correct. But that is unfortunately not caused by the genimg > script. The current ubuntu/next is also failing [1].> > This is caused by the ubuntu/lts image being VERY VERY out of date. > Inserting `sudo apt update && sudo apt upgrade -y` fixed the issue. This > is a repro [2] on the current ubuntu/next 4 months ago. It's fair to say > that ubuntu/lts hasn't been updated, for some unknown reason, for at > least 4 months now.
QQ: have you been getting any emails about build failures for these?
According to the Ubuntu build.yml, you shoud get those
On 12/1/23 01:02, Haowen Liu wrote:
> This is caused by the ubuntu/lts image being VERY VERY out of date. > Inserting `sudo apt update && sudo apt upgrade -y` fixed the issue. This > is a repro [2] on the current ubuntu/next 4 months ago. It's fair to say > that ubuntu/lts hasn't been updated, for some unknown reason, for at > least 4 months now.
This would be quite strange. All recent builds for the LTS image have
succeeded [1]. I also verified that the image deployed to the build
worker is indeed only a few days old.
I am not quite sure what to make of this?
[1] https://builds.sr.ht/~sircmpwn/refresh/ubuntu/lts
Cheers,
Conrad
On 12/4/2023 10:06 AM, Conrad Hoffmann wrote:
> I am not quite sure what to make of this?> > [1] https://builds.sr.ht/~sircmpwn/refresh/ubuntu/lts> > Cheers,> Conrad
Yup, not sure either. One of the following three is happening:
1. genimg is building an outdated image to begin with
2. The updated version image is not properly deployed
3. The properly deployed version did not get used by builds.sr.ht
Maybe start by checking the deployed image timestamp?
Haowen
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
On 12/4/2023 9:44 PM, Taavi Väänänen wrote:
> 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
On 12/4/2023 9:50 PM, Taavi Väänänen wrote:
> 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/21/24 04:40, Haowen Liu wrote:
> Could you please check this patch once again?
Can you please re-submit the patch and include a link to a successful
build log?
Cheers,
Conrad