Your message dated Wed, 19 Nov 2014 12:03:01 +0100 with message-id <[email protected]> and subject line Re: Bug#770164: php5: /usr/lib/php5/sessionclean broken: passes incompatible argument to sed has caused the Debian Bug report #770164, regarding php5-common: sessionclean scripts now always fails on Wheezy because "sed: invalid option -- 'z'" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 770164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770164 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: php5-common Version: 5.4.35-0+deb7u1 Severity: important Dear Maintainer, Since last night unattended-upgrade, sessionclean is broken on Wheezy with standard repositories. Shown in /var/log/apt/history.log : Start-Date: 2014-11-19 06:50:06 Upgrade: libapache2-mod-php5:amd64 (5.4.34-0+deb7u1, 5.4.35-0+deb7u1), php5-gd:amd64 (5.4.34-0+deb7u1, 5.4.35-0+deb7u1), php5-cli:amd64 (5.4.34-0+deb7u1, 5.4.35-0+deb7u1), php5-common:amd64 (5.4.34-0+deb7u1, 5.4.35-0+deb7u1) End-Date: 2014-11-19 06:50:28 Since that upgrade, I receive a cron error mail like : Subject: Cron <root@piou> [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime) sed : option invalide -- 'z' Utilisation: sed [OPTION]... {script-seulement-si-pas-d'autre-script} [fichier-d'entrée]... In php5-common, the script /usr/lib/php5/maxlifetime try to use "sed -z" but this option seems unsupported in : ii sed 4.2.1-10 amd64 The GNU sed stream editor My sources.list : root@piou:/var/log/apt# cat /etc/apt/sources.list deb http://ftp.fr.debian.org/debian/ wheezy main deb-src http://ftp.fr.debian.org/debian/ wheezy main deb http://security.debian.org/ wheezy/updates main contrib deb-src http://security.debian.org/ wheezy/updates main contrib # wheezy-updates, previously known as 'volatile' deb http://ftp.fr.debian.org/debian/ wheezy-updates main contrib deb-src http://ftp.fr.debian.org/debian/ wheezy-updates main contrib My unattended-upgrade config : root@piou:/etc/apt/apt.conf.d# grep -vE '^(//|$)' 50unattended-upgrades Unattended-Upgrade::Origins-Pattern { // Archive or Suite based matching: // Note that this will silently match a different release after // migration to the specified archive (e.g. testing becomes the // new stable). "o=Debian,a=stable"; "o=Debian,a=stable-updates"; "origin=Debian,archive=stable,label=Debian-Security"; }; Unattended-Upgrade::Package-Blacklist { }; Unattended-Upgrade::Mail "root"; Unattended-Upgrade::Remove-Unused-Dependencies "false"; -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---Version: 5.4.35-0+deb7u2 This was fixed in a DSA regression update.
--- End Message ---
