Hi intrigeri,
On Dienstag, 20. November 2012, intrigeri wrote:
> However, I don't think it is acceptable to apply these permissions (on
> a directory shipped by the package) unconditionally at configure time,
> the way the proposed patch does it: e.g. it changes the state of
> dpkg -managed files behind its feet, and it prevents the administrator
> from using dpkg-statoverride. Hence, I'm removing the "patch"
> tag. Sorry.
>
> I think a better way to fix this bug would be to fix the package (and
> possibly upstream) build system so that this directory is created with
> the correct owner by dpkg itself.
this cannot work, the munin-async user and group is created by the packages
postinst, so
I've enhanced Daniel's commit by this one (which is similar to what is done in
munin.postinst):
git show 7f380151c3e7279681eec1eb27024b41d604d44d
Essentially this is:
diff --git a/debian/munin-async.postinst b/debian/munin-async.postinst
index 6cbab88..dc171bb 100644
--- a/debian/munin-async.postinst
+++ b/debian/munin-async.postinst
@@ -22,7 +22,10 @@ initperms() {
case "$1" in
configure)
add_munin_async_user
- initperms
+ # this can go away after wheezy
+ if dpkg --compare-versions "$2" le "2.0.6-1~" || [ "$2" = 0 ] ;
then
+ initperms
+ fi
;;
abort-upgrade|abort-deconfigure|abort-remove)
cheers,
Holger
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
