Your message dated Thu, 7 Jun 2007 08:01:37 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427868: hg-buildpackage generated orig.tar.gz differs from
the checksum of upstream
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: hg-buildpackage
Version: 1.0.2
Severity: normal
Hi! It seems that the orig.tar.gz generated by hg-buildpackage is not the same
as the upstream tarball, checksum-wise. Is this a given? Should it the
checksum be the same as upstream?
Thanks
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages hg-buildpackage depends on:
ii dctrl-tools 2.9.3 Command-line tools to process Debi
ii devscripts 2.10.4 Scripts to make the life of a Debi
ii dpkg-dev 1.14.4 package building tools for Debian
ii hg-load-dirs 1.1.4 Import upstream archives into darc
ii libc6 2.5-10 GNU C Library: Shared libraries
ii libgmp3c2 2:4.2.1+dfsg-4 Multiprecision arithmetic library
ii mercurial 0.9.3-2 Scalable distributed version contr
hg-buildpackage recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Jun 07, 2007 at 03:25:47PM +1000, Jan Michael Alonzo wrote:
> Package: hg-buildpackage
> Version: 1.0.2
> Severity: normal
>
>
> Hi! It seems that the orig.tar.gz generated by hg-buildpackage is not the same
> as the upstream tarball, checksum-wise. Is this a given? Should it the
> checksum be the same as upstream?
It will likely never be, since gzip stores a creation date in the file.
Not only that, but tar stores uid/gid information for each file, which
will likely be different on your box than the upstream's.
The orig.tar.gz generation is most useful for Debian-native packages.
For other packages, if you like, you can let hg-buildpackage generate
the orig.tar.gz once, and reuse it for subsequent uploads. Or I just
rename upstream's tarball to the orig.tar.gz, and hg-buildpackage will
then leave it alone.
-- John
--- End Message ---
