Bug#1024443: asterisk-modules no longer includes chan_sip which breaks existing configs

2022-11-19 Thread james.bottom...@hansenpartnership.com
Package: asterisk-modules Version: 1:20.0.0~dfsg+~cs6.12.40431414-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: james.bottom...@hansenpartnership.com The package asterisk-module no longer contains chan_sip.so which means that all existing SIP configuration with chan_sip

Bug#958830: php-apcu: upgrade to php-apcu 5.1.17->18 breaks nextcloud

2020-04-25 Thread james.bottom...@hansenpartnership.com
Package: php-apcu Version: 5.1.18+4.0.11-1+b1 Severity: grave Justification: renders package unusable After the upgrade nextcloud just gives an internal server error The problem seems to be that nextcloud is configured to use apcu as a memory cache and this version of apcu only has php7.4 files.

Bug#955247: amavisd-new: upgrade of amavis fails to start daemon

2020-03-28 Thread james.bottom...@hansenpartnership.com
Package: amavisd-new Version: 1:2.11.1-1 Severity: grave Justification: renders package unusable After upgrading to the latest amavisd-new in testing, it fails to start. This is the error from the logs Mar 28 10:22:18 bedivere amavis[3095]: (!)Net::Server: 2020/03/28-10:22:18 Couldn't open pid f

Bug#923208: libengine-pkcs11-openssl: libengines-pkcs11-openssl is installing to the wrong engine directory on x86

2019-02-24 Thread james.bottom...@hansenpartnership.com
Package: libengine-pkcs11-openssl Version: 0.4.9-3 Severity: grave Justification: renders package unusable The problem is this: bedivere:~# dpkg -L libengine-pkcs11-openssl |grep engines /usr/lib/i686-linux-gnu/engines-1.1 /usr/lib/i686-linux-gnu/engines-1.1/pkcs11.la /usr/lib/i686-linux-gnu/engi

Bug#541702: linux-image-2.6.30-1-686: Kernel fails to start networking because no e100 firmware

2009-08-15 Thread james.bottom...@hansenpartnership.com
Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: serious Justification: Policy 2.2.1 On upgrade from 2.6.30-2-686 networking (on a remote machine) failed to start, meaning that a support ticket had to be opened for KVM access. Diagnosis revealed that the e100 driver in 2.6.26-2-686 r