bad upgrade from talkd to ktalkd ... whose bug?
If you have talkd installed, then apt-get install ktalkd, ktalkd
conflicts with talkd, so it gets uninstalled, but not purged. i.e. the
lines in inetd.conf are still there. Then ktalkd postinst greps
inetd.conf for ^talkd, finds that there is already a line with talkd,
and doesn't install its own line. Voilá, you got no talkd.
So the question is how to solve this kind of thing neatly? Should talkd
and ktalkd remove its lines when you remove but not purge them? Or
should e.g. ktalkd do extra checking or be more eager in installing
lines in inetd.conf?
<crazy>I guess maybe one would want some neater interface to all this
inetd.conf stuff? Some debconf thingy? A bit like the nice debconf
question asking whether one wants wdm, xdm, kdm or gdm to be the display
manager? That is implemented with init.d scripts checking
"default-display-manager" file though, this will have to work quite
differently. But for mere talkd, this whole interactive idea is a bit
overkill.</crazy>
Hugo van der Merwe
Reply to: