Your message dated Mon, 16 Jul 2007 08:40:58 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433256: addendum
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
I get the following backtrace when I try to run
hg view
in a repos created by hg-buildpackage. If you want further details,
let me know. This was intended to merge in mercurial 0.9.4 from
upstream with Debian changes for 0.9.3.
I'm not sure what is happening, but something appears to be getting
hold of tags from mercurial's own repository and trying to add them to
the repos created by hg-buildpackage, understandably creating no end
of confusion.
Faheem.
*********************************************************************
[EMAIL PROTECTED]:/usr/local/src/mercurial-sarge/mercurial.upstream$ hg view
Error in startup script: tip
8:63df5ee3bb93
DEBIAN_mercurial_0.9.3-2~bpo2 6:611804829238
UPSTREAM_mercurial_0.9.4_TAG 4:ee39d1317ad2
UPSTREAM_mercurial_0.9.4 3:1a296fcadb50
UPSTREAM_mercurial_0.9.3_TAG 1:de95cecedf0d
UPSTREAM_mercurial_0.9.3 0:6240df7d3a51
[EMAIL PROTECTED], line 1: tag '0.4f' refers to unknown node
[EMAIL PROTECTED], line 2: tag '0.4e' refers to unknown node
[EMAIL PROTECTED], line 3: tag '0.4d' refers to unknown node
[EMAIL PROTECTED], line 4: tag '0.4c' refers to unknown node
[EMAIL PROTECTED], line 5: tag '0.5' refers to unknown node
[EMAIL PROTECTED], line 6: tag '0.5b' refers to unknown node
[EMAIL PROTECTED], line 7: tag '0.6' refers to unknown node
[EMAIL PROTECTED], line 8: tag '0.6b' refers to unknown node
[EMAIL PROTECTED], line 9: tag '0.6c' refers to unknown node
[EMAIL PROTECTED], line 10: tag '0.7' refers to unknown node
[EMAIL PROTECTED], line 11: tag '0.8' refers to unknown node
[EMAIL PROTECTED], line 12: tag '0.8.1' refers to unknown node
[EMAIL PROTECTED], line 13: tag '0.9' refers to unknown node
[EMAIL PROTECTED], line 14: tag '0.9.1' refers to unknown node
[EMAIL PROTECTED], line 15: tag '0.9.2' refers to unknown node
[EMAIL PROTECTED], line 18: tag '0.9.3' refers to unknown node
while executing
"exec hg tags"
(procedure "readrefs" line 4)
invoked from within
"readrefs"
(file "/usr/share/mercurial/hgk" line 3672)
-- System Information:
Debian Release: 4.0
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'stable'), (50, 'unstable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages hg-buildpackage depends on:
ii dctrl-tools 2.9.3 Command-line tools to process Debi
ii devscripts 2.9.26 Scripts to make the life of a Debi
ii dpkg-dev 1.13.25 package building tools for Debian
ii hg-load-dirs 1.1.4 Import upstream archives into darc
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libgmp3c2 2:4.2.1+dfsg-4 Multiprecision arithmetic library
ii mercurial 0.9.3-2~bpo2 Scalable distributed version contr
hg-buildpackage recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
OK, I have examined the Debian source package for Mercurial 0.9.4.
It ships both a .hgignore and .hgtags. The .hgignore is the reason that
debian/patches is ignored. The .hgtags is the reason that you are getting
those errors.
It is not the place for hg-buildpackage to delete or otherwise corrupt .hg*
files in your source directory. If you wish to do so, you can do that
manually.
I would suggest that the presence of .hg* in the mercurial source package in
Debian is a bug, though not a serious one.
I would also suggest that since MErcurial's upstream is in Mercurial, you may
be better off having mercurial.upstream pulled from there, rather than built
from Debian's orig.tar.gz packages.
-- John
On Sun July 15 2007 5:38:54 pm Faheem Mitha wrote:
> When doing the merge into 0.9.4, hg-buildpackage seems to have mislaid the
> patches directory. Not sure if this is something I'm doing wrong.
>
> The problem appears to be that though the patches directory is correctly
> added in the import of Debian sources, it is not registered by the
> repository created by hg-buildpackage, namely
>
> changeset: 6:611804829238
> tag: DEBIAN_mercurial_0.9.3-2~bpo2
> parent: 2:b1560ebbfd39
> user: [EMAIL PROTECTED]
> date: Sun Jul 15 17:46:33 2007 -0400
> files: .hgtags debian/NEWS debian/README.Debian debian/changelog
> debian/compat debian/control debian/copyright debian/dirs debian/docs
> debian/examples debian/hgext.rc debian/mercurial.postinst debian/preinst
> debian/pyversions debian/rules debian/watch description:
> Import Debian mercurial 0.9.3-2~bpo2
> Imported mercurial-0.9.3
> into Mercurial repository
>
> Take care,
> Faheem.
--- End Message ---
