Currently I have no access to the only box where I can reproduce this bug (it is a fileserver at a customer's office). However I'll post here all the info you ask as soon as I can access the server.
<rant> About the RC bug argument: I didn't even know that a grave bug is RC while an important one isn't. I simply read the instructions that reportbug prints on the screen: it says that the bug is grave when the package is completely unusable, and that's exactly the situation on said server. Is it not a bash-completion bug? Ok, I take your word, but please recognize it's not easy for non-developers to identify the right package... a common user who takes himself the time to report a bug could even think it's a bash bug (though a minor one in that case). I think you developers/maintainers should be thankful when someone reports a bug, instead of complaining about mistakes in the bug report and arguing I deliberately raised the bug severity in hope to get faster attention. I've read the reportbug instructions and thought twice about what severity to choose and finally I choose what seemed the best fit based on my observations. Is the "grave" severity badly described in reportbug? Fix it! You are the developers after all! </rant> Anyway, I don't understand how that can be a bug of a different package, but, again, I take your word. @David: I did not hack my code, I suppose that "-sh" is not to be looked for inside the code, but I think it's only the interpreter of the script. Maybe the users on that server have /bin/sh as default shell, I can't check right now. Maybe also I'm saying meaningless things... Lucio. _______________________________________________ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
