Your message dated Sun, 13 Feb 2005 13:47:03 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#292437: fixed in discover-data 2.2005.02.13-1
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; 27 Jan 2005 00:22:09 +0000
>From [EMAIL PROTECTED] Wed Jan 26 16:22:01 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp.easystreet.com [69.30.22.10] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CtxQ8-0007WF-00; Wed, 26 Jan 2005 16:22:00 -0800
Received: from waitron.freegeek.org (209-162-205-26.dq1mn.easystreet.com 
[209.162.205.26])
        by smtp.easystreet.com (Postfix) with ESMTP id A4323364004
        for <[EMAIL PROTECTED]>; Wed, 26 Jan 2005 16:22:00 -0800 (PST)
Received: from localhost (waitron [127.0.0.1])
        by waitron.freegeek.org (Postfix) with ESMTP id 67ED163F4E;
        Wed, 26 Jan 2005 16:22:00 -0800 (PST)
Received: from waitron.freegeek.org ([127.0.0.1])
        by localhost (mail.freegeek.org [127.0.0.1]) (amavisd-new, port 10024)
        with ESMTP id 29078-04; Wed, 26 Jan 2005 16:22:00 -0800 (PST)
Received: from localhost.localdomain (bc176139.bendcable.com [216.228.176.139])
        by waitron.freegeek.org (Postfix) with ESMTP id 1C09A63F4A;
        Wed, 26 Jan 2005 16:22:00 -0800 (PST)
Received: by localhost.localdomain (Postfix, from userid 1000)
        id 3C5714E9EB; Wed, 26 Jan 2005 16:19:27 -0800 (PST)
Date: Wed, 26 Jan 2005 16:19:26 -0800
From: Vagrant Cascadian <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: discover-data: 5333883d still uses XF86_S3 in pci.lst
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0"
Content-Disposition: inline
X-Reportbug-Version: 3.2
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at freegeek.org
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Package: discover-data
Version: 2.2004.11.22-1
Severity: normal

it appears that bug #249935 was fixed in discover-data's pci-device.xml
file, but not the backwards-compatibility file, /lib/discover/pci.lst,
which still erroneously suggests using XF86_S3 (which is no longer
present in sarge) instead of XFree86(s3virge).

please sync the pci.lst file with the most current data from the
pci-device.xml file.

live well,
  vagrant

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.6.8-2-386
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--6TrnltStXW4iwmi0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB+DOOlPc63BPWGpkRAkUWAJ4nUUdpQ7OpkOdddMNvBR7SmozhZgCfeArB
EgLD+C9n622cd24NKb2VN0A=
=E+Wf
-----END PGP SIGNATURE-----

--6TrnltStXW4iwmi0--

---------------------------------------
Received: (at 292437-close) by bugs.debian.org; 13 Feb 2005 18:53:06 +0000
>From [EMAIL PROTECTED] Sun Feb 13 10:53:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1D0Orh-0004L0-00; Sun, 13 Feb 2005 10:53:05 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1D0Olr-0003gt-00; Sun, 13 Feb 2005 13:47:03 -0500
From: Jeff Licquia <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#292437: fixed in discover-data 2.2005.02.13-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 13 Feb 2005 13:47:03 -0500
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-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 7

Source: discover-data
Source-Version: 2.2005.02.13-1

We believe that the bug you reported is fixed in the latest version of
discover-data, which is due to be installed in the Debian FTP archive:

discover-data-udeb_2.2005.02.13-1_all.udeb
  to pool/main/d/discover-data/discover-data-udeb_2.2005.02.13-1_all.udeb
discover-data_2.2005.02.13-1.diff.gz
  to pool/main/d/discover-data/discover-data_2.2005.02.13-1.diff.gz
discover-data_2.2005.02.13-1.dsc
  to pool/main/d/discover-data/discover-data_2.2005.02.13-1.dsc
discover-data_2.2005.02.13-1_all.deb
  to pool/main/d/discover-data/discover-data_2.2005.02.13-1_all.deb
discover-data_2.2005.02.13.orig.tar.gz
  to pool/main/d/discover-data/discover-data_2.2005.02.13.orig.tar.gz



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.
Jeff Licquia <[EMAIL PROTECTED]> (supplier of updated discover-data 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: Sun, 13 Feb 2005 13:22:47 -0500
Source: discover-data
Binary: discover-data-udeb discover-data
Architecture: source all
Version: 2.2005.02.13-1
Distribution: unstable
Urgency: low
Maintainer: Discover Workers <[EMAIL PROTECTED]>
Changed-By: Jeff Licquia <[EMAIL PROTECTED]>
Description: 
 discover-data - Data lists for Discover hardware detection system
 discover-data-udeb - hardware lists for libdiscover2 (short list) (udeb)
Closes: 261705 262920 264594 275492 286308 286398 292437
Changes: 
 discover-data (2.2005.02.13-1) unstable; urgency=low
 .
   * Added data regarding name change in Linux 2.6.9:
     mv64340_eth -> mv643xx_eth.  Closes: #261705.
   * Removed i810-tco from discover 1 data.  Closes: #262920.
   * Add device info for various devices.
     Closes: #264594, #275492, #286308, #292437.
   * Remove references to radeonfb in PCI lists, as it interferes
     with the proprietary drivers.  Closes: #286398.
   * Updated the list of drivers significant to debian-installer.
   * Don't change data files in the main Makefile; move all of that
     to a separate Makefile, so that merely rebuilding the package
     doesn't cause data changes.
Files: 
 7622fd62fd852bae9d4b367fef4dd7f0 750 libs optional 
discover-data_2.2005.02.13-1.dsc
 6c95ebd652b32d0e0daa546eb3dc4911 329713 libs optional 
discover-data_2.2005.02.13.orig.tar.gz
 fdc9710945d351785875ab8fdbd32568 20 libs optional 
discover-data_2.2005.02.13-1.diff.gz
 e29b843787eb004f9e56471c8c30f52d 18564 debian-installer extra 
discover-data-udeb_2.2005.02.13-1_all.udeb
 7307b9cc62c108c3657bce48174cdada 243938 libs optional 
discover-data_2.2005.02.13-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCD53wYApVP/ZmyR0RAr2kAJ9CFJSOL2j8VhHrqc0O7kcEmI4/1wCffYgH
UlFpWUr2Xny7d7BakiSezmY=
=fsbl
-----END PGP SIGNATURE-----


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

Reply via email to