On Mon, 2011-01-31 at 11:20 +0000, Stefano Rivera wrote: > Yup, and it has mercurial 1.0.1-5.1 which is pretty ancient, and was > never part of a stable Ubuntu release. It was part of a stable Debian > release, lenny, but without this bug.
I think you're right. I wonder why they are using such an ancient package. > > I'm assuming metad is much newer than metad. > > Than doesn't parse :) Sorry, I meant metad newer than jaunty. But given the antiquity of the package, I'm not sure any more. > > > This appears to be a problem with the packaging > > No, the issue is that common.py is appearing in mercurial. I don't see > this on lenny or the version that built on Ubuntu: /usr/lib/python- > support/mercurial/python2.4/hgext/inotify/common.py > > I can see this in Ubuntu 1.0.1-5.1 on sparc, not entirely sure why, > presumably there is/was something different in the behavior of python > /python-support on sparc. However it was fixed in newer versions. Ah I see. > It certainly *was* a bug in Ubuntu, but it isn't any more. Sparc is no > longer supported, and there are no supported versions of Ubuntu showing > this bug. Well let's hope that for the next gNewSense release, they use a recent Ubuntu base. -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/400236 Title: Mercurial conflicts with python (jaunty sparc at least) -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
