| 2007-04-22 09:41:32 |
Steve |
description |
bitlbee can be started either from inetd (default) or as a stand-alone daemon (marked upstream as experimental).
It ships in feisty configured to start from inetd, yet - unlike the version shipped with edgy - it does not depend on netkit-inetd: compare http://packages.ubuntu.com/feisty/net/bitlbee with http://packages.ubuntu.com/edgy/net/bitlbee .
This means that after an apt-get dist-upgrade, followed by an apt-get autoremove bitlbee is broken and doesn't start. |
bitlbee can be started either from inetd (default) or as a stand-alone daemon (marked upstream as experimental).
It ships in feisty configured to start from inetd, yet - unlike the version shipped with edgy - it does not depend on netkit-inetd: compare http://packages.ubuntu.com/feisty/net/bitlbee with http://packages.ubuntu.com/edgy/net/bitlbee. Nor does it ship with an init script.
This means that after an apt-get dist-upgrade, followed by an apt-get autoremove bitlbee is broken and doesn't start. |
|
