Public bug reported: 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. ** Affects: bitlbee (Ubuntu) Importance: Undecided Status: Unconfirmed ** Summary changed: - bitlbee fails to start in feisty + bitlbee fails to start in feisty (netkit-inetd depend gone awol) ** Description changed: 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 . + 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. -- bitlbee fails to start in feisty (netkit-inetd depend gone awol) https://bugs.launchpad.net/bugs/108855 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
