Package: mediatomb Version: 0.11.0-3 Severity: important
when importing media, mediatomb no longer reads and stores the 4cc information. i confirmed this by looking into the database: here is a sample entry from the mt_cds_object table and the "resources" field. 0~protocolInfo=http-get%3A%2A%3Avideo%2Favi%3A%2A&size=178433640&bitrate=1030~~ i remember that those lines used to hvae a 4cc=XXXX at the end. I questioned jin about this and he thinks its a dependency problem with ffmpeg. coincidentally, this problem started when my ffmpeg updated from 2008-12-26 18:00:47 upgrade ffmpeg 3:20080706-0.3 3:20081210-0.1 Perhaps mediatomb needs to be rebuilt against the new ffmpeg? I am considering doing a build myself to test this solution -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages mediatomb depends on: ii iceweasel [www-browser] 3.0.5-1 lightweight web browser based on M ii lynx-cur [www-browser] 2.8.7dev11-2 Text-mode WWW Browser with NLS sup ii mediatomb-daemon 0.11.0-3 UPnP MediaServer (daemon package) ii w3m [www-browser] 0.5.2-2+b1 WWW browsable pager with excellent mediatomb recommends no packages. mediatomb suggests no packages. -- no debconf information
