Bug#1036828: debian-cd: wrong firmware archives built and published for D-I releases?

Cyril Brulebois <[email protected]>
Newsgroups gmane.linux.debian.devel.cd
Organization Debian
Message-ID <[email protected]>
Control: tag -1 patch pending

Cyril Brulebois <[email protected]> (2023-05-27):
> For the record, those archives end up being published in locations like
> the following, and I definitely expected those to match the firmware
> packages getting shipped into the images, not be some kind of snapshot of
> what's in unstable at the time the release is built!
> 
>     https://cdimage.debian.org/cdimage/firmware/bookworm/bookworm_di_rc3/
> 
> We should definitely clarify the situation, and get to the bottom of that
> double firmware build.
> 
> From the log lines quoted above, if both bookworm and sid builds end up
> shipping files in the same destination directory, the last build wins and
> overrides the first one entirely?

I'm considering the following change for the upcoming (pseudo) RC 5 release:
  https://salsa.debian.org/images-team/setup/-/commit/9a77631

This means nothing changes for weekly builds, which are detected as being
built with DEBVERSION set to “testing” (please note that I didn't
investigate what happens to firmware directories in this case).

Meanwhile, actual releases get that sid job skipped (since the release
specific config file, e.g. CONF.sh.bookworm_di_rc4, sets DEBVERSION to
“bookworm-DI-rc4” instead of sticking to the default “testing” value).


Cheers,
-- 
Cyril Brulebois ([email protected])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmSAqikACgkQ/5FK8MKz
VSDWMQ//YRSYta88lDprsXEmqSJMFhV8izz7EaW5PGUPDi7j2yLFae7w7Cbot8Kp
L27xmmT+aN+RgzFU5niwot886yMngLYXraznrMKjZ79LutEyPlHFQ9dFztbQkXvM
S8xnjnXBnsdzfjS5/rRMM7rG5tDYnDcX3V8KRWqSWO5dtwrkwcEK0sLi2otUHu+M
NUaQYi25Rf5bAX9e0VIvF606SUEHnaDURIO76kAKzHsSGdXIO1n1v0wR3wVemIH4
eRCCP6LOOM7h3SDZNi2/DfZeKKgVURkq+3PbJ+CHLFwNBdnkK6XN9G7hb8nUZn+6
bZef2aAfN48eGCOqt7PxPZNV3C4F7tGmd28ukCC9X9bNdI7Sh1MSn3rGXIQTdGzH
Ze88BUrbzuTgnaT/p3qVEwQBISuY4l/vCYcHKtziugyOrjet5V/cHhhoZqNGbRMY
MkFBNEkPBPcROtNIbXnAdAA7VHUD+JIvXcz1dL17+Efi0ty2a01ko2clC9e8MeJp
yKU4ol0txdnqoDBRhU7ujtyweGzR8HzLdW8ED66iqgNiELg6yqQXh8q3WSH4tsq7
jqERcOA9KWoHLuVF4Cf+tfs1WPN61PZFzAZT4K39pUqoEia3rN5DIIlS8QzApU/M
ReHShEnAa9fknIH8LtcgMYPdA3eIfEolxHvEinOqw8uvuKbkWG0=
=m8Rf
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.