[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#768582: marked as done (unblock: man-db/2.7.0.2-3)

Your message dated Sat, 08 Nov 2014 14:36:58 +0000
with message-id <8f206ef25fe809b57e98645113144e27@mail.adsl.funky-badger.org>
and subject line Re: Bug#768582: unblock: man-db/2.7.0.2-3
has caused the Debian Bug report #768582,
regarding unblock: man-db/2.7.0.2-3
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 owner@bugs.debian.org
immediately.)


-- 
768582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768582
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package man-db.  I notice that openssh 1:6.7p1-3 was
already unblocked, and man-db is for the same reason: it drops obsolete
assumptions about dpkg-statoverride's path.  Even if the
/usr/sbin/dpkg-statoverride symlink is restored, I'd rather not have
this potentially cause problems during upgrades from jessie to jessie+1.

diff -Nru man-db-2.7.0.2/debian/changelog man-db-2.7.0.2/debian/changelog
--- man-db-2.7.0.2/debian/changelog	2014-10-10 14:09:07.000000000 +0100
+++ man-db-2.7.0.2/debian/changelog	2014-11-03 20:26:42.000000000 +0000
@@ -1,3 +1,11 @@
+man-db (2.7.0.2-3) unstable; urgency=medium
+
+  * Policy version 3.9.6: no changes required.
+  * Assume that dpkg-statoverride exists and drop the test for an obsolete
+    compatibility path.
+
+ -- Colin Watson <cjwatson@debian.org>  Mon, 03 Nov 2014 20:26:39 +0000
+
 man-db (2.7.0.2-2) unstable; urgency=medium
 
   * Remove /var/lib/man-db/auto-update on purge.
diff -Nru man-db-2.7.0.2/debian/control man-db-2.7.0.2/debian/control
--- man-db-2.7.0.2/debian/control	2014-09-28 00:24:26.000000000 +0100
+++ man-db-2.7.0.2/debian/control	2014-10-15 01:43:25.000000000 +0100
@@ -2,7 +2,7 @@
 Section: doc
 Priority: important
 Maintainer: Colin Watson <cjwatson@debian.org>
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
 Build-Depends: dpkg (>= 1.16.1~), debhelper (>= 9~), flex, groff, libgdbm-dev, po4a, zlib1g-dev, libpipeline-dev (>= 1.3.0), pkg-config, dh-autoreconf, autopoint
 Homepage: http://man-db.nongnu.org/
 Vcs-Git: git://anonscm.debian.org/pkg-man-db/man-db.git
diff -Nru man-db-2.7.0.2/debian/postinst man-db-2.7.0.2/debian/postinst
--- man-db-2.7.0.2/debian/postinst	2014-09-28 00:24:26.000000000 +0100
+++ man-db-2.7.0.2/debian/postinst	2014-11-03 20:25:22.000000000 +0000
@@ -52,8 +52,7 @@
 
 for x in $maybesetuid; do
     # No statoverrides available or none exist for us ...
-    if [ ! -x /usr/sbin/dpkg-statoverride ] || \
-	    ! dpkg-statoverride --list /usr/bin/$x >/dev/null; then
+    if ! dpkg-statoverride --list /usr/bin/$x >/dev/null; then
 	chown $owner /usr/bin/$x || true
 	chmod $mode  /usr/bin/$x
     fi

unblock man-db/2.7.0.2-3

Thanks,

-- 
Colin Watson                                       [cjwatson@debian.org]

--- End Message ---
--- Begin Message --- 
On 2014-11-08 14:24, Colin Watson wrote:

Please unblock package man-db.  I notice that openssh 1:6.7p1-3 was
already unblocked, and man-db is for the same reason: it drops obsolete
assumptions about dpkg-statoverride's path.  Even if the
/usr/sbin/dpkg-statoverride symlink is restored, I'd rather not have
this potentially cause problems during upgrades from jessie to jessie+1. 

Unblocked, thanks.

Regards,

Adam

--- End Message ---
Reply to: