Closing since it's presumed fixed.
** Changed in: pbuilder (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/118180
Title:
Pbuilder gives a different
@Tyler thank you so much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/118180
Title:
Pbuilder gives a different md5sum for a source .diff.gz archive in
result than the one it started with
To
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Your issue should have been fixed in dpkg a while ago.
It would help us a lot if you could test it on a currently supported Ubuntu
version. When you test it and it is fixed for you, kindly upload the updated
This has been fixed upstream in dpkg 1.15.8.
** Changed in: dpkg (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/118180
Title:
Pbuilder gives a different
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
--
Pbuilder gives a different md5sum for a source .diff.gz archive in result than
the one it started with
https://bugs.launchpad.net/bugs/118180
You received this bug notification because you are a member of Ubuntu
Bugs,
Loïc, the issue seems to be the way diff parsed the directories for
comparison. The difference between the two .diff.gz files is the order
of files. My guess is that it compares directories in directory order,
not sorted by name.
--
Pbuilder gives a different md5sum for a source .diff.gz
@Tyler: that'd be a good explanation; however pbuilder just calls into
dpkg-dev (via dpkg-source/dpkg-buildpackage) to create/unpack .diff.gzs;
I suspect we should address this in dpkg-dev.
--
Pbuilder gives a different md5sum for a source .diff.gz archive in result than
the one it started with
By the way my current workflows gets around the above issue entirely: I
upload the source package to a PPA, and then it spews out .changes files
for each binary that don't refer to the .diff.gz
--
Pbuilder gives a different md5sum for a source .diff.gz archive in result than
the one it started
You should be calling pbuilder as usually for the first upload to your
archive (will include source) and with --binary-arch for all subsequent
uploads.
It might be interesting to see why the .diff.gz is modified; it could
either be a difference in the output on i386 and on amd64, or it could
be a
I have the same issue, same package. Building wine for i386 and amd64
with pbuilder. The .diff.gz has a different checksum (individual
patches inside the diff are reordered) on both architectures as from the
original:
pre[EMAIL PROTECTED]:~/src/wine$ md5sum ~/src/wine/wine_1.0.0-2eitri1.diff.gz
I've confirmed the same behaviour compiling hello.
--
Pbuilder gives a different md5sum for a source .diff.gz archive in result than
the one it started with
https://bugs.launchpad.net/bugs/118180
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Found the solution. By default pbuilder calls dpkg-buildpackage like
so:
DEBBUILDOPTS=$DEBBUILDOPTS -rfakeroot
dpkg-buildpackage -us -uc $DEBBUILDOPTS
That causes dpkg-buildpackage to rebuild the diff.gz and .dsc files.
Add a -b in there, and it won't. It also means the resulting .changes
file
** Summary changed:
- Pbuilder gives a different md5sum for a source .diff.gz archive in result
then the one it started with
+ Pbuilder gives a different md5sum for a source .diff.gz archive in result
than the one it started with
--
Pbuilder gives a different md5sum for a source .diff.gz
13 matches
Mail list logo
