Your message dated Mon, 14 Nov 2005 00:33:10 -0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in upload of gconf2 2.12.1-1 to experimental
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 26 Oct 2005 21:43:43 +0000
>From [EMAIL PROTECTED] Wed Oct 26 14:43:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from silence.lateralis.org [81.56.5.120] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EUt3f-0003rh-00; Wed, 26 Oct 2005 14:43:43 -0700
Received: from laurent by silence.lateralis.org with local (Exim 4.54)
        id 1EUt3c-0000dq-M9; Wed, 26 Oct 2005 23:43:40 +0200
Date: Wed, 26 Oct 2005 23:43:40 +0200
From: Laurent Fousse <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gconf2-common: fails to purge because of nonexistant directory 
/etc/gconf/2
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.17
User-Agent: Mutt/1.5.11
Sender: Laurent Fousse <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: gconf2-common
Version: 2.10.1-6
Severity: serious

Hi,

I get the following when trying to purge gconf2-common :

[EMAIL PROTECTED]:~$ sudo dpkg --purge gconf2-common
(Reading database ... 53094 files and directories currently installed.)
Removing gconf2-common ...
Purging configuration files for gconf2-common ...
rmdir: `/etc/gconf/2': No such file or directory
dpkg: error processing gconf2-common (--purge):
 subprocess post-removal script returned error exit status 1
Errors were encountered while processing:
 gconf2-common

Cheers,

Laurent.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.4-blo
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages gconf2-common depends on:
ii  ucf                           2.003      Update Configuration File: preserv

gconf2-common recommends no packages.

-- 
WE FUCKING WORSHIP SATAN

---------------------------------------
Received: (at 335941-done) by bugs.debian.org; 14 Nov 2005 02:33:23 +0000
>From [EMAIL PROTECTED] Sun Nov 13 18:33:23 2005
Return-path: <[EMAIL PROTECTED]>
Received: from linares.terra.com.br ([200.176.10.195])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EbU9r-0004kx-11; Sun, 13 Nov 2005 18:33:23 -0800
Received: from moroto.terra.com.br (moroto.terra.com.br [200.176.10.5])
        by linares.terra.com.br (Postfix) with ESMTP id 9DABE4DC007;
        Mon, 14 Nov 2005 00:33:20 -0200 (BRST)
X-Terra-Karma: -2%
X-Terra-Hash: 45059823269a0773a83b02d94e6a7789
Received-SPF: pass (moroto.terra.com.br: domain of terra.com.br designates 
200.176.10.5 as permitted sender) client-ip=200.176.10.5; [EMAIL PROTECTED]; 
helo=[192.168.1.3];
Received: from [192.168.1.3] (c9066ade.virtua.com.br [201.6.106.222])
        (authenticated user guilherme.pastore)
        by moroto.terra.com.br (Postfix) with ESMTP id 417E514CC049;
        Mon, 14 Nov 2005 00:33:20 -0200 (BRST)
Subject: Re: Fixed in upload of gconf2 2.12.1-1 to experimental
From: "Guilherme de S. Pastore" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=UTF-8
Date: Mon, 14 Nov 2005 00:33:10 -0200
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.1 
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-2.5 required=4.0 tests=BAYES_00,RCVD_IN_SORBS 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2

Version: 2.12.1-1

Hi,

these bugs have been fixed in the last upload of gconf to experimental
and are, therefore, being marked as such. Thanks!

Em Dom, 2005-11-13 =C3=A0s 15:32 -0800, Josselin Mouette escreveu:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Format: 1.7
> Date: Sun, 13 Nov 2005 23:05:39 +0100
> Source: gconf2
> Binary: libgconf2-4 gconf2 gconf2-common libgconf2-dev
> Architecture: source i386 all
> Version: 2.12.1-1
> Distribution: experimental
> Urgency: low
> Maintainer: Josselin Mouette <[EMAIL PROTECTED]>
> Changed-By: Josselin Mouette <[EMAIL PROTECTED]>
> Description:=20
>  gconf2     - GNOME configuration database system (support tools)
>  gconf2-common - GNOME configuration database system (common files)
>  libgconf2-4 - GNOME configuration database system (shared libraries)
>  libgconf2-dev - GNOME configuration database system (development)
> Closes: 329340 335941
> Changes:=20
>  gconf2 (2.12.1-1) experimental; urgency=3Dlow
>  .
>    * New upstream release.
>    * gconf2-common.postrm: check for /etc/gconf/2 before removing it
>      (closes: #335941).
>    * Merge the gconf directory trees for better performance:
>      + 60gconf2_merge-tree: new session startup script. This script
>        forces the rebuild of ~/.gconf.
>      + gconf2-common.install: install this script in /etc/X11/Xsession.=
d.
>      +  control.in: depend on psmisc (for killall).
>      + gconf2.postinst: run gconf-merge-tree on /var/lib/gconf/defaults
>        if necessary.
>      + gconf2-common.postrm: entirely purge /var/lib/gconf,
>        /etc/gconf.xml.defaults and /etc/gconf.xml.mandatory.
>      + gconf2-common.postinst: the chmod-fixes aren't necessary anymore=
.
>    * uupdate: removed, unused.
>    * Provide a framework to easily set up defaults in Debian packages
>      (closes: #329340).
>      + update-gconf-defaults: new script, takes defaults in a specific =
format
>        in /usr/share/gconf/defaults and generates a gconf tree in
>        /var/lib/gconf/debian.defaults.
>      + gconf2.install: install it.
>      + control.in: depend on python for its execution.
>      + rules: run dh_python.
>      + gconf2-common.dirs: create /var/lib/gconf/debian.defaults and
>        /usr/share/gconf/defaults, and remove the unused directories
>        in /usr/share/gconf.
>      + default.path: remove references to the /usr/share directories, a=
nd
>        reference the brand new /var/lib/gconf/debian.defaults instead.
>    * Settle for World domination.
> Files:=20
>  a6917f3c875acb755749f48ea1b0008b 1732 libs optional gconf2_2.12.1-1.ds=
c
>  ed2d2ca67cbfd71c0295f5f964174456 3229227 libs optional gconf2_2.12.1.o=
rig.tar.gz
>  c64c8db4fe615022ebcc58e00f03b058 15144 libs optional gconf2_2.12.1-1.d=
iff.gz
>  5390bd13c3541aeca274ce2f032f80a4 1278270 libs optional gconf2-common_2=
.12.1-1_all.deb
>  0b2b88b38d8ea173b006ec1de7c9afe2 120290 libs optional gconf2_2.12.1-1_=
i386.deb
>  baa49d417b11be5bb0c6adb8345429cb 217064 libs optional libgconf2-4_2.12=
.1-1_i386.deb
>  a27f4913612d95b9a85a6719ccafe77b 242162 libdevel optional libgconf2-de=
v_2.12.1-1_i386.deb
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>=20
> iD8DBQFDd8mKrSla4ddfhTMRAsBLAJ9B77Rek9jTfh914hfmQ4zKAdcdjgCgnnLx
> 9ZYEj55ygQUE/97vTA5couQ=3D
> =3D/ZEP
> -----END PGP SIGNATURE-----

--=20
Guilherme de S. Pastore (fatalerror)
<[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to