Hi, I'm still concerned about this issue. As far as I understand, the ghc in hardy has a bug which returns random data when asked for the inode number. This causes any darcs executable built with that ghc to run very slowly (presumably because it is trying to use a bunch of random bogus inode numbers?). Until this is fixed in Hardy, I have to ask people to be careful not to use ghc on Hardy, which raises the question of what they should do instead. If this is fixed, I can instead ask them just to upgrade to the fix.
-- Please SRU ghc6 in Hardy to fix correctness bug https://bugs.launchpad.net/bugs/280129 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
