Notes about issue varying_mtimes_in_data_tar_gz_or_control_tar_gz in unstable
| Identifier: | varying_mtimes_in_data_tar_gz_or_control_tar_gz |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| URL: | https://wiki.debian.org/ReproducibleBuilds/Howto#Members_of_control.tar_and_data.tar_have_varying_mtimes |
| Description: |
We currently adjust the file mtimes in dh_builddeb. Packages which calls `dpkg --build` directly should have a prior call to: `export SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog --count 1 -SDate)" +%s)` and `find debian/tmp -newermt "@$$SOURCE_DATE_EPOCH" -print0 | \ xargs -0r touch --no-dereference --date="@$$SOURCE_DATE_EPOCH"` Another option is to convert the build system to `dh`. |
|
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |
|
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A # sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a P means a
pending bug while # indicates a
closed bug. In cases of several bugs, the symbol is repeated.