From c325f4a207bf2eee04de93719924f682f5a9d817 Mon Sep 17 00:00:00 2001 From: Didier Raboud Date: Thu, 23 Oct 2014 22:06:18 +0200 Subject: cups 1.7.5-7 Debian release. --- debian/changelog | 18 ++++++++++++++++++ debian/cups-daemon.NEWS | 4 ++-- 2 files changed, 20 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index 1a7c9df6..57694223 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,21 @@ +cups (1.7.5-7) unstable; urgency=medium + + * Revert to not socket-activating CUPS (Closes: #747073) + - Drop patch to let CUPS write the systemd.socket configuration files + - Replace preinst generation of the same configuration file, delete them on + upgrade + - Drop the symlink enforcing the automatic configuration + - Update NEWS and README.Debian to reflect that change + - Create two cups socket configuration examples, document their existence + in README.Debian + - Update the systemd socket activation patch to include + PassCredentials=true in the socket configuration, following upstream's + feedback + - Disable automatic idle exit timeout under systemd, as this will get + activated without socket activation + + -- Didier Raboud Thu, 23 Oct 2014 22:06:18 +0200 + cups (1.7.5-6) unstable; urgency=medium * Backport several upstream patches: diff --git a/debian/cups-daemon.NEWS b/debian/cups-daemon.NEWS index 4a3750cc..6f7794e2 100644 --- a/debian/cups-daemon.NEWS +++ b/debian/cups-daemon.NEWS @@ -1,8 +1,8 @@ -cups (1.7.5-6+) UNRELEASED; urgency=medium +cups (1.7.5-7) unstable; urgency=medium CUPS can now be socket-activated when running under systemd as init, but isn't by default; if configured to do so, it can automatically exit itself after being idle for some time (30 seconds by default) by using the 'SystemdIdleExit on' stanza in /etc/cups/cupsd.conf. - -- Didier Raboud Wed, 12 Mar 2014 12:03:14 +0100 + -- Didier Raboud Thu, 23 Oct 2014 22:06:18 +0200 -- cgit v1.2.3