Your message dated Fri, 23 Sep 2005 06:32:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#329789: fixed in gconf2 2.10.1-5
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; 23 Sep 2005 12:57:52 +0000
>From [EMAIL PROTECTED] Fri Sep 23 05:57:52 2005
Return-path: <[EMAIL PROTECTED]>
Received: from a82-93-13-222.adsl.xs4all.nl (localhost.localdomain)
[82.93.13.222]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EIn7f-00067K-00; Fri, 23 Sep 2005 05:57:52 -0700
Received: from shevek by localhost.localdomain with local (Exim 4.52)
id 1EIn7V-0002ou-7T; Fri, 23 Sep 2005 14:57:41 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Bas Wijnen <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gconf2-common fails to install if /etc/gconf/2/ is not present
X-Mailer: reportbug 3.17
Date: Fri, 23 Sep 2005 14:57:41 +0200
Message-Id: <[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-3
Severity: grave
Justification: renders package unusable
I was just installing sid, by installing from a sarge cdrom and changing
sources.list at the first possible opportunity. When installing
gconf2-common, it failed configuring because /etc/gconf/2/ didn't exist.
Creating it solved the problem. This should be done by the package.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-386
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages gconf2-common depends on:
ii ucf 2.002 Update Configuration File: preserv
gconf2-common recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 329789-close) by bugs.debian.org; 23 Sep 2005 13:38:32 +0000
>From [EMAIL PROTECTED] Fri Sep 23 06:38:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EInes-0000EJ-00; Fri, 23 Sep 2005 06:32:10 -0700
From: Sebastien Bacher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#329789: fixed in gconf2 2.10.1-5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 23 Sep 2005 06:32:10 -0700
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=-4.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Source: gconf2
Source-Version: 2.10.1-5
We believe that the bug you reported is fixed in the latest version of
gconf2, which is due to be installed in the Debian FTP archive:
gconf2-common_2.10.1-5_all.deb
to pool/main/g/gconf2/gconf2-common_2.10.1-5_all.deb
gconf2_2.10.1-5.diff.gz
to pool/main/g/gconf2/gconf2_2.10.1-5.diff.gz
gconf2_2.10.1-5.dsc
to pool/main/g/gconf2/gconf2_2.10.1-5.dsc
gconf2_2.10.1-5_i386.deb
to pool/main/g/gconf2/gconf2_2.10.1-5_i386.deb
libgconf2-4_2.10.1-5_i386.deb
to pool/main/g/gconf2/libgconf2-4_2.10.1-5_i386.deb
libgconf2-dev_2.10.1-5_i386.deb
to pool/main/g/gconf2/libgconf2-dev_2.10.1-5_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastien Bacher <[EMAIL PROTECTED]> (supplier of updated gconf2 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 23 Sep 2005 15:03:36 +0200
Source: gconf2
Binary: libgconf2-4 gconf2 gconf2-common libgconf2-dev
Architecture: source i386 all
Version: 2.10.1-5
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette <[EMAIL PROTECTED]>
Changed-By: Sebastien Bacher <[EMAIL PROTECTED]>
Description:
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: 329724 329789
Changes:
gconf2 (2.10.1-5) unstable; urgency=low
.
* debian/gconf2-common.dirs:
- list "/etc/gconf/2" (Closes: #329724, #329789).
Files:
78e587df951e0728a45681a8dbf0cfa0 1732 libs optional gconf2_2.10.1-5.dsc
a1393a69acd3307b61e4d11830751c74 12969 libs optional gconf2_2.10.1-5.diff.gz
f10130b43b95e36061d73ac35f1e2512 1159916 libs optional
gconf2-common_2.10.1-5_all.deb
56a0bf366e213124760ba4dc5a26dc8a 114536 libs optional gconf2_2.10.1-5_i386.deb
ba6a605d834e0387bf71a7d30ba37311 212466 libs optional
libgconf2-4_2.10.1-5_i386.deb
014be82455dad61861437812c443caf0 237344 libdevel optional
libgconf2-dev_2.10.1-5_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDNACjQxo87aLX0pIRAlziAJ99MPA8WDXxcK78+yojoFsEQTmNhwCgptR5
z4Uv/rKnVZuLI0fxVBsxKs0=
=tlBv
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
