Your message dated Sat, 29 Nov 2014 18:02:16 -0500
with message-id
<caecnbvynvec+gjj9ge2hzyuemu2pdzvoad-nnfs8u6zifqb...@mail.gmail.com>
and subject line Fixed in 0.12.1-5
has caused the Debian Bug report #696549,
regarding mediatomb: implicit dependencies for ffmpeg
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 ow...@bugs.debian.org
immediately.)
--
696549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mediatomb
Version: 0.12.1-4
Severity: normal
It would be nice if Depends would be updated to reflect correct dependencies.
Right now backporting mediatomb on debian/stable fails with:
make[3]: Entering directory `/tmp/mediatomb-0.12.1/build'
g++ -DHAVE_CONFIG_H -I. -I.. -I../tombupnp/upnp/inc -I../src
-I../tombupnp/ixml/inc -I../tombupnp/threadutil/inc -I../tombupnp/upnp/inc -I..
-I/usr/include/mysql -DBIG_JOINS=1 -fno-strict-aliasing -DUNIV_LINUX
-DUNIV_LINUX -I/usr/include/js -I/usr/include/taglib -pthread -g
-O2 -c -o libmediatomb_a-ffmpeg_handler.o `test -f
'../src/metadata/ffmpeg_handler.cc' || echo
'./'`../src/metadata/ffmpeg_handler.cc
../src/metadata/ffmpeg_handler.cc: In function ‘void
addFfmpegResourceFields(zmm::Ref<CdsItem>, AVFormatContext*, int*, int*)’:
../src/metadata/ffmpeg_handler.cc:211: error: ‘AVMEDIA_TYPE_VIDEO’ was not
declared in this scope
../src/metadata/ffmpeg_handler.cc:242: error: ‘AVMEDIA_TYPE_AUDIO’ was not
declared in this scope
make[3]: *** [libmediatomb_a-ffmpeg_handler.o] Error 1
make[3]: Leaving directory `/tmp/mediatomb-0.12.1/build'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/mediatomb-0.12.1'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/mediatomb-0.12.1'
dh_auto_build: make -j1 returned exit code 2
make: *** [binary-arch] Error 2
Thanks
-- System Information:
Debian Release: 6.0.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (200, 'testing'), (100,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mediatomb depends on:
ii chromium-br 6.0.472.63~r59945-5+squeeze6 Chromium browser
ii epiphany-br 2.30.6-1 Intuitive GNOME web browser
ii iceweasel [ 10.0.11esr-1~bpo60+1 Web browser based on Firefox
ii links [www- 2.3~pre1-1+squeeze1 Web browser running in text mode
ii mediatomb-d 0.12.0~svn2018-6.1 UPnP MediaServer (daemon package)
ii w3m [www-br 0.5.2-9 WWW browsable pager with excellent
mediatomb recommends no packages.
mediatomb suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: mediatomb
Version: 0.12.1-5
This bug was fixed in 0.12.1-5.
The problem was that the package depended on libavformat-dev instead of
libavformat-dev (>= 4:0.7-2~). At the time this bug was submitted squeeze had
ffmpeg version 4:0.5.10-1 in the release archive and libav version
6:0.8.3-1~bpo60+1 in backports but since the dependency was unversioned
4:0.5.10-1 was used.
In 0.12.1-5 libavformat-dev (>= 6:9) is used. I tried compiling 0.12.1-7
in a wheezy chroot since wheezy has 6:0.8.16-1 in release and 6:10.1-1~bpo70+1
in backports and it succeeded building using the backports packages.
Cheers,
Miguel
--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
