Marc Dequènes (Duck) <d...@duckcorp.org> ha escrit: > No, you're wrong, this is the right place to send a bug, so that the > maintainer can check if it relevant,
You did not get the point: it's not about bugs.debian.org. It's about the proper address to report Dico-related bugs to. The proper place to report these bugs is to <bug-d...@gnu.org.ua> *not* to <g...@gnu.org.ua>. > But you're right, i should have tested this problem with the dico > client instead. That's another good reason to filter reports before > sending them to the author directly. I'm then reassigning this bug to > the dict package, as it is not reproducible with the dico client > ("dico --host=dico.duckcorp.org --noauth -m kuruma" works). I see now. The report was worded such that it was unclear to me that they were having the problem with their *server*, not the client program. There's no use reassigning this bug, as `dict' client has indeed nothing to do with it. The difference between operation of `dict' and `dico' is that the former by default issues MATCH * . "kuruma" whereas the latter issues MATCH ! . "kuruma" You can easily reproduce this by connecting to dico.duckcorp.org:2628 and issuing the latter command. It will disconnect silently. To handle this I need additional information, namely: any log messages issued by dicod at dico.duckcorp.org and exact contents of the configuration file that is used there. > or wait for the Debian maintainer to forward you the relevant bugs. Once again, let me underline that any bug reports should be forwarded not to "me", but to <bug-d...@gnu.org.ua>. Thank you. Regards, Sergey -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org