Your message dated Thu, 16 Jul 2015 12:01:57 -0400
with message-id
<CAEcnbVy4-yafz7ko0Vg=p1flwac9nu-tdtwsjejgbxxzsak...@mail.gmail.com>
and subject line Unreproducible
has caused the Debian Bug report #792595,
regarding mediatomb-common: Licence clash with libmp4v2 (MPL) and mediatomb
GPL-+2
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.)
--
792595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792595
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mediatomb-common
Version: 0.12.1-47-g7ab7616-1
Severity: serious
Dear Maintainer,
In mediatomb 0.12.1-7 libmp4v2 support has been disabled due to licence
problem and now libmp4v2 support has been enabled again...
Could you explain ?
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 4.0.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mediatomb-common depends on:
ii libavformat56 6:11.4-2
ii libavutil54 6:11.4-2
ii libc6 2.19-19
ii libcurl3-gnutls 7.43.0-1
ii libexif12 0.6.21-2
ii libexpat1 2.1.0-6+b3
ii libffmpegthumbnailer4 2.0.8-2+b4
ii libflac8 1.3.1-2
ii libgcc1 1:5.1.1-14
ii libjs-prototype 1.7.1-3
ii libmagic1 1:5.22+15-2
ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4.3
ii libmysqlclient18 5.6.25-2
ii libnspr4 2:4.10.8-2
ii libsqlite3-0 3.8.10.2-1
ii libstdc++6 5.1.1-14
ii libtag1c2a 1.9.1-2.1
ii libuuid1 2.26.2-6
ii zlib1g 1:1.2.8.dfsg-2+b1
mediatomb-common recommends no packages.
mediatomb-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> Dear Maintainer,
>
> In mediatomb 0.12.1-7 libmp4v2 support has been disabled due to licence
> problem and now libmp4v2 support has been enabled again...
>
> Could you explain ?
Not sure what there is to explain since nothing about libmp4v2 has changed.
It still is compiled with "--disable-libmp4v2" and the package does
not depend on libmp4v2 in any architecture as partially shown by the
i386 example in the submitted bug report.
> Versions of packages mediatomb-common depends on:
> ii libavformat56 6:11.4-2
> ii libavutil54 6:11.4-2
> ii libc6 2.19-19
> ii libcurl3-gnutls 7.43.0-1
> ii libexif12 0.6.21-2
> ii libexpat1 2.1.0-6+b3
> ii libffmpegthumbnailer4 2.0.8-2+b4
> ii libflac8 1.3.1-2
> ii libgcc1 1:5.1.1-14
> ii libjs-prototype 1.7.1-3
> ii libmagic1 1:5.22+15-2
> ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4.3
> ii libmysqlclient18 5.6.25-2
> ii libnspr4 2:4.10.8-2
> ii libsqlite3-0 3.8.10.2-1
> ii libstdc++6 5.1.1-14
> ii libtag1c2a 1.9.1-2.1
> ii libuuid1 2.26.2-6
> ii zlib1g 1:1.2.8.dfsg-2+b1
>
> mediatomb-common recommends no packages.
>
> mediatomb-common suggests no packages.
>
> -- no debconf information
The buildd logs show that the libmp4v2-dev does not get installed either.
The only changes about libmp4v2 were updating the old libmp4v2 patch
that updated the code for newer libmp4v versions and reverting a
upstream commit which forced compilation with older libmp4v2 versions
but this was fixed by the 1st patch I mentioned.
I'm closing this bug but feel free to reopen if there is still an issue.
Hope this helps,
Miguel
--- End Message ---
