Package: buildd.debian.org When binNMUing a package, the time of the build is used for creating the changelog entry. This is an sbuild default due to #843773. That results in SOURCE_DATE_EPOCH not being equal for those builds and some tools embed that timestamp into packages for shared files. Doing so can result in unpack errors, when the relevant binary packages are marked Multi-Arch: same. An example package is libtie-hash-indexed-perl and it happens to break due to binNMUs being performed on different dates.
On the sbuild side, the idea is that you pass --binNMU-timestamp=... Unfortunately, it's not so easy on the wanna-build side as you can schedule a binNMU at any time. What makes matters worse is that each binNMU is scheduled individually and locks tables individually in that process (according to Aurelien Jarno). So while wanna-build could pass that flag to sbuild, it's not easy to produce an equal value for all binNMUs of a source package. Picking closer dates would have avoided the issue with libtie-hash-indexed-perl. Does anyone else see more options for solving this? Helmut
