[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#394076: marked as done (Please add to instalation logs dfbinfo's output)

Your message dated Tue, 24 Oct 2006 06:47:17 -0700
with message-id <E1GcMcf-00011m-6w@spohr.debian.org>
and subject line Bug#394076: fixed in installation-report 2.21
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: installation-report
Severity: minor
Tags: patch

The dfbinfo tool is a diagnostic tool meant to gather infos about DirectFrameBuffer configuration and it's going to be provided [1] by libdirectfb-0.9-25-udeb. Having its output in the instalation logs would be very useful to debug graphical-installer related issues: could this be achived by something like the attached patch? Note that the patch assumes dfbinfo to be located in /usr/lib/directfb-0.9.25/bin/, which won't be true the day a libdirectfb-bin-udeb is created.



[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390437

Index: report-hw
--- report-hw   (revisione 41837)
+++ report-hw   (copia locale)
@@ -41,3 +41,7 @@
 dmidecode 2>&1 | addinfo dmidecode
+if [ -e /usr/lib/directfb-0.9.25/bin/dfbinfo ]; then
+       /usr/lib/directfb-0.9.25/bin/dfbinfo 2>&1 | addinfo dfbinfo

--- End Message ---
--- Begin Message ---
Source: installation-report
Source-Version: 2.21

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

  to pool/main/i/installation-report/installation-report_2.21.dsc
  to pool/main/i/installation-report/installation-report_2.21.tar.gz
  to pool/main/i/installation-report/installation-report_2.21_all.deb
  to pool/main/i/installation-report/save-logs_2.21_all.udeb

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 394076@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Frans Pop <fjp@debian.org> (supplier of updated installation-report 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 ftpmaster@debian.org)

Hash: SHA1

Format: 1.7
Date: Tue, 24 Oct 2006 14:55:25 +0200
Source: installation-report
Binary: save-logs installation-report
Architecture: source all
Version: 2.21
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Frans Pop <fjp@debian.org>
 installation-report - system installation report
 save-logs  - save logs and configuration for debug purposes (udeb)
Closes: 394076
 installation-report (2.21) unstable; urgency=low
   * Add output from dfbinfo (only when gtk frontend is being used).
     Closes: #394076.
   [ Updated translations ]
   * Belarusian (be.po) by Andrei Darashenka
   * Hungarian (hu.po) by SZERVÃ?C Attila
   * Kurdish (ku.po) by Erdal Ronahi
   * Albanian (sq.po) by Elian Myftiu
   * Tamil (ta.po) by Damodharan Rajalingam
   * Vietnamese (vi.po) by Clytie Siddall
 2bc2c9c3b19f8f6c33b2543697e8917e 797 debian-installer optional installation-report_2.21.dsc
 97f3b7a08de04dc758e104d80e851d1f 65436 debian-installer optional installation-report_2.21.tar.gz
 71f41a837e8fa2db4348f1edfa4642f0 42646 debian-installer standard save-logs_2.21_all.udeb
 c26e35826427c97ed2289111234aac3b 14102 misc optional installation-report_2.21_all.deb
Package-Type: udeb

Version: GnuPG v1.4.5 (GNU/Linux)


--- End Message ---

Reply to: