Your message dated Wed, 23 Dec 2009 23:47:24 +0000
with message-id <[email protected]>
and subject line Bug#560189: fixed in mercurial-buildpackage 0.3
has caused the Debian Bug report #560189,
regarding "Main tarball must follow dpkg format 3.0" error is confusing
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
560189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560189
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mercurial-buildpackage
Version: 0.2
Severity: normal
Hi,
the following gives a cryptic error:
% mercurial-importorig ../upstream-1.0.tar.gz ../upstream-plugin-1.0.tar.gz
E: Main tarball must follow dpkg format 3.0
It should say that the filenames must follow the right pattern for 3.0
(quilt) format.
Actualy even better would be if the name does not matter. I would
prefer if the following would work:
% mercurial-importorig --version 1.2 /tmp/upstream.tar.gz /tmp/plugin.tar.gz
It should import the 2 tarballs as version 1.2 and (optionally?) copy
the 2 files to .. under the name expected by dpkg-source. Often
(allways) upstream names the files different to what dpkg-source wants
and having to rename them manualy prior to importing is tiresome.
It would also be nice to have an --empty-orig option that would import
an empty tar.gz (e.g. /usr/share/mercurial-buildpackage/empty.tar.gz)
file as maintarball. I have several packages now that only have
components and would like to avoid having to provide my own
empty.tar.gz for importing.
MfG
Goswin
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (499, 'unstable'), (2, 'experimental'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31.5 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages mercurial-buildpackage depends on:
ii devscripts 2.10.55 scripts to make the life of a Debi
ii libc6 2.10.1-7 GNU C Library: Shared libraries
ii libneko0 1.8.1-2 Lightweight virtual machine - shar
ii mercurial 1.3.1-1 scalable distributed version contr
ii neko 1.8.1-2 Lightweight virtual machine - comp
ii pristine-tar 1.00 regenerate pristine tarballs
Versions of packages mercurial-buildpackage recommends:
ii pbuilder 0.192 personal package builder for Debia
ii sudo 1.7.2p1-1 Provide limited super user privile
mercurial-buildpackage suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mercurial-buildpackage
Source-Version: 0.3
We believe that the bug you reported is fixed in the latest version of
mercurial-buildpackage, which is due to be installed in the Debian FTP archive:
mercurial-buildpackage_0.3.dsc
to main/m/mercurial-buildpackage/mercurial-buildpackage_0.3.dsc
mercurial-buildpackage_0.3.tar.gz
to main/m/mercurial-buildpackage/mercurial-buildpackage_0.3.tar.gz
mercurial-buildpackage_0.3_i386.deb
to main/m/mercurial-buildpackage/mercurial-buildpackage_0.3_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jens Peter Secher <[email protected]> (supplier of updated mercurial-buildpackage
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 23 Dec 2009 00:18:16 +0100
Source: mercurial-buildpackage
Binary: mercurial-buildpackage
Architecture: source i386
Version: 0.3
Distribution: unstable
Urgency: low
Maintainer: Jens Peter Secher <[email protected]>
Changed-By: Jens Peter Secher <[email protected]>
Description:
mercurial-buildpackage - Suite to maintain Debian packages in Mercurial
repository
Closes: 560189
Changes:
mercurial-buildpackage (0.3) unstable; urgency=low
.
* Porting branches are now suported.
* Always use Mercurial's internal merging mechanism to avoid arbitrary
merging programs to start up; instead conflict markers are put
directly in conflicting files.
* Explained repository layout in manpage, and various other manpage
fixes.
* Better error message when tarball filenames do not follow format 3.0,
thanks to Goswin von Brederlow.
(Closes: #560189)
Checksums-Sha1:
ccc2004ec97c1bcd3e2786df7e56ec46e5ad9a1b 967 mercurial-buildpackage_0.3.dsc
beaf9d44ac453f6f0c58810f72438c57c4b0a33d 25412
mercurial-buildpackage_0.3.tar.gz
95935d82aca2a21456831fd238b2b8e3c1cf6daf 217736
mercurial-buildpackage_0.3_i386.deb
Checksums-Sha256:
ef896fa7b02fbccf94a323fe72f19e06c85c681c3fbc10472b3b07fe4a93bb23 967
mercurial-buildpackage_0.3.dsc
c89d6d827ee708a2f8d6414d99d78968d01f3248d286955d08d6e8b5debb2c7c 25412
mercurial-buildpackage_0.3.tar.gz
badfa8b5b5d172265f3f075cce14481dded81d5bf2de3650f5afbf55f558e301 217736
mercurial-buildpackage_0.3_i386.deb
Files:
6e9a5b67beefe8ce960fc1155a6b6246 967 devel optional
mercurial-buildpackage_0.3.dsc
7078a910b2f201c069bd89e6ec24a18a 25412 devel optional
mercurial-buildpackage_0.3.tar.gz
dd89d18d0dbdd9d75e7567254fb49792 217736 devel optional
mercurial-buildpackage_0.3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iJwEAQECAAYFAksyqCEACgkQiFVdEFPVQL8VmgQAnSQLB2yyw48jbABpeq45oVBl
RZZLI3JP9HjucBF8JYWtDRxNtlFKY/EeJBgUa+Lnr6+qess+wdRigLPcvS+Zb5zx
6Ll9YDcp0isT8cCTwcnvVj/tO7V+RES2JI3tQqqcawyyBjPcveHfXgevEuYz1d3m
0RH1IyF6fLwUQvwF8gk=
=Dl8+
-----END PGP SIGNATURE-----
--- End Message ---
