Your message dated Wed, 09 Aug 2006 16:02:09 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349619: fixed in lshw 02.08.01-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)

--- Begin Message ---
Package: lshw
Version: 02.06-3
Severity: minor


This seems to work fine on amd64, which should be mentioned in the 
package description.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages lshw depends on:
ii  libc6                         2.3.5-12   GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.2-6  GCC support library
ii  libstdc++6                    4.0.2-6    The GNU Standard C++ Library v3
ii  lshw-common                   02.06-3    information about hardware configu

lshw recommends no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Source: lshw
Source-Version: 02.08.01-1

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

lshw-common_02.08.01-1_all.deb
  to pool/main/l/lshw/lshw-common_02.08.01-1_all.deb
lshw-gtk_02.08.01-1_i386.deb
  to pool/main/l/lshw/lshw-gtk_02.08.01-1_i386.deb
lshw_02.08.01-1.diff.gz
  to pool/main/l/lshw/lshw_02.08.01-1.diff.gz
lshw_02.08.01-1.dsc
  to pool/main/l/lshw/lshw_02.08.01-1.dsc
lshw_02.08.01-1_i386.deb
  to pool/main/l/lshw/lshw_02.08.01-1_i386.deb
lshw_02.08.01.orig.tar.gz
  to pool/main/l/lshw/lshw_02.08.01.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.
Ghe Rivero <[EMAIL PROTECTED]> (supplier of updated lshw 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: Thu, 20 Jul 2006 00:35:07 +0200
Source: lshw
Binary: lshw-common lshw lshw-gtk
Architecture: source i386 all
Version: 02.08.01-1
Distribution: unstable
Urgency: low
Maintainer: Ghe Rivero <[EMAIL PROTECTED]>
Changed-By: Ghe Rivero <[EMAIL PROTECTED]>
Description: 
 lshw       - information about hardware configuration
 lshw-common - information about hardware configuration
 lshw-gtk   - information about hardware configuration
Closes: 349619 360182
Changes: 
 lshw (02.08.01-1) unstable; urgency=low
 .
   * New upstream release. Closes: #360182
   * Added AMD64 to the known platforms that works properly. Closes: #349619
Files: 
 9970d4212e0f8c40d21d3b930ec1943b 654 utils optional lshw_02.08.01-1.dsc
 57c1bb0fec3543641c389726a8844307 1062265 utils optional 
lshw_02.08.01.orig.tar.gz
 4aebfa9c00161be23f7e7785849f696e 7593 utils optional lshw_02.08.01-1.diff.gz
 7a573cdb5f4ae0d9683beac15be5393b 295134 utils optional lshw_02.08.01-1_i386.deb
 7bb860c7d2acf282a3dea3b7ed728423 399038 utils optional 
lshw-gtk_02.08.01-1_i386.deb
 6831f37f26645ca2a4d34ac9ba8d2e3b 751670 utils optional 
lshw-common_02.08.01-1_all.deb

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

iD8DBQFE2meMipBneRiAKDwRAuyTAJ9sjlzSM1lujqX1gXhlSQRfRdZ9MwCeOAf9
+X7x4eux8BiVO0ltPIv4FIg=
=hkBg
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to