Package: winff
Severity: normal

The error reported in this bug appears to have been caused by an old version of 
mime-support.
After upgrading mime-support, winff installs without complaints. Sorry for the 
noise. Perhaps
winff should suggest a mime-support version that understands 'generic_icon'.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30.4 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ISO-8859-1) (ignored: 
LC_ALL set to en_US)
Shell: /bin/sh linked to /bin/dash

Versions of packages winff depends on:
ii  ffmpeg             4:0.5.svn20090414-0.0 audio/video encoder, streaming ser
ii  konsole [x-termina 4:3.5.7-4             X terminal emulator for KDE
ii  libatk1.0-0        1.20.0-1              The ATK accessibility toolkit
ii  libc6              2.9-4                 GNU C Library: Shared libraries
ii  libglib2.0-0       2.20.1-1              The GLib library of C routines
ii  libgtk2.0-0        2.16.1-2              The GTK+ graphical user interface 
ii  libpango1.0-0      1.24.0-3+b1           Layout and rendering of internatio
ii  libx11-6           2:1.2.2-1             X11 client-side library
ii  xterm [x-terminal- 244-1                 X terminal emulator

winff recommends no packages.

Versions of packages winff suggests:
ii  iceape-browser [www-browser]  1.1.13-1   Iceape Navigator (Internet browser
ii  iceweasel [www-browser]       3.0.9-1    lightweight web browser based on M
ii  konqueror [www-browser]       4:4.3.0-1  KDE 4's advanced file manager, web
ii  kpdf [pdf-viewer]             4:3.5.5-2  PDF viewer for KDE
ii  lynx [www-browser]            2.8.6-2    Text-mode WWW Browser
ii  w3m [www-browser]             0.5.2-2.1  WWW browsable pager with excellent
ii  xpdf-reader [pdf-viewer]      3.01-9     Portable Document Format (PDF) sui

-- no debconf information



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

Reply via email to