Bug#667203: marked as done (hydrogen: ftbfs with GCC-4.7)
Your message dated Fri, 04 May 2012 06:54:15 + with message-id and subject line Bug#667203: fixed in italc 1:1.0.13-1.3 has caused the Debian Bug report #667203, regarding hydrogen: ftbfs with GCC-4.7 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.) -- 667203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hydrogen Version: 0.9.6~beta1-2 Severity: important Tags: sid wheezy User: debian-...@lists.debian.org Usertags: ftbfs-gcc-4.7 The package fails to build in a test rebuild on at least amd64 with gcc-4.7/g++-4.7, but succeeds to build with gcc-4.6/g++-4.6. The severity of this report may be raised before the wheezy release. portmidi_driver.cpp:108:16: error: 'usleep' was not declared in this scope The full build log can be found at: http://people.debian.org/~lucas/logs/2012/03/29-clang-gcc47/unstable-gcc47/hydrogen_0.9.6~beta1-2_unstable-gcc47.log The last lines of the build log are at the end of this report. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html To build with GCC 4.7, either set CC=gcc-4.7 CXX=g++-4.7 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. [...] make[3]: Entering directory `/«PKGBUILDDIR»/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles" [ 0%] Building CXX object src/core/CMakeFiles/hydrogen-core-0.9.6.dir/src/logger.cpp.o cd "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/core" && /usr/bin/g++-O2 -fno-implement-inlines -g -I"/«PKGBUILDDIR»/src/core/include" -I"/«PKGBUILDDIR»/include" -I"/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/core/include" -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -o CMakeFiles/hydrogen-core-0.9.6.dir/src/logger.cpp.o -c "/«PKGBUILDDIR»/src/core/src/logger.cpp" /usr/bin/cmake -E cmake_progress_report "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles" [ 0%] Building CXX object src/core/CMakeFiles/hydrogen-core-0.9.6.dir/src/midi_map.cpp.o cd "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/core" && /usr/bin/g++-O2 -fno-implement-inlines -g -I"/«PKGBUILDDIR»/src/core/include" -I"/«PKGBUILDDIR»/include" -I"/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/core/include" -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -o CMakeFiles/hydrogen-core-0.9.6.dir/src/midi_map.cpp.o -c "/«PKGBUILDDIR»/src/core/src/midi_map.cpp" /usr/bin/cmake -E cmake_progress_report "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles" 82 [ 1%] Building CXX object src/core/CMakeFiles/hydrogen-core-0.9.6.dir/src/sampler/sampler.cpp.o cd "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/core" && /usr/bin/g++-O2 -fno-implement-inlines -g -I"/«PKGBUILDDIR»/src/core/include" -I"/«PKGBUILDDIR»/include" -I"/«PKGBUILDDIR»/obj-x86_64-linux-gnu/src/core/include" -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtDBus -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -o CMakeFiles/hydrogen-core-0.9.6.dir/src/sampler/sampler.cpp.o -c "/«PKGBUILDDIR»/src/core/src/sampler/sampler.cpp" /usr/bin/cmake -E cmake_progress_report "/«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles" [ 1%] Building CXX object src/core/CMakeFiles/hydrogen-c
libav_0.8.1-7_mipsel.changes ACCEPTED into unstable
Accepted: ffmpeg-dbg_0.8.1-7_mipsel.deb to main/liba/libav/ffmpeg-dbg_0.8.1-7_mipsel.deb ffmpeg_0.8.1-7_mipsel.deb to main/liba/libav/ffmpeg_0.8.1-7_mipsel.deb libav-dbg_0.8.1-7_mipsel.deb to main/liba/libav/libav-dbg_0.8.1-7_mipsel.deb libav-extra-dbg_0.8.1-7_mipsel.deb to main/liba/libav/libav-extra-dbg_0.8.1-7_mipsel.deb libav-regular-dbg_0.8.1-7_mipsel.deb to main/liba/libav/libav-regular-dbg_0.8.1-7_mipsel.deb libav-tools_0.8.1-7_mipsel.deb to main/liba/libav/libav-tools_0.8.1-7_mipsel.deb libavcodec-dev_0.8.1-7_mipsel.deb to main/liba/libav/libavcodec-dev_0.8.1-7_mipsel.deb libavcodec-extra-53_0.8.1-7_mipsel.deb to main/liba/libav/libavcodec-extra-53_0.8.1-7_mipsel.deb libavcodec53_0.8.1-7_mipsel.deb to main/liba/libav/libavcodec53_0.8.1-7_mipsel.deb libavdevice-dev_0.8.1-7_mipsel.deb to main/liba/libav/libavdevice-dev_0.8.1-7_mipsel.deb libavdevice53_0.8.1-7_mipsel.deb to main/liba/libav/libavdevice53_0.8.1-7_mipsel.deb libavfilter-dev_0.8.1-7_mipsel.deb to main/liba/libav/libavfilter-dev_0.8.1-7_mipsel.deb libavfilter2_0.8.1-7_mipsel.deb to main/liba/libav/libavfilter2_0.8.1-7_mipsel.deb libavformat-dev_0.8.1-7_mipsel.deb to main/liba/libav/libavformat-dev_0.8.1-7_mipsel.deb libavformat53_0.8.1-7_mipsel.deb to main/liba/libav/libavformat53_0.8.1-7_mipsel.deb libavutil-dev_0.8.1-7_mipsel.deb to main/liba/libav/libavutil-dev_0.8.1-7_mipsel.deb libavutil51_0.8.1-7_mipsel.deb to main/liba/libav/libavutil51_0.8.1-7_mipsel.deb libpostproc-dev_0.8.1-7_mipsel.deb to main/liba/libav/libpostproc-dev_0.8.1-7_mipsel.deb libpostproc52_0.8.1-7_mipsel.deb to main/liba/libav/libpostproc52_0.8.1-7_mipsel.deb libswscale-dev_0.8.1-7_mipsel.deb to main/liba/libav/libswscale-dev_0.8.1-7_mipsel.deb libswscale2_0.8.1-7_mipsel.deb to main/liba/libav/libswscale2_0.8.1-7_mipsel.deb Changes: libav (6:0.8.1-7) unstable; urgency=low . * Fix build for hurd. Thanks to Samuel Thibault for patch. (Closes: #613034) (Closes: #671038) * Properly migrate /etc/ffserver.conf to /etc/avserver.conf. (Closes: #660786) * Renable opencv support. Override entries for your package: ffmpeg-dbg_0.8.1-7_mipsel.deb - extra oldlibs ffmpeg_0.8.1-7_mipsel.deb - extra oldlibs libav-dbg_0.8.1-7_mipsel.deb - extra debug libav-extra-dbg_0.8.1-7_mipsel.deb - extra debug libav-regular-dbg_0.8.1-7_mipsel.deb - extra debug libav-tools_0.8.1-7_mipsel.deb - optional video libavcodec-dev_0.8.1-7_mipsel.deb - optional libdevel libavcodec-extra-53_0.8.1-7_mipsel.deb - optional libs libavcodec53_0.8.1-7_mipsel.deb - optional libs libavdevice-dev_0.8.1-7_mipsel.deb - optional libdevel libavdevice53_0.8.1-7_mipsel.deb - optional libs libavfilter-dev_0.8.1-7_mipsel.deb - optional libdevel libavfilter2_0.8.1-7_mipsel.deb - optional libs libavformat-dev_0.8.1-7_mipsel.deb - optional libdevel libavformat53_0.8.1-7_mipsel.deb - optional libs libavutil-dev_0.8.1-7_mipsel.deb - optional libdevel libavutil51_0.8.1-7_mipsel.deb - optional libs libpostproc-dev_0.8.1-7_mipsel.deb - optional libdevel libpostproc52_0.8.1-7_mipsel.deb - optional libs libswscale-dev_0.8.1-7_mipsel.deb - optional libdevel libswscale2_0.8.1-7_mipsel.deb - optional libs Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processing of libav_0.8.1-7_mipsel.changes
libav_0.8.1-7_mipsel.changes uploaded successfully to localhost along with the files: libav-tools_0.8.1-7_mipsel.deb ffmpeg_0.8.1-7_mipsel.deb ffmpeg-dbg_0.8.1-7_mipsel.deb libav-dbg_0.8.1-7_mipsel.deb libav-regular-dbg_0.8.1-7_mipsel.deb libav-extra-dbg_0.8.1-7_mipsel.deb libavutil51_0.8.1-7_mipsel.deb libavcodec53_0.8.1-7_mipsel.deb libavdevice53_0.8.1-7_mipsel.deb libavformat53_0.8.1-7_mipsel.deb libavfilter2_0.8.1-7_mipsel.deb libpostproc52_0.8.1-7_mipsel.deb libswscale2_0.8.1-7_mipsel.deb libavutil-dev_0.8.1-7_mipsel.deb libavcodec-dev_0.8.1-7_mipsel.deb libavdevice-dev_0.8.1-7_mipsel.deb libavformat-dev_0.8.1-7_mipsel.deb libavfilter-dev_0.8.1-7_mipsel.deb libpostproc-dev_0.8.1-7_mipsel.deb libswscale-dev_0.8.1-7_mipsel.deb libavcodec-extra-53_0.8.1-7_mipsel.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671302: libav: circular dependency between libav and opencv
On May 3, 2012 5:36 PM, "Julien Cristau" wrote: > > On Thu, May 3, 2012 at 10:20:57 -0400, Andres Mejia wrote: > > > I'm not entirely certain how build circular dependency issues like this are > > resolved. Perhaps we should ask for help from the toolchain package > > maintainers or debian-devel. > > What's wrong with just disabling opencv? > > Cheers, > Julien There's a circular build dependency with x264 and gpac. I rather find anothet way to resolve this issue now then resorting to doing a full rebuild of libav on the buildd network twice. It may just be faster to do what I suggested earlier. ~ Andres ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: add patch
Processing commands for cont...@bugs.debian.org: > tags 667101 + patch Bug #667101 [ardour] ardour: ftbfs with GCC-4.7 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 667101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#667101: add patch
tags 667101 + patch thanks diff -Nru ardour-2.8.12/debian/changelog ardour-2.8.12/debian/changelog --- ardour-2.8.12/debian/changelog 2011-10-05 17:57:57.0 + +++ ardour-2.8.12/debian/changelog 2012-05-03 20:37:06.0 + @@ -1,3 +1,10 @@ +ardour (1:2.8.12-1.1) unstable; urgency=low + + * Non maintainer upload. + * Fix build failure with gcc 4.7. Closes: #667101. + + -- Matthias Klose Thu, 03 May 2012 22:36:28 +0200 + ardour (1:2.8.12-1) unstable; urgency=low [ Jaromír Mikeš ] diff -Nru ardour-2.8.12/debian/patches/ftbfs-gcc-4.7.diff ardour-2.8.12/debian/patches/ftbfs-gcc-4.7.diff --- ardour-2.8.12/debian/patches/ftbfs-gcc-4.7.diff 1970-01-01 00:00:00.0 + +++ ardour-2.8.12/debian/patches/ftbfs-gcc-4.7.diff 2012-05-03 20:40:09.0 + @@ -0,0 +1,24 @@ +Index: ardour-2.8.12/libs/pbd/path.cc +=== +--- ardour-2.8.12.orig/libs/pbd/path.cc2009-02-24 12:38:16.0 + ardour-2.8.12/libs/pbd/path.cc 2012-05-03 20:36:04.098422794 + +@@ -17,6 +17,7 @@ + */ + + #include ++#include + + #include + #include +Index: ardour-2.8.12/libs/rubberband/src/main.cpp +=== +--- ardour-2.8.12.orig/libs/rubberband/src/main.cpp2009-02-24 12:38:17.0 + ardour-2.8.12/libs/rubberband/src/main.cpp 2012-05-03 20:40:05.806431789 + +@@ -21,6 +21,7 @@ + #include + #include + #include ++#include + #include "sysutils.h" + + #ifdef __MSVC__ diff -Nru ardour-2.8.12/debian/patches/series ardour-2.8.12/debian/patches/series --- ardour-2.8.12/debian/patches/series 2011-10-05 03:12:38.0 + +++ ardour-2.8.12/debian/patches/series 2012-05-03 20:35:30.0 + @@ -9,3 +9,4 @@ 140_enable-ladish.patch 150_soundtouch.patch 160_kfreebsd.patch +ftbfs-gcc-4.7.diff ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671362: mplayer2 crashes when trying to connect to remote pulseaudio server
Fixed upstream in bb908027178fe8bfd7d6e3fc255dea8c5051cd4a. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Initial packaging of handbrake for Debian (WIP)
Hi there.
As I am a brand new dad, I want to transcode videos of my newborn son to
formats that other family members can see and the first thought of mine was
to do the job with handbrake.
For that purpose, I took the packages of Christian and started modifying
them to be in a git-buildpackage buildable form (I wouldn't like anything
else) and I have eliminated *almost* (not all, yet) downloading that
handbrake performs when it is being built.
With the packages that the team has already (libmkv and faac), there are
only some finishing touches before we get a functional (not legal) package.
Then, after that, I guess that one could also be legally OK and upload
handbrake to Debian.
Would you be interested in the work that I have done so far? Please, keep in
mind that it is *incomplete* and very *dirty*, but a start, at least. :)
Regards,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671302: libav: circular dependency between libav and opencv
On Thu, May 3, 2012 at 10:20:57 -0400, Andres Mejia wrote: > I'm not entirely certain how build circular dependency issues like this are > resolved. Perhaps we should ask for help from the toolchain package > maintainers or debian-devel. What's wrong with just disabling opencv? Cheers, Julien signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Re: clam: ftbfs with GCC-4.7
Processing commands for cont...@bugs.debian.org: > tags 667136 + patch Bug #667136 [clam] clam: ftbfs with GCC-4.7 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 667136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Re: clam-networkeditor: ftbfs with GCC-4.7
Processing commands for cont...@bugs.debian.org: > tags 667137 + patch Bug #667137 [clam-networkeditor] clam-networkeditor: ftbfs with GCC-4.7 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 667137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#667137: clam-networkeditor: ftbfs with GCC-4.7
tags 667137 + patch thanks this can be worked around by building with -fpermissive. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#667136: clam: ftbfs with GCC-4.7
tags 667136 + patch thanks this can be worked around by building with -fpermissive. and please turn on the verbose build. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671407: vlc-nox does not include /usr/lib/vlc/plugins/codec/libavcodec_plugin.so
Package: vlc-nox Version: 2.0.1-4 Severity: important Dear Maintainer, vlc-nox does not include the module provided in /usr/lib/vlc/plugins/codec/libavcodec_plugin.so This means that to use the features provided by this module, the user would need to install the "vlc" package, which they might not want if they're running a headless server. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 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 vlc-nox depends on: ii liba52-0.7.4 0.7.4-16 ii libasound2 1.0.25-2 ii libass40.10.0-3 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libavc1394-0 0.5.4-1 ii libavcodec53 5:0.8.1-4 ii libavformat53 5:0.8.1-4 ii libavutil515:0.8.1-4 ii libbluray1 1:0.2.2-1 ii libc6 2.13-30 ii libcaca0 0.99.beta18-1 ii libcddb2 1.3.2-3 ii libcdio10 0.81-5 ii libdbus-1-31.5.12-1 ii libdc1394-22 2.2.0-2 ii libdca00.0.5-5 ii libdirac-decoder0 1.0.2-6 ii libdirac-encoder0 1.0.2-6 ii libdvbpsi7 0.2.2-1 ii libdvdnav4 4.2.0-1 ii libdvdread44.2.0-1 ii libebml3 1.2.2-2 ii libfaad2 2.7-8 ii libflac8 1.2.1-6 ii libfontconfig1 2.8.0-3.1 ii libfreetype6 2.4.9-1 ii libfribidi00.19.2-3 ii libgcc11:4.7.0-3 ii libgcrypt111.5.0-3 ii libgnutls262.12.18-1 ii libgpg-error0 1.10-3 ii libiso9660-7 0.81-5 ii libkate1 0.4.1-1 ii liblircclient0 0.9.0~pre1-1 ii liblua5.1-05.1.5-1 ii libmad00.15.1b-7 ii libmatroska5 1.3.0-2 ii libmodplug11:0.8.8.4-3 ii libmpcdec6 2:0.1~r459-2 ii libmpeg2-4 0.4.1-3 ii libmtp91.1.3-2 ii libncursesw5 5.9-6 ii libogg01.2.2~dfsg-1 ii libpng12-0 1.2.49-1 ii libpostproc52 5:0.8.1-4 ii libproxy0 0.3.1-4+b3 ii libraw1394-11 2.0.8-1 ii libresid-builder0c2a 2.1.1-13 ii libsamplerate0 0.1.8-4 ii libschroedinger-1.0-0 1.0.11-1 ii libshout3 2.2.2-8 ii libsidplay22.1.1-13 ii libsmbclient 2:3.6.4-1 ii libspeex1 1.2~rc1-3 ii libspeexdsp1 1.2~rc1-3 ii libstdc++6 4.7.0-3 ii libswscale25:0.8.1-4 ii libtag1c2a 1.7.1-2 ii libtheora0 1.1.1+dfsg.1-3 ii libtinfo5 5.9-6 ii libtwolame00.3.13-1 ii libudev0 175-3.1 ii libupnp3 1:1.6.6-5.1 ii libusb-0.1-4 2:0.1.12-20 ii libv4l-0 0.8.8-1 ii libvcdinfo00.7.24-1 ii libvlc52.0.1-4 ii libvlccore52.0.1-4 ii libvorbis0a1.3.2-1.2 ii libvorbisenc2 1.3.2-1.2 ii libx264-1202:0.120.2171+git01f7a33-4 ii libxml22.7.8.dfsg-9 ii libzvbi0 0.2.33-5 ii zlib1g 1:1.2.6.dfsg-2 vlc-nox recommends no packages. vlc-nox suggests no packages. Versions of packages libvlc5 depends on: ii libc62.13-30 ii libvlccore5 2.0.1-4 Versions of packages libvlccore5 depends on: ii libc62.13-30 ii libdbus-1-3 1.5.12-1 ii vlc-data 2.0.1-4 Versions of packages vlc-nox is related to: ii libavutil50 ii libavutil51 5:0.8.1-4 -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671302: Circular Build Dependencies (was Bug#671302: libav: circular dependency between libav and opencv)
On May 3, 2012 10:20 AM, "Andres Mejia" wrote: > > On May 3, 2012 9:30 AM, "Pino Toscano" wrote: > > > > Alle giovedì 3 maggio 2012, Andres Mejia ha scritto: > > > On Thu, May 3, 2012 at 3:44 AM, Pino Toscano wrote: > > > > Package: libav > > > > Version: 6:0.8.1-7 > > > > Severity: important > > > > > > > > Hi, > > > > > > > > libav 6:0.8.1-7 reenables the use of opencv... which itself uses > > > > libav libraries. This currently makes libav unbuildable on mipsel > > > > and hurd-i386, and generically makes libav no more bootstrap'able > > > > without having itself compiled already. > > > > Could you please drop the opencv usage again, please? > > > > > > > What could be done instead is a binary only upload with opencv > > > support disabled (i.e. use dpkg-buildpackage -B). Doing it on our > > > end will not require changing the version. Once this package is > > > uploaded, the release team can then be asked to do a binNMU for > > > these archs, which will bring back opencv support since the archive > > > will contain the regular *.debian.tar.gz changes that included > > > opencv. > > > > > > I believe this is better than doing a full build on all archs without > > > opencv, then doing another build with opencv. > > > > This mess (which is only a mess, not a clean solution) does not solve at > > all the fact that you cannot do a clean build of libav without having > > libav compiled already (for opencv). > > I don't see this as a viable solution, especially if in the future the > > epoch is raised bringing again conflicts between the old libav libraries > > and the new one. > > > > -- > > Pino Toscano > > I'm not entirely certain how build circular dependency issues like this are resolved. Perhaps we should ask for help from the toolchain package maintainers or debian-devel. > > ~ Andres Hello all, I would like to know if there is a good (perhaps best) approach in resolving issues with packages with circular build dependencies. Libav has various circular build dependencies including. libav -> opencv -> libav libav -> x264 -> libav libav -> x264 -> gpac -> libav I found some mention of this issue at [1]. This however doesn't offer any clear solution. 1. http://wiki.debian.org/DebianBootstrap ~ Andres ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671151: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: multicat | 1.0-1 | hurd-i386, kfreebsd-amd64, kfreebsd-i386 --- Reason --- ANAIS; Architectures not allowed -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 671...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/671151 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 671302 src:libav 6:0.8.1-7 Bug #671302 [libav] libav: circular dependency between libav and opencv Bug reassigned from package 'libav' to 'src:libav'. No longer marked as found in versions 6:0.8.1-7. Ignoring request to alter fixed versions of bug #671302 to the same values previously set Bug #671302 [src:libav] libav: circular dependency between libav and opencv Marked as found in versions libav/6:0.8.1-7. > merge 671302 671381 Bug #671302 [src:libav] libav: circular dependency between libav and opencv Bug #671381 [src:libav] libav: unbuildable due to circular dependency with opencv Merged 671302 671381 > End of message, stopping processing here. Please contact me if you need assistance. -- 671302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671302 671381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] crtmpserver/master: Add postrm script for crtmpserver-apps.
Hi Jonas, Alessio,
I complete fixes. Please review changes and upload package.
On Tue, Apr 24, 2012 at 09:23:56AM -0400, Jonas Smedegaard wrote:
> On 12-04-24 at 10:17am, Andriy Beregovenko wrote:
> > Hi Jonas,
> >
> > On Tue, Apr 24, 2012 at 02:40:22AM -0400, Jonas Smedegaard wrote:
> > > On 12-04-24 at 08:53am, Andriy Beregovenko wrote:
> > > > Hi Alessio,
> > > >
> > > > On Tue, Apr 24, 2012 at 02:06:43AM +0200, Alessio Treglia wrote:
> > > > > This doesn't look sane to me:
> > > > >
> > > > > On Sat, Apr 14, 2012 at 9:45 PM,
> > > > > wrote:
> > > > > > +do_remove() {
> > > > > > + for app in $APPLICATIONS; do
> > > > > > + if [ -f "/etc/crtmpserver/applications/$app.lua" ];
> > > > > > then
> > > > > > + compare
> > > > > > "/etc/crtmpserver/applications/$app.lua" \
> > > > > > +
> > > > > > "/usr/share/doc/crtmpserver-apps/examples/$app.lua" \
> > > > > > + && rm
> > > > > > "/etc/crtmpserver/applications/$app.lua"
> > > > >
> > > > > Why do you try to remove those files?
> > > > > The crtmpserver-apps package seems to own no conffiles.
> > > > This files are not managed by conffile, so I check if it is same as
> > > > default,
> > > > and if yes - remove it(if no user changes in it)
> > > >
> > > > >
> > > > > > + fi
> > > > > > + done
> > > > > > + rmdir /etc/crtmpserver/applications
> > > > >
> > > > > This is Severity: grave as it means removing user's files and may
> > > > > potentially
> > > > > cause data loss!
> > > > This may not lead to data loss, because rmdir(w/o -f) actually do not
> > > > remove dir
> > > > if there are files inside, so this command remove dir only if it is
> > > > empty
> > > > (i.e. user do not modificate any conf files and it was removed during
> > > > prev
> > > > steps)
> > > >
> > > > > If you really want to provide crtmpserver-apps with conffiles, you
> > > > > should install them clean way (e.g. dh_install) and then manage
> > > > > their removal with dpkg-maintscript-helper.
> > >
> > > If you really really need to do it this odd way (I too recommend to
> > > simply use conffiles) then beware that you must not rely on files below
> > > /usr/share/doc but need to install the reference files somewhere else.
> >
> > Ok, let me describe my point, maybe I have misunderstood somewhere.
> > Files that need for server to be usable is installed with package
> > crtmpserver. Lua scripts that is installed with package crtmpserver-apps
> > mostly is example scripts and it provides "default solution" that can done
> > basic needs(so user will not modify them and if it purge app - it will be
> > removed), but users who need to implement advanced configuration will
> > modify this scripts harder, and in this way I do not think that annoing user
> > with conffiles notifications is good idea. That is why i'm just copy
> > "example scripts" from /usr/share/doc and maintaine "remove/purge" action
> > manually.
> >
> > Please correct me if I wrong.
>
> Either the files are *only* provided as examples or they are handled by
> the packaging scripts.
>
> If only example files, then they are not owned by the package and should
> not be handled by the package.
>
> If handled by the package - no matter how rarely - they must not be
> located below /usr/share/doc/.
>
> Conffiles except for special cases where you need some complex
> maintenance routines. If conffile notifications occur without a sane
> reason, then something else is wrong with your packaging!
>
> Please carefully reas Debian Policy ?10.7.3 and ?12.3.
>
>
> - Jonas
>
> --
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136 Website: http://dr.jones.dk/
>
> [x] quote me freely [ ] ask before reusing [ ] keep private
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
--
Best regards,
Andriy
0xBDDBDAE3
signature.asc
Description: Digital signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org:
> severity 671302 serious
Bug #671302 [libav] libav: circular dependency between libav and opencv
Severity set to 'serious' from 'important'
> merge 671302 671381
Bug #671302 [libav] libav: circular dependency between libav and opencv
Unable to merge bugs because:
package of #671381 is 'src:libav' not 'libav'
Failed to merge 671302: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x25bd2c8)',
'requester', 'Andres Mejia ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'
End of message, stopping processing here.
Please contact me if you need assistance.
--
671302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671302
671381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
zita-convolver 3.1.0-2 MIGRATED to testing
FYI: The status of the zita-convolver source package in Debian's testing distribution has changed. Previous version: 3.1.0-1 Current version: 3.1.0-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
wxsvg 2:1.1.8~dfsg0-2 MIGRATED to testing
FYI: The status of the wxsvg source package in Debian's testing distribution has changed. Previous version: 2:1.1.7~dfsg0-1 Current version: 2:1.1.8~dfsg0-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
mididings 0~20120419~ds0-1 MIGRATED to testing
FYI: The status of the mididings source package in Debian's testing distribution has changed. Previous version: 0~20120312-1 Current version: 0~20120419~ds0-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
libquicktime 2:1.2.4-2 MIGRATED to testing
FYI: The status of the libquicktime source package in Debian's testing distribution has changed. Previous version: 2:1.2.4-1 Current version: 2:1.2.4-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more information. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671381: libav: unbuildable due to circular dependency with opencv
Source: libav Version: 6:0.8.1-7 Severity: serious libav build-depends on libopencv-dev, which depends on libswscale2, which comes from libav source and is not installable on mipsel currently because of b0rked dependencies in 6:0.8.1-5. Cheers, Julien signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: debian-multimedia.org considered harmful - redux
On May 3, 2012, at 9:24 AM, Stefano Zacchiroli wrote:
> On Thu, Apr 12, 2012 at 02:26:27PM +0200, Stefano Zacchiroli wrote:
>> I've drafted a message that I'd like to send to Christian publicly
>> Cc:-ing this list. It is attached to this mail for review by the
>> pkg-multimedia team. (Yes, I know this is a public list and Christian
>> will likely read it before the review, but I don't particularly mind: it
>> will just anticipate a public discussion we'd like to have anyhow.)
>>
>> I'd appreciate your feedback on it.
>
> I've now patched my first draft trying to take into account your
> feedback without changing the substance of the message I think we should
> send through. The new draft is attached.
>
> You're feedback is, again, very welcome.
> If you have no further changes to suggest or objections, I can send it
> this week-end.
>
> Either way, please let me know,
> Cheers.
> --
> Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
> Maître de conférences .. http://upsilon.cc/zack .. . . o
> Debian Project Leader... @zack on identi.ca ...o o o
> « the first rule of tautology club is the first rule of tautology club »
>
> From: Stefano Zacchiroli
> Date: May 3, 2012 9:22:49 AM EDT
> To: Christian Marillat , maril...@free.fr
> Cc: pkg-multimedia-maintainers@lists.alioth.debian.org
> Bcc: lea...@debian.org
> Subject: on package duplication between Debian and debian-multimedia
>
>
> Dear Christian,
> as you probably are aware of, there are recurring discussions on the
> package duplication between the official Debian archive and the
> debian-multimedia.org ("d-m.o" from now on) that you maintain.
>
> AFAIK, the Debian team in charge of maintaining multimedia packages
> (that I'm Cc:-ing) is not happy about the duplication and has approached
> you about that [1], providing some evidence of the troubles that it
> causes to them and to Debian users that also happen to use d-m.o. OTOH
> I'm sure you are maintaining d-m.o to provide a useful service to Debian
> users, when some of the packages you distribute are not available in
> Debian proper.
>
> [1]
> http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-March/025498.html
>
> Personally, I think that principle is fine, but I'm worried about the
> duplication part. Not only due to the troubles that it might cause to
> users, but also for the apparent waste of maintenance energies. Energies
> that could be put into better use if you and the pkg-multimedia team
> could find a way to collaborate, and to do so contributing to the
> *official* Debian packaging of the concerned software.
>
> I have no specific opinion on the technical claims that d-m.o causes
> trouble to official Debian packages. That might be true or not. Ditto
> for your allegations of conflict of interest in the maintenance of
> ffmpeg or libav in Debian. But I observe that *in* Debian we do have
> mechanisms to solve that kind of issues, if and when they arise. As long
> as you keep on doing your work outside Debian instead of raising your
> concerns within Debian, we'll have to keep on assuming that what is
> being done in Debian is fine and is entitled to the official status that
> come with the name "Debian".
>
> Thinking about it, I think we should choose one of the two possible way
> forward:
>
> 1) You and the pkg-multimedia team reach an agreement on
> which-packages-belong-where. One way to settle would be that for
> every package that exist in the official Debian archive, the same
> package should not exist in d-m.o, unless it has a version that does
> not interfere with the official packages in "standard" Debian
> installations. Another way would be to rename packages and sonames.
>
> I understand that such agreements would give a sort of "advantage" to
> the pkg-multimedia people over d-m.o, but that seems to be warranted
> by the fact that they are doing the official packaging, while you're
> not. If, as I hope, you could start doing your packaging work
> (wherever possible) within Debian as well, things would be different
> and we could consider solving potential technical conflicts in the
> usual Debian way.
>
> 2) You stop using "debian" as part of the domain name of your
> repository, which is confusing for users (e.g. [2,3]). That would
> allow each part to keep on doing what they want in terms of
> packaging, but at least would remove any of the existings doubts
> about the official status of d-m.o.
>
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660924#20
> [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668308#47
>
> I can imagine that would be a painful step for you to take, given the
> well established domain name. But it seems fair to ask you to do so
> if we couldn't manage to find an agreement between you and the
> official Debian packaging initiative of software you're maintaining
> in an unofficial repositor
Bug#671366: laditools: ladi-control-center crashes when a studio is loaded.
Package: laditools
Version: 1.0-1
Severity: grave
Justification: renders package unusable
nevyn@cetacea:/usr/share/doc/laditools$ ladi-control-center
Traceback (most recent call last):
File "/usr/bin/ladi-control-center", line 714, in
app.run()
File "/usr/bin/ladi-control-center", line 667, in run
self._activate(**kwargs)
File "/usr/bin/ladi-control-center", line 643, in _activate
treeview = modules[mod].run({})
File "/usr/bin/ladi-control-center", line 109, in run
return self.activate()
File "/usr/bin/ladi-control-center", line 565, in activate
start_editing=False)
TypeError: set_cursor() got an unexpected keyword argument 'focus_column'
nevyn@cetacea:/usr/share/doc/laditools$
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.4.0-rc2-rt2-00249-ga9d3702 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages laditools depends on:
ii gir1.2-vte-2.90 1:0.32.1-1
ii python2.7.2-10
ii python-gi 3.2.0-3
ii python-laditools 1.0-1
Versions of packages laditools recommends:
ii gladish 1+dfsg0-2
Versions of packages laditools suggests:
ii g15composer 3.2-2
-- no debconf information
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671302: libav: circular dependency between libav and opencv
On May 3, 2012 9:30 AM, "Pino Toscano" wrote: > > Alle giovedì 3 maggio 2012, Andres Mejia ha scritto: > > On Thu, May 3, 2012 at 3:44 AM, Pino Toscano wrote: > > > Package: libav > > > Version: 6:0.8.1-7 > > > Severity: important > > > > > > Hi, > > > > > > libav 6:0.8.1-7 reenables the use of opencv... which itself uses > > > libav libraries. This currently makes libav unbuildable on mipsel > > > and hurd-i386, and generically makes libav no more bootstrap'able > > > without having itself compiled already. > > > Could you please drop the opencv usage again, please? > > > > > What could be done instead is a binary only upload with opencv > > support disabled (i.e. use dpkg-buildpackage -B). Doing it on our > > end will not require changing the version. Once this package is > > uploaded, the release team can then be asked to do a binNMU for > > these archs, which will bring back opencv support since the archive > > will contain the regular *.debian.tar.gz changes that included > > opencv. > > > > I believe this is better than doing a full build on all archs without > > opencv, then doing another build with opencv. > > This mess (which is only a mess, not a clean solution) does not solve at > all the fact that you cannot do a clean build of libav without having > libav compiled already (for opencv). > I don't see this as a viable solution, especially if in the future the > epoch is raised bringing again conflicts between the old libav libraries > and the new one. > > -- > Pino Toscano I'm not entirely certain how build circular dependency issues like this are resolved. Perhaps we should ask for help from the toolchain package maintainers or debian-devel. ~ Andres ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671362: mplayer2: mpolayer2 crashes when trying to connect remote pulsaudio server
Package: mplayer2 Version: 2.0-426-gc32b3ed-2 Severity: important Dear Maintainer, when I try to run "mplayer -ao pulse:servername" it crashes: --cut-- ... == Requested audio codec family [mpg123] (afm=mpg123) not available. Enable it at compilation. Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 48000 Hz, 1 ch, floatle, 96.0 kbit/6.25% (ratio: 12000->192000) Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio) == MPlayer interrupted by signal 11 in module: ao2_init - MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash. - MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug. MPlayer2 UNKNOWN (C) 2000-2011 MPlayer Team --cut-- Version 2.0-426-gc32b3ed-2 works fine. But 2.0-518-gb711624-2, 2.0-541-gf64a4e9-1 and 1:2.0~git20120430-dmo1 are broken. Thank you! -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (700, 'unstable'), (600, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mplayer2 depends on: ii libaa11.4p5-39 ii libasound21.0.25-2 ii libass4 0.10.0-3 ii libaudio2 1.9.3-5 ii libavcodec53 7:0.10.2-dmo3 ii libavformat53 7:0.10.2-dmo3 ii libavutil51 7:0.10.2-dmo3 ii libbluray11:0.2.2-1 ii libc6 2.13-31 ii libcaca0 0.99.beta18-1 ii libcdparanoia03.10.2+debian-10.1 ii libdca0 0.0.5-5 ii libdirectfb-1.2-9 1.2.10.0-4.3 ii libdvdnav44.2.0-1 ii libdvdread4 4.2.0-1 ii libenca0 1.13-4 ii libesd0 0.2.41-10+b1 ii libfaad2 2.7-8 ii libfontconfig12.9.0-2 ii libfreetype6 2.4.9-1 ii libfribidi0 0.19.2-3 ii libgcc1 1:4.7.0-6 ii libgif4 4.1.6-9 ii libgl1-mesa-glx [libgl1] 8.0.2-2 ii libjack0 [libjack-0.116] 1:0.121.3+20120418git75e3e20b-1 ii libjpeg8 8d-1 ii liblircclient00.9.0~pre1-1 ii libncurses5 5.9-7 ii libogg0 1.2.2~dfsg-1 ii libpng12-01.2.49-1 ii libpostproc52 7:0.10.2-dmo3 ii libpulse0 1.1-3.2 ii libsdl1.2debian 1.2.15-3 ii libsmbclient 2:3.6.5-1 ii libspeex1 1.2~rc1-3 ii libstdc++64.7.0-6 ii libswscale2 7:0.10.2-dmo3 ii libtheora01.1.1+dfsg.1-3 ii libtinfo5 5.9-7 ii libvdpau1 0.4.1-5 ii libvorbis0a 1.3.2-1.2 ii libx11-6 2:1.4.99.901-2 ii libxext6 2:1.3.1-2 ii libxinerama1 2:1.1.2-1 ii libxt61:1.1.3-1 ii libxv12:1.0.7-1 ii libxvidcore4 3:1.3.2-0.6 ii libxxf86dga1 2:1.1.3-1 ii libxxf86vm1 1:1.1.2-1 ii zlib1g1:1.2.6.dfsg-2 mplayer2 recommends no packages. mplayer2 suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: debian-multimedia.org considered harmful - redux
On May 3, 2012 9:24 AM, "Stefano Zacchiroli" wrote:
>
> On Thu, Apr 12, 2012 at 02:26:27PM +0200, Stefano Zacchiroli wrote:
> > I've drafted a message that I'd like to send to Christian publicly
> > Cc:-ing this list. It is attached to this mail for review by the
> > pkg-multimedia team. (Yes, I know this is a public list and Christian
> > will likely read it before the review, but I don't particularly mind: it
> > will just anticipate a public discussion we'd like to have anyhow.)
> >
> > I'd appreciate your feedback on it.
>
> I've now patched my first draft trying to take into account your
> feedback without changing the substance of the message I think we should
> send through. The new draft is attached.
>
> You're feedback is, again, very welcome.
> If you have no further changes to suggest or objections, I can send it
> this week-end.
>
> Either way, please let me know,
> Cheers.
> --
> Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
> Maître de conférences .. http://upsilon.cc/zack .. . . o
> Debian Project Leader... @zack on identi.ca ...o o o
> « the first rule of tautology club is the first rule of tautology club »
>
>
> -- Forwarded message --
> From: Stefano Zacchiroli
> To: Christian Marillat , maril...@free.fr
> Cc: pkg-multimedia-maintainers@lists.alioth.debian.org
> Date: Thu, 3 May 2012 15:22:49 +0200
> Subject: on package duplication between Debian and debian-multimedia
> Dear Christian,
> as you probably are aware of, there are recurring discussions on the
> package duplication between the official Debian archive and the
> debian-multimedia.org ("d-m.o" from now on) that you maintain.
>
> AFAIK, the Debian team in charge of maintaining multimedia packages
> (that I'm Cc:-ing) is not happy about the duplication and has approached
> you about that [1], providing some evidence of the troubles that it
> causes to them and to Debian users that also happen to use d-m.o. OTOH
> I'm sure you are maintaining d-m.o to provide a useful service to Debian
> users, when some of the packages you distribute are not available in
> Debian proper.
>
> [1]
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-March/025498.html
>
> Personally, I think that principle is fine, but I'm worried about the
> duplication part. Not only due to the troubles that it might cause to
> users, but also for the apparent waste of maintenance energies. Energies
> that could be put into better use if you and the pkg-multimedia team
> could find a way to collaborate, and to do so contributing to the
> *official* Debian packaging of the concerned software.
>
> I have no specific opinion on the technical claims that d-m.o causes
> trouble to official Debian packages. That might be true or not. Ditto
> for your allegations of conflict of interest in the maintenance of
> ffmpeg or libav in Debian. But I observe that *in* Debian we do have
> mechanisms to solve that kind of issues, if and when they arise. As long
> as you keep on doing your work outside Debian instead of raising your
> concerns within Debian, we'll have to keep on assuming that what is
> being done in Debian is fine and is entitled to the official status that
> come with the name "Debian".
>
> Thinking about it, I think we should choose one of the two possible way
> forward:
>
> 1) You and the pkg-multimedia team reach an agreement on
> which-packages-belong-where. One way to settle would be that for
> every package that exist in the official Debian archive, the same
> package should not exist in d-m.o, unless it has a version that does
> not interfere with the official packages in "standard" Debian
> installations. Another way would be to rename packages and sonames.
>
> I understand that such agreements would give a sort of "advantage" to
> the pkg-multimedia people over d-m.o, but that seems to be warranted
> by the fact that they are doing the official packaging, while you're
> not. If, as I hope, you could start doing your packaging work
> (wherever possible) within Debian as well, things would be different
> and we could consider solving potential technical conflicts in the
> usual Debian way.
>
> 2) You stop using "debian" as part of the domain name of your
> repository, which is confusing for users (e.g. [2,3]). That would
> allow each part to keep on doing what they want in terms of
> packaging, but at least would remove any of the existings doubts
> about the official status of d-m.o.
>
> [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660924#20
> [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668308#47
>
> I can imagine that would be a painful step for you to take, given the
> well established domain name. But it seems fair to ask you to do so
> if we couldn't manage to find an agreement between you and the
> official Debian packaging initiative of software you're maintaining
> in an unofficial repos
Bug#671360: gladish tools->configure jack references ladiconf which no longer exists.
Package: gladish Version: 1+dfsg0-2 Severity: grave Justification: renders package unusable gladish should be configured to use ladi-control-center by default -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0-rc2-rt2-00249-ga9d3702 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gladish depends on: ii ladish 1+dfsg0-2 ii libart-2.0-2 2.3.21-1 ii libatk1.0-02.4.0-2 ii libatkmm-1.6-1 2.22.6-1 ii libc6 2.13-32 ii libcairo2 1.12.2-1 ii libcairomm-1.0-1 1.10.0-1 ii libdbus-1-31.5.12-1 ii libdbus-glib-1-2 0.98-1 ii libflowcanvas5 0.7.1+dfsg0-0.1+b1 ii libfontconfig1 2.9.0-3 ii libfreetype6 2.4.9-1 ii libgcc11:4.7.0-7 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.2-1 ii libglibmm-2.4-1c2a 2.32.0-1 ii libgnomecanvas2-0 2.30.3-1 ii libgnomecanvasmm-2.6-1c2a 2.26.0-1 ii libgtk2.0-02.24.10-1 ii libgtkmm-2.4-1c2a 1:2.24.2-1 ii libpango1.0-0 1.30.0-1 ii libpangomm-1.4-1 2.28.4-1 ii libsigc++-2.0-0c2a 2.2.10-0.1 ii libstdc++6 4.7.0-7 Versions of packages gladish recommends: ii laditools 1.0-1 gladish suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: debian-multimedia.org considered harmful - redux
Am 03.05.2012 15:24, schrieb Stefano Zacchiroli: You're feedback is, again, very welcome. Reads fine, thank you! - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: debian-multimedia.org considered harmful - redux
Hi, On Thu, May 3, 2012 at 3:24 PM, Stefano Zacchiroli wrote: > I've now patched my first draft trying to take into account your > feedback without changing the substance of the message I think we should > send through. The new draft is attached. +1 from me. Thanks! -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer | quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671302: libav: circular dependency between libav and opencv
Alle giovedì 3 maggio 2012, Andres Mejia ha scritto: > On Thu, May 3, 2012 at 3:44 AM, Pino Toscano wrote: > > Package: libav > > Version: 6:0.8.1-7 > > Severity: important > > > > Hi, > > > > libav 6:0.8.1-7 reenables the use of opencv... which itself uses > > libav libraries. This currently makes libav unbuildable on mipsel > > and hurd-i386, and generically makes libav no more bootstrap'able > > without having itself compiled already. > > Could you please drop the opencv usage again, please? > > > What could be done instead is a binary only upload with opencv > support disabled (i.e. use dpkg-buildpackage -B). Doing it on our > end will not require changing the version. Once this package is > uploaded, the release team can then be asked to do a binNMU for > these archs, which will bring back opencv support since the archive > will contain the regular *.debian.tar.gz changes that included > opencv. > > I believe this is better than doing a full build on all archs without > opencv, then doing another build with opencv. This mess (which is only a mess, not a clean solution) does not solve at all the fact that you cannot do a clean build of libav without having libav compiled already (for opencv). I don't see this as a viable solution, especially if in the future the epoch is raised bringing again conflicts between the old libav libraries and the new one. -- Pino Toscano signature.asc Description: This is a digitally signed message part. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: debian-multimedia.org considered harmful - redux
On Thu, Apr 12, 2012 at 02:26:27PM +0200, Stefano Zacchiroli wrote:
> I've drafted a message that I'd like to send to Christian publicly
> Cc:-ing this list. It is attached to this mail for review by the
> pkg-multimedia team. (Yes, I know this is a public list and Christian
> will likely read it before the review, but I don't particularly mind: it
> will just anticipate a public discussion we'd like to have anyhow.)
>
> I'd appreciate your feedback on it.
I've now patched my first draft trying to take into account your
feedback without changing the substance of the message I think we should
send through. The new draft is attached.
You're feedback is, again, very welcome.
If you have no further changes to suggest or objections, I can send it
this week-end.
Either way, please let me know,
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences .. http://upsilon.cc/zack .. . . o
Debian Project Leader... @zack on identi.ca ...o o o
« the first rule of tautology club is the first rule of tautology club »
--- Begin Message ---
Dear Christian,
as you probably are aware of, there are recurring discussions on the
package duplication between the official Debian archive and the
debian-multimedia.org ("d-m.o" from now on) that you maintain.
AFAIK, the Debian team in charge of maintaining multimedia packages
(that I'm Cc:-ing) is not happy about the duplication and has approached
you about that [1], providing some evidence of the troubles that it
causes to them and to Debian users that also happen to use d-m.o. OTOH
I'm sure you are maintaining d-m.o to provide a useful service to Debian
users, when some of the packages you distribute are not available in
Debian proper.
[1]
http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/2012-March/025498.html
Personally, I think that principle is fine, but I'm worried about the
duplication part. Not only due to the troubles that it might cause to
users, but also for the apparent waste of maintenance energies. Energies
that could be put into better use if you and the pkg-multimedia team
could find a way to collaborate, and to do so contributing to the
*official* Debian packaging of the concerned software.
I have no specific opinion on the technical claims that d-m.o causes
trouble to official Debian packages. That might be true or not. Ditto
for your allegations of conflict of interest in the maintenance of
ffmpeg or libav in Debian. But I observe that *in* Debian we do have
mechanisms to solve that kind of issues, if and when they arise. As long
as you keep on doing your work outside Debian instead of raising your
concerns within Debian, we'll have to keep on assuming that what is
being done in Debian is fine and is entitled to the official status that
come with the name "Debian".
Thinking about it, I think we should choose one of the two possible way
forward:
1) You and the pkg-multimedia team reach an agreement on
which-packages-belong-where. One way to settle would be that for
every package that exist in the official Debian archive, the same
package should not exist in d-m.o, unless it has a version that does
not interfere with the official packages in "standard" Debian
installations. Another way would be to rename packages and sonames.
I understand that such agreements would give a sort of "advantage" to
the pkg-multimedia people over d-m.o, but that seems to be warranted
by the fact that they are doing the official packaging, while you're
not. If, as I hope, you could start doing your packaging work
(wherever possible) within Debian as well, things would be different
and we could consider solving potential technical conflicts in the
usual Debian way.
2) You stop using "debian" as part of the domain name of your
repository, which is confusing for users (e.g. [2,3]). That would
allow each part to keep on doing what they want in terms of
packaging, but at least would remove any of the existings doubts
about the official status of d-m.o.
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660924#20
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668308#47
I can imagine that would be a painful step for you to take, given the
well established domain name. But it seems fair to ask you to do so
if we couldn't manage to find an agreement between you and the
official Debian packaging initiative of software you're maintaining
in an unofficial repository.
We could also consider various in-between solutions, such as adding
suitable prominent disclaimers on your website explaining that your
initiative is not affiliated with the Debian Project, that it might
cause technical incompatibilities with official packages, and that the
donations you're collecting are for you personally and not for the
Debian Project.
I hope we can reach an agreement on (some variants of) point (1). I'm
personally convin
Bug#671302: libav: circular dependency between libav and opencv
On Thu, May 3, 2012 at 3:44 AM, Pino Toscano wrote: > Package: libav > Version: 6:0.8.1-7 > Severity: important > > Hi, > > libav 6:0.8.1-7 reenables the use of opencv... which itself uses libav > libraries. This currently makes libav unbuildable on mipsel and > hurd-i386, and generically makes libav no more bootstrap'able without > having itself compiled already. > Could you please drop the opencv usage again, please? > > Thanks, > -- > Pino > > > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers What could be done instead is a binary only upload with opencv support disabled (i.e. use dpkg-buildpackage -B). Doing it on our end will not require changing the version. Once this package is uploaded, the release team can then be asked to do a binNMU for these archs, which will bring back opencv support since the archive will contain the regular *.debian.tar.gz changes that included opencv. I believe this is better than doing a full build on all archs without opencv, then doing another build with opencv. -- ~ Andres ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Problem in package liblilv-dev
Hi there,
I got the following error message while building Luppp on Debian
testing:
/libengine_gui.a(lvtwohost.cpp.0.o): In function `Lilv::uri_to_path(char
const*)':
/usr/include/lilv-0/lilv/lilvmm.hpp:24: multiple definition of
`Lilv::uri_to_path(char const*)'
./libengine_gui.a(offlineworker.cpp.0.o):/usr/include/lilv-0/lilv/lilvmm.hpp:24:
first defined here
collect2: ld returned 1 exit status
/usr/include/lilv-0/lilv/lilvmm.hpp:24 reads:
const char* uri_to_path(const char* uri) { return lilv_uri_to_path(uri); }
When this header gets included in more than one compilation unit,
uri_to_path gets defined several times, which causes the error.
In the current upstream version of lilv from [1], the function is
declared 'static inline' which fixes the problem.
- Johannes
[1] http://drobilla.net/software/lilv/
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#671302: libav: circular dependency between libav and opencv
Package: libav Version: 6:0.8.1-7 Severity: important Hi, libav 6:0.8.1-7 reenables the use of opencv... which itself uses libav libraries. This currently makes libav unbuildable on mipsel and hurd-i386, and generically makes libav no more bootstrap'able without having itself compiled already. Could you please drop the opencv usage again, please? Thanks, -- Pino ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
