Bug#1073075: policyd-rate-limit: Update to v1.2.0. Current version incompatible with Python and needs update
Package: policyd-rate-limit Version: 1.0.1.1-2.1 Severity: normal Dear Maintainer, Starting the application with the current Debian-supplied Python version results in a failure to start at all and exits with a failure. The report logged by systemd is: config.setup() File "/usr/lib/python3/dist-packages/policyd_rate_limit/utils.py", line 144, in setup self._config = Config(config_file) ^^^ File "/usr/lib/python3/dist-packages/policyd_rate_limit/utils.py", line 88, in __init__ self._config = yaml.load(f, loader=FullLoader) ^^ NameError: name 'FullLoader' is not defined policyd-rate-limit.service: Main process exited, code=exited, status=1/FAILURE policyd-rate-limit.service: Failed with result 'exit-code'. This is fixed by 88c88 < self._config = yaml.load(f) --- > self._config = yaml.load(f, Loader=yaml.SafeLoader) to the file /usr/lib/python3/dist-packages/policyd_rate_limit/utils.py This was previously reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022034 in 2022 and not fixed. This is fixed in the source repository 3 years ago via commit: https://github.com/nitmir/policyd-rate-limit/commit/6c155a633bf5e9986304b1ca009a4716846e66f9 Ultimately, this and other changes are updated in v1.2.0 which was released August 27 2023 https://github.com/nitmir/policyd-rate-limit/releases/tag/v1.2.0 This package should be updated to v1.2.0 for trixie. -- System Information: Debian Release: 12.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages policyd-rate-limit depends on: ii adduser 3.134 ii init-system-helpers 1.65.2 ii python3 3.11.2-1+b1 ii python3-yaml 6.0-3+b2 policyd-rate-limit recommends no packages. Versions of packages policyd-rate-limit suggests: ii python3-mysqldb 1.4.6-2+b1 pn python3-psycopg2 -- Configuration Files: /etc/policyd-rate-limit.yaml [Errno 13] Permission denied: '/etc/policyd-rate-limit.yaml' -- no debconf information
Bug#990008: linux-image-5.10.0-7-amd64: e1000e driver fails to load after upgrade to bullseye from buster
Package: src:linux Version: 5.10.40-1 Severity: important Dear Maintainer, Running Debian on a Lenovo ThinkCentre M90n system. It's a common all-in-one stock system. This system was running perfectly on Debain buster, however on the upgrade to bullseye, lacks all network functionality. Previously, the e1000e driver would load as follows: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k e1000e: Copyright(c) 1999 - 2015 Intel Corporation. e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode e1000e :00:1f.6 :00:1f.6 (uninitialized): registered PHC clock e1000e :00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 98:fa:9b:70:3b:52 e1000e :00:1f.6 eth0: Intel(R) PRO/1000 Network Connection e1000e :00:1f.6 eth0: MAC: 13, PHY: 12, PBA No: FF-0FF e1000e :00:1f.6 eno2: renamed from eth0 e1000e: eno2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Now the e1000e driver seems the following: e1000e: Intel(R) PRO/1000 Network Driver e1000e: Copyright(c) 1999 - 2015 Intel Corporation. e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode e1000e :00:1f.6 :00:1f.6 (uninitialized): Failed to disable ULP e1000e: probe of :00:1f.6 failed with error -2 No other changes to the system took place other than the upgrade to bullseye. Concerning since I assume others will experience this upgrade challenge. Network controller works fine with Windows or if going back to 4.19 for testing. -- Package-specific info: ** Version: Linux version 5.10.0-7-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.40-1 (2021-05-28) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-7-amd64 root=UUID=b49cd91a-b8ea-424f-a6f0-3a80621652ff ro quiet ** Not tainted ** Kernel log: [5.972985] NET: Registered protocol family 38 [5.993961] Bluetooth: RFCOMM TTY layer initialized [5.993969] Bluetooth: RFCOMM socket layer initialized [5.993975] Bluetooth: RFCOMM ver 1.11 [6.940483] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [7.161973] rfkill: input handler disabled [8.665113] FS-Cache: Loaded [8.697699] FS-Cache: Netfs 'nfs' registered for caching [8.699966] Key type dns_resolver registered [8.778065] kauditd_printk_skb: 8 callbacks suppressed [8.778066] audit: type=1400 audit(1623941140.775:19): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=1122 comm="apparmor_parser" [8.843335] NFS: Registering the id_resolver key type [8.843342] Key type id_resolver registered [8.843343] Key type id_legacy registered [9.361898] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [9.363214] Bridge firewalling registered [9.395338] Initializing XFRM netlink socket [9.687026] br-f5d44323feea: port 1(vethda7e498) entered blocking state [9.687030] br-f5d44323feea: port 1(vethda7e498) entered disabled state [9.687340] device vethda7e498 entered promiscuous mode [9.691158] br-f5d44323feea: port 1(vethda7e498) entered blocking state [9.691162] br-f5d44323feea: port 1(vethda7e498) entered forwarding state [9.691213] IPv6: ADDRCONF(NETDEV_CHANGE): br-f5d44323feea: link becomes ready [9.691330] br-f5d44323feea: port 1(vethda7e498) entered disabled state [9.728132] br-f5d44323feea: port 2(veth7bfadb3) entered blocking state [9.728136] br-f5d44323feea: port 2(veth7bfadb3) entered disabled state [9.728418] device veth7bfadb3 entered promiscuous mode [9.734020] br-f5d44323feea: port 2(veth7bfadb3) entered blocking state [9.734023] br-f5d44323feea: port 2(veth7bfadb3) entered forwarding state [ 10.149671] eth0: renamed from veth98f4f77 [ 10.209455] eth0: renamed from veth51e2bf6 [ 10.229203] IPv6: ADDRCONF(NETDEV_CHANGE): veth7bfadb3: link becomes ready [ 10.229690] IPv6: ADDRCONF(NETDEV_CHANGE): vethda7e498: link becomes ready [ 10.229724] br-f5d44323feea: port 1(vethda7e498) entered blocking state [ 10.229726] br-f5d44323feea: port 1(vethda7e498) entered forwarding state [ 26.785343] rfkill: input handler enabled [ 28.238953] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 28.496041] rfkill: input handler disabled [ 95.503702] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 ** Model information sys_vendor: LENOVO product_name: 11ADS0E600 product_version: ThinkCentre M90n-1 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: M2AKT29A board_vendor: LENOVO board_name: 314D board_version: SDK0J40697 WIN 3305310468669 ** Loaded modules: ctr ccm xt_nat veth nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink xfrm_user xfrm_algo br_netfilter bridge stp
Bug#941986: mariadb-client-10.3: InnoTop crashes during use
Package: mariadb-client-10.3
Version: 1:10.3.17-0+deb10u1
Severity: important
Dear Maintainer,
On running `innotop`, it appears to work correctly, however upon choosing one
of the other screens, such as pushing "L" to bring up the lock screen, it
crashes with the error:
Use of uninitialized value $text in pattern match (m//) at
/tmp/innotop.orig line 620.
This is because technically 10.3 is not officially supported by innotop, and so
it uses old legacy code which returns incorrect results.
While innotop doesn't get support 10.3, us shipping innotop with MariaDB 10.3
means it should really work with it. It is substantially close to 10.1/10.2 to
include it in the ways that works as opposed to using outdated code meant for
older versions of MySQL.
Ideally, innotop should be updated to include official 10.3 support. Until the
developer does that, this will at least make innotop usable on Debian Buster 10.
-- System Information:
Debian Release: 10.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mariadb-client-10.3 depends on:
ii debianutils 4.8.6.1
ii libc6 2.28-10
ii libconfig-inifiles-perl 3.01-1
ii libgnutls30 3.6.7-4
ii libstdc++68.3.0-6
ii mariadb-client-core-10.3 1:10.3.17-0+deb10u1
ii perl 5.28.1-6
ii zlib1g1:1.2.11.dfsg-1
Versions of packages mariadb-client-10.3 recommends:
ii libdbd-mysql-perl 4.050-2
ii libdbi-perl 1.642-1+b1
ii libterm-readkey-perl 2.38-1
mariadb-client-10.3 suggests no packages.
-- no debconf information
--- /tmp/innotop.orig 2019-10-08 11:17:31.446038258 -0400
+++ /usr/bin/innotop2019-10-08 11:21:57.258023170 -0400
@@ -471,7 +471,7 @@
# too many locks to print, the output might be truncated)
my $time_text;
- if ( ($mysqlversion =~ /^5\.[67]\./) || ($mysqlversion =~ /^10\.[012]\./) )
{
+ if ( ($mysqlversion =~ /^5\.[67]\./) || ($mysqlversion =~ /^10\.[0123]\./)
) {
( $time_text ) = $fulltext =~ m/^([0-9-]* [0-9:]*) [0-9a-fx]* INNODB
MONITOR OUTPUT/m;
$innodb_data{'ts'} = [ parse_innodb_timestamp_56( $time_text ) ];
} else {
@@ -639,7 +639,7 @@
return 0 unless $fulltext;
my ( $ts, $type );
- if ( ($mysqlversion =~ /^5.[67]\./) || ($mysqlversion =~ /^10.[012]\./) ) {
+ if ( ($mysqlversion =~ /^5.[67]\./) || ($mysqlversion =~ /^10.[0123]\./) ) {
( $ts, $type ) = $fulltext =~ m/^([0-9-]* [0-9:]*)\s[0-9a-fx]*\s+(\w+)/m;
$section->{'ts'} = [ parse_innodb_timestamp_56( $ts ) ];
} else {
@@ -899,7 +899,7 @@
my ( $ts ) = $fulltext =~ m/^$s$/m;
return 0 unless $ts;
- if ( ($mysqlversion =~ /^5\.[67]\./) || ($mysqlversion =~ /^10\.[012]\./) )
{
+ if ( ($mysqlversion =~ /^5\.[67]\./) || ($mysqlversion =~ /^10\.[0123]\./)
) {
$dl->{'ts'} = [ parse_innodb_timestamp_56( $ts ) ];
}
else {
Bug#927150: spamassassin: awl sql file is missing field, causing error message on each INSERT
Package: spamassassin Version: 3.4.2-1 Severity: normal Dear Maintainer, The last_hit timestamp is missing on the the awl table (similar to the txref table) since 3.4.1 last_hit timestamp NOT NULL default CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP This should be updated in /usr/share/doc/spamassassin/sql for both postgresql/mysql. An upgrade note should also be raised to alter the schema on upgrades (or if it doesn't exist) See: https://svn.apache.org/viewvc?view=revision=1844485 for patches. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages spamassassin depends on: ii adduser3.118 ii curl 7.64.0-2 ii init-system-helpers1.56+nmu1 pn libarchive-tar-perl ii libhtml-parser-perl3.72-3+b3 ii libhttp-date-perl 6.02-1 ii libmail-dkim-perl 0.54-1 ii libnet-dns-perl1.19-1 ii libnetaddr-ip-perl 4.079+dfsg-1+b3 ii libsocket6-perl0.29-1+b1 ii libsys-hostname-long-perl 1.5-1 ii lsb-base 10.2019031300 ii perl 5.28.1-6 Versions of packages spamassassin recommends: ii gnupg2.2.12-1 ii libio-socket-inet6-perl 2.72-2 ii libmail-spf-perl 2.9.0-4 pn libsys-syslog-perl ii sa-compile 3.4.2-1 ii spamc3.4.2-1 Versions of packages spamassassin suggests: pn libcompress-zlib-perl ii libdbi-perl1.642-1+b1 pn libencode-detect-perl ii libgeo-ip-perl 1.51-1+b1 ii libio-socket-ssl-perl 2.060-3 ii libnet-patricia-perl 1.22-1+b5 ii pyzor 1:1.0.0-3 ii razor 1:2.85-4.2+b5 -- Configuration Files: /etc/default/spamassassin changed [not included] /etc/spamassassin/init.pre changed [not included] /etc/spamassassin/local.cf changed [not included] /etc/spamassassin/v310.pre changed [not included] /etc/spamassassin/v341.pre changed [not included] /etc/spamassassin/v342.pre changed [not included] -- no debconf information
Bug#927017: mailgraph: Image directory does not exist, resulting in errors and no graphs
Package: mailgraph Version: 1.14-17 Severity: important Dear Maintainer, On a new (configured) installation, visiting the page results in this error in the apache error log and broken images ERROR: Could not save png to '/var/lib/mailgraph/,mailgraph/mailgraph_3_grey.png' End of script output before headers: mailgraph.cgi, referer: http://.../mailgraph/mailgraph.cgi Fix: mkdir /var/lib/mailgraph/,mailgraph/ chown www-data:www-data /var/lib/mailgraph/,mailgraph/ the mkdir $tmp_dir/$uri/ on line 252 of mailgraph.cgi won't work due to lack of permissions on /var/lib/mailgraph to the www-data user. Of course, ideally the files should just go into /var/lib/mailgraph, so this might point to either: - a bug in the application which could get it to use /var/lib/mailgraph - simply a missing directory which should be created and permissions to www-data assigned on install - permissions to www-data on /var/lib/mailgraph to create its sub-folder - a documentation error that such a directory must be created (and how to derrive it from the path) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mailgraph depends on: ii debconf [debconf-2.0] 1.5.71 ii libfile-tail-perl 1.3-5 ii librrds-perl 1.7.1-1 ii lsb-base 10.2019031300 ii perl 5.28.1-6 ii ucf3.0038+nmu1 Versions of packages mailgraph recommends: ii apache2 [httpd] 2.4.38-3 ii postfix [mail-transport-agent] 3.4.5-1 mailgraph suggests no packages. -- debconf information: * mailgraph/mail_log: /var/log/mail.log * mailgraph/start_on_boot: true * mailgraph/ignore_localhost: true
Bug#926473: amavisd-new: Dependency on non-existing ZeroMQ Perl library
Package: amavisd-new Version: 1:2.11.0-6 Severity: normal amavisd-status does not work, depending on ZeroMQ which is no longer in Debian See https://bugs.debian.org/824905 # amavisd-status Perl modules ZMQ::LibZMQ3 or ZMQ::LibZMQ2 or ZeroMQ not available BEGIN failed--compilation aborted at /usr/sbin/amavisd-status line 110. This was previously reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801852 however in taht case it was to recommend making it a depend/recommend. In this case, it is reporting the broken functionality as a result of that. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages amavisd-new depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii file 1:5.35-4 ii init-system-helpers1.56+nmu1 pn libarchive-tar-perl ii libarchive-zip-perl1.64-1 ii libberkeleydb-perl 0.55-2 ii libconvert-tnef-perl 0.18-1 ii libconvert-uulib-perl 1:1.5~dfsg-1+b1 pn libdigest-md5-perl ii libio-stringy-perl 2.111-3 ii libmail-dkim-perl 0.54-1 ii libmailtools-perl 2.18-1 pn libmime-base64-perl ii libmime-tools-perl 5.509-1 ii libnet-libidn-perl 0.12.ds-3+b1 ii libnet-server-perl 2.009-1 pn libtime-hires-perl ii libunix-syslog-perl1.1-3+b1 ii lsb-base 10.2019031300 ii pax1:20190224-1 ii perl 5.28.1-6 Versions of packages amavisd-new recommends: ii altermime 0.3.10-9 ii libnet-patricia-perl 1.22-1+b5 pn ripole Versions of packages amavisd-new suggests: ii apt-listchanges 3.19 ii arj 3.10.22-18 ii cabextract 1.9-1 ii clamav 0.101.2+dfsg-1 ii clamav-daemon0.101.2+dfsg-1 ii cpio 2.12+dfsg-6 pn dspam pn lhasa ii libauthen-sasl-perl 2.1600-1 ii libdbi-perl 1.642-1+b1 ii libmail-dkim-perl0.54-1 pn libnet-ldap-perl pn libsnmp-perl pn libzeromq-perl pn lzop ii nomarch 1.4-3+b2 pn p7zip pn rpm ii spamassassin 3.4.2-1 pn unrar -- no debconf information
Bug#926449: postfix: preconfig does not ensure /sbin and /usr/sbin is in $PATH
Package: postfix Version: 3.4.5-1 Severity: normal Upgrading from 3.4.4 to 3.4.5-1, I see the following messages after a 'su' to root Preconfiguring packages ... Can't exec "postconf": No such file or directory at /tmp/postfix.config.swGX60 line 220, line 14. Can't exec "postconf": No such file or directory at /tmp/postfix.config.swGX60 line 284, line 16. Can't exec "postconf": No such file or directory at /tmp/postfix.config.swGX60 line 386, line 21. It most certainly relates to the news article at https://sources.debian.org/src/util-linux/2.33.1-0.1/debian/util-linux.NEWS/ however, that is no reason for the postfix preconfig to fail (and who knows what change I missed there) The script should err on the side of caution, knowing full-well where postconf is and that it is required, and add /usr/sbin and /sbin to the PATH in the scripts. Right now it (potentially) fails to do what it is supposed to do with a $PATH it can't control. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages postfix depends on: ii adduser3.118 ii cpio 2.12+dfsg-6 ii debconf [debconf-2.0] 1.5.71 ii dpkg 1.19.6 ii e2fsprogs 1.44.5-1 ii libc6 2.28-8 ii libdb5.3 5.3.28+dfsg1-0.5 ii libicu63 63.1-6 ii libsasl2-2 2.1.27+dfsg-1 ii libssl1.1 1.1.1b-1 ii lsb-base 10.2019031300 ii netbase5.6 ii ssl-cert 1.0.39 Versions of packages postfix recommends: ii python3 3.7.2-1 Versions of packages postfix suggests: ii dovecot-core [dovecot-common] 1:2.3.4.1-3 ii libsasl2-modules 2.1.27+dfsg-1 ii mailutils [mail-reader]1:3.5-3 pn postfix-cdb pn postfix-doc pn postfix-ldap pn postfix-lmdb ii postfix-mysql 3.4.5-1 pn postfix-pcre pn postfix-pgsql pn postfix-sqlite pn procmail pn resolvconf ii ufw0.36-1 -- debconf information excluded
Bug#926354: postfixadmin: Missing symbolic link to config.local.php results in warning message during setup
Package: postfixadmin Version: 3.2.1-2 Severity: minor When using /postfixadmin/setup.php, a warning is provided as follows: Warning: config.local.php - NOT FOUND It's Recommended to store your own settings in config.local.php instead of editing config.inc.php Create the file, and edit as appropriate (e.g. select database type etc) To fix, ln -s /etc/postfixadmin/config.local.php /usr/share/postfixadmin/config.local.php is appropriate (the same way config.inc.php is linked) on installation -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages postfixadmin depends on: ii apache2 [httpd] 2.4.38-2 ii dbconfig-common 2.0.11 ii debconf 1.5.71 ii default-mysql-client1.0.5 ii php 2:7.3+69 ii php-fpm 2:7.3+69 ii php-imap2:7.3+69 ii php-mbstring2:7.3+69 ii php-mysql 2:7.3+69 ii php7.3 [php]7.3.3-1 ii php7.3-fpm [php-fpm]7.3.3-1 ii php7.3-imap [php-imap] 7.3.3-1 ii php7.3-mbstring [php-mbstring] 7.3.3-1 ii php7.3-mysql [php-mysqlnd] 7.3.3-1 ii wwwconfig-common0.3.0 Versions of packages postfixadmin recommends: ii dovecot-core1:2.3.4.1-3 ii mariadb-server 1:10.3.13-1 ii mariadb-server-10.3 [virtual-mysql-server] 1:10.3.13-1 ii php7.3-cli [php-cli]7.3.3-1 ii postfix-mysql 3.4.4-1 pn zendframework postfixadmin suggests no packages. -- Configuration Files: /etc/apache2/conf-available/postfixadmin.conf changed [not included] -- debconf information excluded
Bug#857791: postfixadmin & dbconfig-common: mysql/mysqli mismatch
Package: postfixadmin Version: 3.2.1-2 Followup-For: Bug #857791 This bug remains in the current buster release. As PHP 5.x and MySQL (not MySQLi) is fully depreciated there is no need for even the patch in question. Very simply, this should just have mysqli as the database engine and nothing more. 1. It may be doable with just dbconfig-common's scripts in this package 2. otherwise a simple sed 3. or including this at the bottom of the file: if ($dbtype=='mysql') $dbtype='mysqli'; -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages postfixadmin depends on: ii apache2 [httpd] 2.4.38-2 ii dbconfig-common 2.0.11 ii debconf 1.5.71 ii default-mysql-client1.0.5 ii php 2:7.3+69 ii php-fpm 2:7.3+69 ii php-imap2:7.3+69 ii php-mbstring2:7.3+69 ii php-mysql 2:7.3+69 ii php7.3 [php]7.3.3-1 ii php7.3-fpm [php-fpm]7.3.3-1 ii php7.3-imap [php-imap] 7.3.3-1 ii php7.3-mbstring [php-mbstring] 7.3.3-1 ii php7.3-mysql [php-mysqlnd] 7.3.3-1 ii wwwconfig-common0.3.0 Versions of packages postfixadmin recommends: ii dovecot-core1:2.3.4.1-3 ii mariadb-server 1:10.3.13-1 ii mariadb-server-10.3 [virtual-mysql-server] 1:10.3.13-1 ii php7.3-cli [php-cli]7.3.3-1 ii postfix-mysql 3.4.4-1 pn zendframework postfixadmin suggests no packages. -- Configuration Files: /etc/apache2/conf-available/postfixadmin.conf changed [not included] -- debconf information excluded
Bug#926253: postfixadmin: /usr/share/postfixadmin/lib/../templates_c does not exist on new installation
Package: postfixadmin Version: 3.2.1-2 Severity: important On a new installation of postfixadmin in Buster, /usr/share/postfixadmin/lib/../templates_c (the compiled template folder) is not created. As such, the following error appears and nothing works: AH01071: Got error 'PHP message: ERROR: directory /usr/share/postfixadmin/lib/../templates_c doesn't exist or isn't writeable for the webserver' A simple: mkdir -p /usr/share/postfixadmin/lib/../templates_c chown www-data /usr/share/postfixadmin/lib/../templates_c -R chmod 700 /usr/share/postfixadmin/lib/../templates_c results in postfixadmin working correctly by creating the folder and appropriately sets permissions for the folder for use by web servers. This should be propertly created and permissions set if it does not exist on an installation. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages postfixadmin depends on: ii apache2 [httpd] 2.4.38-2 ii dbconfig-common 2.0.11 ii debconf 1.5.71 ii default-mysql-client1.0.5 ii php 2:7.3+69 ii php-fpm 2:7.3+69 ii php-imap2:7.3+69 ii php-mbstring2:7.3+69 ii php-mysql 2:7.3+69 ii php7.3 [php]7.3.3-1 ii php7.3-fpm [php-fpm]7.3.3-1 ii php7.3-imap [php-imap] 7.3.3-1 ii php7.3-mbstring [php-mbstring] 7.3.3-1 ii php7.3-mysql [php-mysqlnd] 7.3.3-1 ii wwwconfig-common0.3.0 Versions of packages postfixadmin recommends: ii dovecot-core1:2.3.4.1-3 ii mariadb-server 1:10.3.13-1 ii mariadb-server-10.3 [virtual-mysql-server] 1:10.3.13-1 ii php7.3-cli [php-cli]7.3.3-1 ii postfix-mysql 3.4.4-1 pn zendframework postfixadmin suggests no packages. -- Configuration Files: /etc/apache2/conf-available/postfixadmin.conf changed [not included] -- debconf information excluded
Bug#926252: postfixadmin: apache2 configuration does not point to public folder
Package: postfixadmin Version: 3.2.1-2 Severity: important Tags: patch File /etc/apache2/conf-available/postfixadmin.conf refers to Alias /postfixadmin /usr/share/postfixadmin /usr/share/doc/postfixadmin/README.Debain incorrectly suggests that After installing the package, you should find that : http://youserver/postfixadmin/setup.php works. This is inconsistent. /etc/apache2/conf-available/postfixadmin.conf should refer to /usr/share/postfixadmin/public PATCH --- /etc/apache2/conf-enabled/postfixadmin.conf.bak 2019-04-02 13:04:03.282829696 -0400 +++ /etc/apache2/conf-enabled/postfixadmin.conf 2019-04-02 13:04:16.671144465 -0400 @@ -1,5 +1,5 @@ # BEGIN FOR POSTFIXADMIN -Alias /postfixadmin /usr/share/postfixadmin +Alias /postfixadmin /usr/share/postfixadmin/public # END FOR POSTFIXADMIN -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages postfixadmin depends on: ii apache2 [httpd] 2.4.38-2 ii dbconfig-common 2.0.11 ii debconf 1.5.71 ii default-mysql-client1.0.5 ii php 2:7.3+69 ii php-fpm 2:7.3+69 ii php-imap2:7.3+69 ii php-mbstring2:7.3+69 ii php-mysql 2:7.3+69 ii php7.3 [php]7.3.3-1 ii php7.3-fpm [php-fpm]7.3.3-1 ii php7.3-imap [php-imap] 7.3.3-1 ii php7.3-mbstring [php-mbstring] 7.3.3-1 ii php7.3-mysql [php-mysqlnd] 7.3.3-1 ii wwwconfig-common0.3.0 Versions of packages postfixadmin recommends: ii dovecot-core1:2.3.4.1-3 ii mariadb-server 1:10.3.13-1 ii mariadb-server-10.3 [virtual-mysql-server] 1:10.3.13-1 ii php7.3-cli [php-cli]7.3.3-1 ii postfix-mysql 3.4.4-1 pn zendframework postfixadmin suggests no packages. -- debconf information excluded --- /etc/apache2/conf-enabled/postfixadmin.conf.bak 2019-04-02 13:04:03.282829696 -0400 +++ /etc/apache2/conf-enabled/postfixadmin.conf 2019-04-02 13:04:16.671144465 -0400 @@ -1,5 +1,5 @@ # BEGIN FOR POSTFIXADMIN -Alias /postfixadmin /usr/share/postfixadmin +Alias /postfixadmin /usr/share/postfixadmin/public # END FOR POSTFIXADMIN
Bug#554029: proftpd-basic: proftpd silently fails when inetd isn't installed and is installed in inetd mode
Package: proftpd-basic Version: 1.3.1-17lenny2 Severity: normal When installing proftpd, the user is prompted for standalone or inetd mode. If inetd mode is chosen, no check is made for inetd being present. Accordingly, a failed grep happens and the package appears to install fine, however is not configured or enabled as a result of the inability to install it into an inetd mode. The correct response should be that the check is made for the inetd-superserver virtual package and a note stating that it can't be installed in inetd mode, forcing it in standalone mode. It can not be depended on as a package, or it will require an unnecessary dependancy in standalone mode. This check is missing and unfortunately the package silently fails and of course doesn't start. Installing inetd after the fact will likely result in a missing entry and need to reconfigure proftpd. -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages proftpd-basic depends on: ii adduser 3.110add and remove users and groups ii debconf 1.5.24 Debian configuration management sy ii debianutils 2.30 Miscellaneous utilities specific t ii libacl1 2.2.47-2 Access control list shared library ii libattr11:2.4.43-2 Extended attribute shared library ii libc6 2.7-18 GNU C Library: Shared libraries ii libcap1 1:1.10-14support for getting/setting POSIX. ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii libpam-runtime 1.0.1-5+lenny1 Runtime support for the PAM librar ii libpam0g1.0.1-5+lenny1 Pluggable Authentication Modules l ii libssl0.9.8 0.9.8g-15+lenny5 SSL shared libraries ii libwrap07.6.q-16 Wietse Venema's TCP wrappers libra ii netbase 4.34 Basic TCP/IP networking system ii sed 4.1.5-6 The GNU sed stream editor ii ucf 3.0016 Update Configuration File: preserv ii update-inetd4.31 inetd configuration file updater proftpd-basic recommends no packages. Versions of packages proftpd-basic suggests: ii openssl 0.9.8g-15+lenny5 Secure Socket Layer (SSL) binary a ii proftpd-doc 1.3.1-17lenny4 Versatile, virtual-hosting FTP dae ii proftpd-mod-ldap1.3.1-17lenny2 versatile, virtual-hosting FTP dae ii proftpd-mod-mysql 1.3.1-17lenny2 versatile, virtual-hosting FTP dae ii proftpd-mod-pgsql 1.3.1-17lenny2 versatile, virtual-hosting FTP dae -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#438429: aide uses invalid command
Package: aide Version: 1.13.1-02 When the aide cron script runs, it produces the following output: # /etc/cron.daily/aide /etc/cron.daily/aide: line 117: onexit: command not found /etc/cron.daily/aide: line 61: onexit: command not found onexit does not appear to be a valid bash command. Using the latest Debian Etch -M -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
