2009/1/27 Vincent Danjean <[email protected]>: > 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 agree. > 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. Or simply fix the extension not to choke on stderr stuff ;-) >> 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:~$ OK. OTOH, wouldn't the title of this bug (the cloned one) be better if it would be: hgk/hg view fails to start when hg complains instead of the current hgk doesn't like it when hg complains After all, that's what happens, and "doesn't like it" is not clear what it means. -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
