I have set up a working
pbuilder toolchain for building Debian packages in
amd64 varieties for Ubuntu. I am using
reprepro to manage my own private apt repository and
dupload to upload
.debian.tar.gz files into it. All of this is well documented and it works.
But I am failing to upload the
i386 version of one package together with the
amd64 version of the same package. Reprepro complains with the following message:
File "pool/main/p/package/package_1.0.dsc" is already registered with different checksums!
The source of the generated
amd64 binary packages are exactly the same and have not been modified by me. How can it be that there is a different checksum?
I investigated and discovered that the checksum difference of the
.dsc file is because it contains a differing checksum of the file
Further investigations showed that the
package_1.0.debian.tar.gz file has indeed different checksums every time
dpkg-buildpackage is invoked by the debian build toolchain. The reason is that it changes the modification time of the
/debian subdirectory of a Debian package. The
tar program unfortunately includes the modification time into the resulting archive, leading to different checksums every time the toolchain is run.
So, my question is: How can I prevent
dpkg-buildpackage from modifying the modification date of the
/debian directory when building a Debian package?
If I could do that, the checksum of the files
package_1.0.dsc would stay constant, and I could painlessly upload to