Package: bitlbee-libpurple Version: 3.5.1-1 Severity: important Dear Maintainer,
After a resent bitlbee-libpurple update, and a restart of my VPS, I found that my /etc/bitlbee/bitlbee.conf's DaemonPort setting was not being honored, and that bitlbee was defaulting to 6667. Upon investigation, I found that the /etc/systemd/system/sockets.target.wants/bitlbee.socket is what systemd was choosing to honor. After editing bitlbee.socket's ListenStream and restarting with systemctl it was now on the correct port again. Ideally I think the bitlbee.conf should be honored... but maybe we should add content to the bitlbee(8) man page if this is going to be the new norm? Thank you for your time. -demure -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.7-x86_64-linode80 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bitlbee-libpurple depends on: ii bitlbee-common 3.5.1-1 ii debianutils 4.8.1 ii libc6 2.24-9 ii libgcrypt20 1.7.6-1 ii libglib2.0-0 2.50.3-1 ii libgnutls30 3.5.8-3 ii libpurple0 2.11.0-3 bitlbee-libpurple recommends no packages. bitlbee-libpurple suggests no packages. -- no debconf information
