#1153821 cloud.debian.org: trixie 20261111-2659 release lacks genericcloud and nocloud images

#1153821#5
Date:
2026-11-12 10:48:20 UTC
From:
To:
Hi,

the trixie release build 20261111-2659, which "latest/" now points to,
is
missing the genericcloud and nocloud images. Builds up to and including
20261103-2651 had them.

Details, as of 2026-11-12:

* https://cdimage.debian.org/images/cloud/trixie/20261111-2659/
  Contains only generic (amd64, arm64, ppc64el, riscv64), azure and ec2
  images. 20261103-2651 also had genericcloud and nocloud. As a result,

https://cdimage.debian.org/images/cloud/trixie/latest/debian-13-genericcloud-amd64.qcow2
  returns 404.

*
https://cdimage.debian.org/images/cloud/trixie-backports/20261111-2659/
  Contains only generic images. The azure, ec2, genericcloud and
nocloud
  images that 20261103-2651 had are all missing.

* https://cdimage.debian.org/images/cloud/trixie/daily/latest/
  The directory contains generic, genericcloud and nocloud qcow2
images,
  but its SHA512SUMS lists only the nocloud ones. The dated daily build
  daily/20261111-2659/ looks complete.

* bookworm/latest/ is unaffected.

The CI definitions on master (.gitlab/ci/generated.yml and
generated-daily.yml) still contain genericcloud and nocloud jobs for
trixie, so this doesn't look like an intentional removal. The switch to
mkosi (MR !495, merged 2026-11-05) landed between the last complete
build and this one. That may or may not be related.

Tools that pick the image from latest/SHA512SUMS currently can't find a
genericcloud image for trixie.

Thanks for your work on the cloud images!

#1153821#10
Date:
2026-11-12 19:08:56 UTC
From:
To:
This is now resolved.

We're dealing with ongoing publishing issues with the cloud images and
are having to manually run certain steps in the workflow.  So
publication of certain images may be delayed until those issues are
resolved.

I should be able to ensure that the 'latest' directory is complete in
future manual tasks, if they are necessary...

noah

#1153821#15
Date:
2026-11-12 19:08:56 UTC
From:
To:
This is now resolved.

We're dealing with ongoing publishing issues with the cloud images and
are having to manually run certain steps in the workflow.  So
publication of certain images may be delayed until those issues are
resolved.

I should be able to ensure that the 'latest' directory is complete in
future manual tasks, if they are necessary...

noah