severity 513183 normal
thanks
This bug is not in the core mercurial (ie the core software works
correctly). It is in an extension (hgk).
I really do not think that such a bug should prevent mercurial to be
released with lenny (which would be the case if the severity is kept at
'serious' level).
I think that this bug in hgk will be corrected now that it has been
discovered. But, unless someone comes quickly with a good patch, I do not
think it will be corrected before lenny.
And the workaround is simple: just correct the mercurial configuration
so that the warning is not triggered anymore.
Eddy Petrișor wrote:
> 2009/1/26 Vincent Danjean <vdanj...@debian.org>:
>> Because, if I read correctly your short report, you complain about the
>> hgk extension not working as soon as mercurial emits some of its standard
>> warning messages. Any extensions (not just commit-tool) will trigger this
>> bad behavior of hgk if they call not be loaded.
>
> Probably the easiest fix is to redirect the warning about the
> inability to load the extenson to stderr.
The message is already on stderr:
vdanj...@eyak:~$ cat ~/.hgrc
[extensions]
hgext.yo=
vdanj...@eyak:~$ hg > /dev/null
*** failed to import extension hgext.yo: No module named yo
vdanj...@eyak:~$
Regards,
Vincent
--
Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org
GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87
Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package
APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
