Your message dated Wed, 21 Sep 2005 13:15:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Recent xscreensaver versions have these fixes built-in
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; 9 Nov 2001 17:57:08 +0000
>From [EMAIL PROTECTED] Fri Nov 09 11:57:08 2001
Return-path: <[EMAIL PROTECTED]>
Received: from p3ee2b6b9.dip0.t-ipconnect.de (gauss.dali.inka.de) 
[62.226.182.185] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 162Ftq-0006oS-00; Fri, 09 Nov 2001 11:57:07 -0600
Received: from stephan by gauss.dali.inka.de with local (Exim 3.32 #1 (Debian))
        id 162Fll-0003gP-00; Fri, 09 Nov 2001 18:48:45 +0100
Date: Fri, 9 Nov 2001 18:48:45 +0100
From: Stephan Niemz <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xscreensaver-gnome: xscreensaver-demo doesn't remove orphan entries 
from ~/.xscreensaver
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q"
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
X-Reportbug-Version: 1.33
Delivered-To: [EMAIL PROTECTED]


--ikeVEW9yuYc//A+q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: xscreensaver-gnome
Version: 3.33-5
Severity: normal

    When updating xscreensaver, some savers were removed (like xroger,
xworm and extrusion).  But they are still present in my ~/.xscreensaver
file, so it would be great if xscreensaver-demo would encounter that and
remove them from the displayed list of screensavers.


-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux gauss.dali.inka.de 2.4.14 #1 Tue Nov 6 02:12:35 CET 2001 i686
Locale: LANG=3DC, LC_CTYPE=3D

Versions of packages xscreensaver-gnome depends on:
ii  gdk-imlib1                  1.9.11-3     Gdk-Imlib is an imaging librar=
y fo
ii  libart2                     1.4.1.2-6    The Gnome canvas widget
ii  libaudiofile0               0.2.3-1      The Audiofile Library
ii  libc6                       2.2.4-5      GNU C Library: Shared librarie=
s an
ii  libcapplet0                 1:1.4.0.1-13 Library for Gnome Control Cent=
er a
ii  libdb3                      3.2.9-11     Berkeley v3 Database Libraries=
 [ru
ii  libesd-alsa0                0.2.22-6     Enlightened Sound Daemon (ALSA=
) -=20
ii  libesd-alsa0 [libesd0]      0.2.22-6     Enlightened Sound Daemon (ALSA=
) -=20
ii  libglib1.2                  1.2.10-1.2   The GLib library of C routines
ii  libgnome32                  1.4.1.2-6    The Gnome libraries
ii  libgnomesupport0            1.4.1.2-6    The Gnome libraries (Support l=
ibra
ii  libgnomeui32                1.4.1.2-6    The Gnome libraries (User Inte=
rfac
ii  libgnorba27                 1.4.1.2-6    Gnome CORBA services
ii  libgtk1.2                   1.2.10-2.1   The GIMP Toolkit set of widget=
s fo
ii  liborbit0                   0.5.12-1     Libraries for ORBit - a CORBA =
ORB
ii  xlibs                       4.1.0-9      X Window System client librari=
es
ii  xscreensaver                3.33-5       Automatic screensaver for X

--ikeVEW9yuYc//A+q
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Weitere Infos: siehe http://www.gnupg.org

iD8DBQE77Bb9D4jPIYfdYgoRAoPbAJwJ+C2PufWlWoOtrQT2NCd+EiSEPgCaAlRW
U91mGP3st07v1/99mA3pjtk=
=P7Le
-----END PGP SIGNATURE-----

--ikeVEW9yuYc//A+q--

---------------------------------------
Received: (at 118881-close) by bugs.debian.org; 21 Sep 2005 11:15:20 +0000
>From [EMAIL PROTECTED] Wed Sep 21 04:15:20 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.charite.de [160.45.207.131] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EI2ZM-0001dw-00; Wed, 21 Sep 2005 04:15:20 -0700
Received: from localhost (localhost [127.0.0.1])
        by mail.charite.de (Postfix) with ESMTP id A49B522108A;
        Wed, 21 Sep 2005 13:15:18 +0200 (CEST)
Received: from mail.charite.de ([127.0.0.1])
 by localhost (mail.charite.de [127.0.0.1]) (amavisd-new, port 10025)
 with ESMTP id 01359-05-2; Wed, 21 Sep 2005 13:15:07 +0200 (CEST)
Received: from postamt.charite.de (postamt.charite.de [160.45.207.132])
        (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
        (Client did not present a certificate)
        by mail.charite.de (Postfix) with ESMTP id B068C221071;
        Wed, 21 Sep 2005 13:15:07 +0200 (CEST)
Received: by postamt.charite.de (Postfix, from userid 7945)
        id 3AAD62209A2; Wed, 21 Sep 2005 13:15:07 +0200 (CEST)
Date: Wed, 21 Sep 2005 13:15:07 +0200
From: Ralf Hildebrandt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED]
Subject: Recent xscreensaver versions have these fixes built-in
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.10i
X-Virus-Scanned: amavisd-new at charite.de
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2

While wading through the BTS I found this bug to be fixed, but never
closed. 


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

Reply via email to