Your message dated Wed, 10 May 2006 18:01:22 +0200 with message-id <20060510160122.GA32678@mad.intersec.fr> and subject line tagging 112512 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Kdelibs3 does not cleanup /etc/kde2/{ui,colors} on purge
- From: Philippe Troin <phil@fifi.org>
- Date: 16 Sep 2001 22:53:21 -0700
- Message-id: <8766ai1hym.fsf@ceramic.fifi.org>
Package: kdelibs3 Version: 4:2.1.2-3 On purge: Removing kdelibs3 ... dpkg - warning: while removing kdelibs3, directory `/etc/kde2/ui' not empty so not removed. dpkg - warning: while removing kdelibs3, directory `/etc/kde2/colors' not empty so not removed. dpkg - warning: while removing kdelibs3, directory `/etc/kde2' not empty so not removed. Purging configuration files for kdelibs3 ... And after purge, /etc/kde2/{ui,colors} is still there... You probably want to add [ "$1" = purge ] \ && rmdir /etc/kde2/ui /etc/kde2/colors /etc/kde2 >/dev/null 2>&1 \ || true to your postrm. Phil.
--- End Message ---
--- Begin Message ---
- To: 112512-done@bugs.debian.org
- Subject: Re: tagging 112512
- From: Pierre HABOUZIT <madcoder@debian.org>
- Date: Wed, 10 May 2006 18:01:22 +0200
- Message-id: <20060510160122.GA32678@mad.intersec.fr>
- In-reply-to: <20050923220617.E08F862113@hades.madism.org>
- References: <20050923220617.E08F862113@hades.madism.org>
Version: 4:3.3.0 On Sat, Sep 24, 2005 at 12:06:17AM +0200, Pierre Habouzit wrote: > # Automatically generated email from bts, devscripts version 2.9.7 > tags 112512 + sarge this bug affects woody => sarge upgrade. sarge is now stable, so this can't be fixed anymore in sarge, and won't affect next release. -- ·O· Pierre Habouzit ··O madcoder@debian.org OOO http://www.madism.orgAttachment: signature.asc
Description: Digital signature
--- End Message ---