Your message dated Tue, 08 Jul 2008 22:00:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in 2.2.4-1
has caused the Debian Bug report #443960,
regarding gnucash-common: Does not contain menu icon gnucash-icon.xpm
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
443960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443960
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gnucash-common
Version: 2.2.1-1
Severity: minor

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package gnucash-common does not contain the menu icon.
/usr/share/menu/gnucash says:

        [snip]
        icon="/usr/share/gnucash/pixmaps/gnucash-icon.xpm"

However,

$ file /usr/share/gnucash/pixmaps/gnucash-icon.xpm
/usr/share/gnucash/pixmaps/gnucash-icon.xpm: ERROR: cannot open
`/usr/share/gnucash/pixmaps/gnucash-icon.xpm' (No such file or
directory)

$ sudo dpkg -L gnucash-common | grep xpm
$

Regards,
Andre


- -- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

gnucash-common depends on no packages.

Versions of packages gnucash-common recommends:
ii  gnucash                       2.2.1-1    A personal finance tracking progra

- -- debconf-show failed

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

iD8DBQFG+LVEkDGKfHXexj8RAjNtAJ9YHzrYksqlttNB7dKBQ3VDpbb5ZgCeOi/p
RYy2vm+bru221Ot0ZiqTctU=
=Ji/o
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
Version: 2.2.4-1

The problem appears to be fixed now


--- End Message ---

Reply via email to