These are files containing source code for the Debian operating system.
The files here are in "jigdo" format. Use jigdo tools to download the contents of the complete ISO image files from what's here and a normal Debian mirror. You should end up with an exact copy of each ISO image as though you'd downloaded it directly via HTTP or FTP.
Once you have downloaded all the ISO images you want, you will typically need to write them to installation media.
The images described here are sized to be written to writeable Blu-Ray media at a minimum, but may be written to larger media if needed.
There are files here (SHA1SUMS, SHA256SUMS, etc.) which contain checksums of the images. These checksum files are also signed - see SHA1SUMS.sign, SHA256SUMS.sign, etc. Once you've downloaded an image, you can check:
For more information about how to do these steps, read the verification guide.
See the Debian CD FAQ for lots more information about Debian CDs and installation.
The images here were put together by the Debian CD team , using debian-cd and other software.
After the 9.2.0 release was made and published, a bug was found with the sorting of packages in the full DVD, BD and DLBD sets. Due to a glitch on release day, popularity contest data was not available and this caused packages to be sorted incorrectly.
This may seem like a comparatively minor issue, but it broke an important feature for some users. After the core set of packages needed for the installer, desktops, etc. are placed onto the first disc in a given set, we normally organise packages in order of decreasing popularity such that most users will typically never need to use more than the first 2 or 3 DVDs (for example). This bug broke that feature, meaning that even quite popular packages could have ended up on DVD#14 due to random sorting.
The 9.2.1 build fixes this bug. The build scripts have also been updated to ensure this bug cannot happen again in future - the build will abort if there is a problem updating popcon data.
If you have already installed using 9.2.0, you are unlikely to be affected by this bug. Live images and netinst images are totally unaffected. Apologies for any problems caused for users.