mirsal <mir...@mirsal.fr> wrote: Hi,
> Would you mind sharing a few pointers about what's wrong, or at least > which approach sounds the most sensible so I can research and get this > right ? 1. mt-daapd is dead. Stop flogging the dead horse. Really. 2. adding debconf is big no-no, doubly so if you're trying to get this an update in stable 3. not starting the service also means the service won't be restarted if it's running upon upgrade, which turns security updates into no-ops The best way to handle this is to have mt-daapd reply with an error code/page as long as the admin password is still the default and the request is not coming from localhost (localhost is special-cased and bypasses the admin password entirely). But, again, flogging a dead horse. JB. -- Julien BLACHE <jbla...@debian.org> | Debian, because code matters more Debian & GNU/Linux Developer | <http://www.debian.org> Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
