clone 491329 -1 reassign -1 mercurial-common # I will not start to bikeshed here; # since commit-tools config or other extensions' files are rightfully present, # it looks like hgk extension breaks under relatively common conditions; # I don't think it we could call exotic a case where an extension is removed severity -1 serious retitle -1 fails to start if some other extension is removed (not purged) thanks
2009/1/26 Vincent Danjean <vdanj...@debian.org>: > severity 491329 minor > retitle 491329 commit-tool: causes hg error messages if removed but not purged > thanks > > Hi, > > Debian Bug Tracking System wrote: >>> severity 491329 serious > > I do not really see why you want to raise the severity to such a level. > I'm downgrading it again. I'm also giving it back its more generic title. > If you want to give information about ANOTHER bug, then open a new bug please. Maybe because it breaks other software? But, anyways, this issue is not that clear, since it is a bug of hgk triggered by commit-tool's config (and possibly other extensions). > The fact is that > * the package 'commit-tool' will NEVER remove its config file on removal > (only in purge). It would be against strong Debian policy requirements. > => nothing can be done in commit-tool > * mercurial is designed to print a message on its error output when an > extension cannot be loaded. > => you can try to open a bug for this... (upstream because this will not > be a kind of patch that can be applied only in a Debian package of the > software) > But I find myself that mercurial is sane here > * the hgk extension breaks when mercurial sends it some kind of data (messages > on stderr) > => this is probably the real root of error. If you agree with me, you should > open a bug for this (the best would be a bug upstream and then a bug in > Debian that reference this upstream bug) Well, isn't it a little bit late to wait for upstream? Anyway, I am an accidental hg user - I was trying to find the root cause of #511708 (hg bisect) and I stumbled over this bug. Not being able to use "hg view" looks like a pretty ugly bug, taking into account that is like gitk for hg. > 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. -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
