{"id":170570,"date":"2026-05-10T18:25:01","date_gmt":"2026-05-10T16:25:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-debian-utverzhdena-obyazatelnaya-podderzhka-vosproizvodimyh-sborok-paketov"},"modified":"2026-05-10T18:25:01","modified_gmt":"2026-05-10T16:25:01","slug":"v-debian-utverzhdena-obyazatelnaya-podderzhka-vosproizvodimyh-sborok-paketov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-debian-utverzhdena-obyazatelnaya-podderzhka-vosproizvodimyh-sborok-paketov","title":{"rendered":"Debian has approved mandatory support for reproducible package builds.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The team responsible for Debian releases has announced that reproducible rebuilds of packages will become a mandatory feature. Changes have been made to the build system that block the transfer of new packages that do not support reproducible builds into the repository. In the testing repository, it is also prohibited to update existing packages that have been found to have regressions with reproducible builds. <\/p>\n
In Debian 13, which contains 36,427 source packages, the support for reproducible builds is 96.9% for the x86_64 architecture and 96.8% for the ARM64 architecture. In the Debian Testing repositories, the level of reproducible builds is evaluated at 94.5% for the ARM64 architecture and 75.7% for x86_64 when rebuilding 37,809 source packages. The reproducible builds test in the Debian Testing repository has failed for 1,141 packages (3%), while 7,952 packages (21%) encountered common issues when compiling from source. <\/p>\n
Reproducible builds allow the user to create their own builds that match exactly the binary builds available for download. Users can personally verify that the binaries distributed in packages and installation images are compiled from the provided source texts and do not contain hidden alterations. The verification of the binary build's identity enables not to rely solely on trust in the distribution's build infrastructure, as compromising the compiler or tooling might lead to the insertion of hidden backdoors. <\/p>\n
In the formation of reproducible builds, nuances such as exact dependency matching are taken into account; the use of an unchanged set and versions of build tools; an identical set of options and default settings; preserving the order of file builds (using the same sorting methods); and disabling the compiler from adding unstable metadata such as random values, file path references, and build date and time data. Errors and race conditions in the tooling also affect build reproducibility. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"