Hello, i'm seeing that Anthony closed this bugreport. I - as the reporter - don't agree.
Using m-a is *solution* to go round the problem. Short info how i notice the problem with this package: On mailing list debian-user-german one ask to compile the modules on an seperate pc, rans in problemes and ask on the list. I told him to read the Readme's and go the way proposed there with dpkg-reconfigure or debian/rules binary-modules. He still has problems. Then i do it on my pc and found the problems reported by my two reports. So i think we must: Find a solution doing it right like the Readme's say. And dpkg-reconfigure <paket> is a "official" debian tool. BTW: dpkg-reconfigure is the only paket-tool to configure /etc/lirc/lirc.conf. Or we must change the Readme's to force users to use m-a. But how could one read them when the paket unpacked? I would prefer a fix like: Using dpkg-reconfigure to edit the lirc.conf. Then, instead of building the modules, debconf dialog suggest the user to install m-a und use this to build the modules for his kernel. To document this i prefer to put a Readme.Debian in the paket where this is also documented. Sid and testing user should use BTS as a additional Doc-Structure, but since Etch goes further to release this is IMHO not the way. Greetings Gerhard -- Try rm -rf (_R_ead _M_ail _R_ealy _F_ast) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]