> I am running gNewSense (metad) on a mipsel based machine. 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'm assuming metad is much newer than metad. Than doesn't parse :) > 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. > We're obviously not imagining it. 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. -- 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
