Pbuilder gives a different md5sum for a source .diff.gz archive in result than the one it started with
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
pbuilder (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pbuilder
To build my Wine packages on different arches, I do the following procedure:
First I modify the source to make sure it works properly. Then I build a source archive using dpkg-buildpackage -S -rfakeroot. This gives me a .dsc file, a .orig.tar.gz file, and a .diff.gz file.
I then use pbuilder on the i386 computer to build an i386 version of the package for upload to my apt repository. I then upload everything in pbuilder's results directory to my APT repository, and add them to create an i386 version of the new package.
Then, I take those .dsc, .orig.tar.gz, and .diff.gz file to an amd64 computer and tell pbuilder to build the package. Everything builds as normal, however some of the files in the pbuilder result directory will have a different md5sum than expected - namely, the .diff.gz file. Since the source archive is the same, there's no reason for this file to have changed, unless pbuilder messed with it in some way - the most likely thing is decompressing it and then rebuilding it with greater compression settings, rather than simply copying the .diff.gz file into the result folder.
This presents a problem, since the resulting .changes file now points to what should be the same .diff.gz file as the i386 package, but with a different md5sum. If I upload these files to my apt repository and try to tell reprepro to add them, reprepro will throw an error because of the conflicting "identical" file with a different md5sum.
As a workaround, so far I've been manually removing the offending line from the second .changes file (and ignoring the new .diff.gz file altogether), however a much more elegant solution is to fix pbuilder itself.
I have the same problem here...