Trying to be positive, we have a possible work-around for our own system (drop /packages/local/bin from $PATH) but it is not really a decent fix. The underlying problem is difficult in that all current 32-bit and 64-bit DB files look similar, so work on an improved libgdbm3 is going to be difficult to manage that discrimination. So what is the best option for the 'man' command? Should it ignore the $PATH search for index.db files and stick to those locations configured locally (e.g. by $MANPATH and/or /etc/manpath.config)? Or still scan $PATH but ignore any files on network drives (that are potentially generated by another word-size machine)?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001189 Title: 'man' command fails with lseek error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1001189/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
