Bug#558847: marked as done (Resolve unresolved symbols in shared libraries)
Your message dated Fri, 04 Jun 2010 06:47:09 + with message-id and subject line Bug#558847: fixed in clxclient 3.6.1-2 has caused the Debian Bug report #558847, regarding Resolve unresolved symbols in shared libraries 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.) -- 558847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clxclient Version: 3.6.1-1 Severity: wishlist User: peter.fritzs...@gmx.de Usertags: unresolved-symbols-so I build all packages some time ago with binutils-gold and your package build without an hard failure, but I noticed that you seems to provide a library in a specific library package so other packages can link against it without problems but your shared object has still some unresolved symbols which the program which links agaomst it must resolve. This isnt a good idea because when you introduce new dependencies the package previously linked against the old version will break because it doesnt know about the new dependency. Maybe you could link against all needed libraries so programs must not link against libraries which it doesnt need to use. Maybe it is related to following bugs which hard failed due to unresolved symbols in programs http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=peter.fritzs...@gmx.de;tag=no-add-needed More informations can be found at http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking dpkg-shlibdeps already showed you the related warnings: dpkg-shlibdeps: warning: symbol _ZN8P_threadC2Ev used by debian/libclxclient3/usr/lib/libclxclient.so.3.6.1 found in none of the libraries. dpkg-shlibdeps: warning: symbol _ZN8P_threadD2Ev used by debian/libclxclient3/usr/lib/libclxclient.so.3.6.1 found in none of the libraries. dpkg-shlibdeps: warning: symbol _ZTI8P_thread used by debian/libclxclient3/usr/lib/libclxclient.so.3.6.1 found in none of the libraries. dpkg-shlibdeps: warning: symbol _ZN8ITC_ip1q9get_eventEj used by debian/libclxclient3/usr/lib/libclxclient.so.3.6.1 found in none of the libraries. dpkg-shlibdeps: warning: symbol _ZN8P_thread9thr_startEiim used by debian/libclxclient3/usr/lib/libclxclient.so.3.6.1 found in none of the libraries. --- End Message --- --- Begin Message --- Source: clxclient Source-Version: 3.6.1-2 We believe that the bug you reported is fixed in the latest version of clxclient, which is due to be installed in the Debian FTP archive: clxclient_3.6.1-2.diff.gz to main/c/clxclient/clxclient_3.6.1-2.diff.gz clxclient_3.6.1-2.dsc to main/c/clxclient/clxclient_3.6.1-2.dsc libclxclient-dev_3.6.1-2_i386.deb to main/c/clxclient/libclxclient-dev_3.6.1-2_i386.deb libclxclient3_3.6.1-2_i386.deb to main/c/clxclient/libclxclient3_3.6.1-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 558...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jaromír Mikeš (supplier of updated clxclient package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 21 May 2010 21:55:58 +0200 Source: clxclient Binary: libclxclient-dev libclxclient3 Architecture: source i386 Version: 3.6.1-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers Changed-By: Jaromír Mikeš Description: libclxclient-dev - Development file for libclxclient libclxclient3 - X Window System C++ access library Closes: 558847 Changes: clxclient (3.6.1-2) unstable; urgency=low . * Reordered control file * Corrected dependency in control file * Bump to Standards-Version: 3.8.4 * Fixing FTBFS on amd64 * Added Homepage field to control file * Fixed symbols in shared libraries (Closes: #558847) * Fixed reference to LGPL-2 in copyright file * Fixing FTBFS on i386 * Added quilt as build dependency * Added patch descriptions * Added README.source file * Added entry for NMU to changelog Checksums-Sha1: 9b9dc545c6c9a7093c9ce8f24b4df048e5c24425 1423 clxclient_3.6.1-2.dsc b53ef51d019a3e22e71ced545cfb4a25b79830da 5999 clxclient_3.6.1-2.diff.gz 5581939d2fe830db51711f464e739e4ed333fdbd 9676 libclxclient-dev_3.6.1-2_i386.deb 49e99f4
clxclient override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): libclxclient-dev_3.6.1-2_i386.deb: package says section is libdevel, override says devel. libclxclient-dev_3.6.1-2_i386.deb: package says priority is optional, override says extra. libclxclient3_3.6.1-2_i386.deb: package says priority is optional, override says extra. Please note that a list of new sections were recently added to the archive: cli-mono, database, debug, fonts, gnu-r, gnustep, haskell, httpd, java, kernel, lisp, localization, ocaml, php, ruby, vcs, video, xfce, zope. At this time a script was used to reclassify packages into these sections. If this is the case, please only reply to this email if the new section is inappropriate, otherwise please update your package at the next upload. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please file a bug against ftp.debian.org and explain why. Please INCLUDE the list of packages as seen above, or we won't be able to deal with your request due to missing information. Please make sure that the subject of the bug you file follows the following format: Subject: override: BINARY1:section/priority, [...], BINARYX:section/priority Include the justification for the change in the body of the mail please. [NB: this is an automatically generated mail; if you already filed a bug and have not received a response yet, please ignore this mail. Your bug needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (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) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
clxclient_3.6.1-2_i386.changes ACCEPTED
Accepted: clxclient_3.6.1-2.diff.gz to main/c/clxclient/clxclient_3.6.1-2.diff.gz clxclient_3.6.1-2.dsc to main/c/clxclient/clxclient_3.6.1-2.dsc libclxclient-dev_3.6.1-2_i386.deb to main/c/clxclient/libclxclient-dev_3.6.1-2_i386.deb libclxclient3_3.6.1-2_i386.deb to main/c/clxclient/libclxclient3_3.6.1-2_i386.deb Override entries for your package: clxclient_3.6.1-2.dsc - source libs libclxclient-dev_3.6.1-2_i386.deb - extra devel libclxclient3_3.6.1-2_i386.deb - extra libs Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 558847 Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of clxclient_3.6.1-2_i386.changes
clxclient_3.6.1-2_i386.changes uploaded successfully to localhost along with the files: clxclient_3.6.1-2.dsc clxclient_3.6.1-2.diff.gz libclxclient-dev_3.6.1-2_i386.deb libclxclient3_3.6.1-2_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#584492: marked as done (yoshimi: Uses -march=native)
Your message dated Fri, 04 Jun 2010 01:47:11 + with message-id and subject line Bug#584492: fixed in yoshimi 0.056-2 has caused the Debian Bug report #584492, regarding yoshimi: Uses -march=native 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.) -- 584492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yoshimi Version: 0.056-1 Severity: grave Hi, There was an error while trying to autobuild your package: [...] > /usr/bin/c++ -DMAX_AD_HARMONICS=128 -DMAX_SUB_HARMONICS=64 > -DPAD_MAX_SAMPLES=64 -DNUM_MIDI_PARTS=16 -DNUM_MIDI_CHANNELS=16 > -DNUM_VOICES=8 -DPOLIPHONY=60 -DNUM_SYS_EFX=4 -DNUM_INS_EFX=8 > -DNUM_PART_EFX=3 -DNUM_KIT_ITEMS=16 -DVELOCITY_MAX_SCALE=8.0 -DMAX_EQ_BANDS=8 > -DMAX_FILTER_STAGES=5 -DFF_MAX_VOWELS=6 -DFF_MAX_FORMANTS=12 > -DFF_MAX_SEQUENCE=8 -DPI=3.1415926536f -DLOG_2=0.693147181f > -DYOSHI_FIFO_DIR=\"/dev/shm\" -DDEFAULT_AUDIO=jack_audio > -DDEFAULT_MIDI=jack_midi -DASM_F2I -g -O2 -O3 -march=native -msse -msse2 > -mfpmath=sse -ffast-math -fomit-frame-pointer > -I/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu > -I/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/src > -I/usr/lib/fltk -I/usr/include/alsa -D'YOSHIMI_VERSION="0.056"' -lasound > -ljack -o CMakeFiles/yoshimi.dir/WidgetPDialUI.cxx.o -c > /build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu/WidgetPDialUI.cxx > cc1plus: error: unrecognized command line option "-march=native" > cc1plus: error: unrecognized command line option "-msse" > cc1plus: error: unrecognized command line option "-msse2" > cc1plus: error: unrecognized command line option "-mfpmath=sse" > make[3]: *** [CMakeFiles/yoshimi.dir/WidgetPDialUI.cxx.o] Error 1 > make[3]: Leaving directory > `/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu' > make[2]: *** [CMakeFiles/yoshimi.dir/all] Error 2 > make[1]: *** [all] Error 2 > dh_auto_build: make -j1 returned exit code 2 > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > make[2]: Leaving directory > `/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu' > make[1]: Leaving directory > `/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu' A full build log can be found at: http://buildd.debian.org/build.php?arch=alpha&pkg=yoshimi&ver=0.056-1 Note that alot of those options you're trying to are not supported on all arches. Using something like -march=native also does not make sense to build packages for a binary distribution. It means that it will not run on older CPUs than the one it was build on, and that clearly is not something we want. Using something like -msse is very likely also a problem for the same reason. Kurt --- End Message --- --- Begin Message --- Source: yoshimi Source-Version: 0.056-2 We believe that the bug you reported is fixed in the latest version of yoshimi, which is due to be installed in the Debian FTP archive: yoshimi-data_0.056-2_all.deb to main/y/yoshimi/yoshimi-data_0.056-2_all.deb yoshimi_0.056-2.debian.tar.gz to main/y/yoshimi/yoshimi_0.056-2.debian.tar.gz yoshimi_0.056-2.dsc to main/y/yoshimi/yoshimi_0.056-2.dsc yoshimi_0.056-2_i386.deb to main/y/yoshimi/yoshimi_0.056-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 584...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alessio Treglia (supplier of updated yoshimi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 Jun 2010 03:14:10 +0200 Source: yoshimi Binary: yoshimi yoshimi-data Architecture: source i386 all Version: 0.056-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers Changed-By: Alessio Treglia Description: yoshimi- A software synthesizer based on ZynAddSubFX yoshimi-data - Presets for Yoshimi Closes: 584492 Changes: yoshimi (0.056-2) unstable; urgency=low . * Add --as-needed to linking options. * Drop GCC options which are not supported on all architectures; only i386 and amd64 support some of them (Closes: #584492). Checksu
yoshimi_0.056-2_i386.changes ACCEPTED
Accepted: yoshimi-data_0.056-2_all.deb to main/y/yoshimi/yoshimi-data_0.056-2_all.deb yoshimi_0.056-2.debian.tar.gz to main/y/yoshimi/yoshimi_0.056-2.debian.tar.gz yoshimi_0.056-2.dsc to main/y/yoshimi/yoshimi_0.056-2.dsc yoshimi_0.056-2_i386.deb to main/y/yoshimi/yoshimi_0.056-2_i386.deb Override entries for your package: yoshimi-data_0.056-2_all.deb - optional sound yoshimi_0.056-2.dsc - source sound yoshimi_0.056-2_i386.deb - optional sound Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 584492 Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of yoshimi_0.056-2_i386.changes
yoshimi_0.056-2_i386.changes uploaded successfully to localhost along with the files: yoshimi_0.056-2.dsc yoshimi_0.056-2.debian.tar.gz yoshimi_0.056-2_i386.deb yoshimi-data_0.056-2_all.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#584492: yoshimi: Uses -march=native
Source: yoshimi Version: 0.056-1 Severity: grave Hi, There was an error while trying to autobuild your package: [...] > /usr/bin/c++ -DMAX_AD_HARMONICS=128 -DMAX_SUB_HARMONICS=64 > -DPAD_MAX_SAMPLES=64 -DNUM_MIDI_PARTS=16 -DNUM_MIDI_CHANNELS=16 > -DNUM_VOICES=8 -DPOLIPHONY=60 -DNUM_SYS_EFX=4 -DNUM_INS_EFX=8 > -DNUM_PART_EFX=3 -DNUM_KIT_ITEMS=16 -DVELOCITY_MAX_SCALE=8.0 -DMAX_EQ_BANDS=8 > -DMAX_FILTER_STAGES=5 -DFF_MAX_VOWELS=6 -DFF_MAX_FORMANTS=12 > -DFF_MAX_SEQUENCE=8 -DPI=3.1415926536f -DLOG_2=0.693147181f > -DYOSHI_FIFO_DIR=\"/dev/shm\" -DDEFAULT_AUDIO=jack_audio > -DDEFAULT_MIDI=jack_midi -DASM_F2I -g -O2 -O3 -march=native -msse -msse2 > -mfpmath=sse -ffast-math -fomit-frame-pointer > -I/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu > -I/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/src > -I/usr/lib/fltk -I/usr/include/alsa -D'YOSHIMI_VERSION="0.056"' -lasound > -ljack -o CMakeFiles/yoshimi.dir/WidgetPDialUI.cxx.o -c > /build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu/WidgetPDialUI.cxx > cc1plus: error: unrecognized command line option "-march=native" > cc1plus: error: unrecognized command line option "-msse" > cc1plus: error: unrecognized command line option "-msse2" > cc1plus: error: unrecognized command line option "-mfpmath=sse" > make[3]: *** [CMakeFiles/yoshimi.dir/WidgetPDialUI.cxx.o] Error 1 > make[3]: Leaving directory > `/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu' > make[2]: *** [CMakeFiles/yoshimi.dir/all] Error 2 > make[1]: *** [all] Error 2 > dh_auto_build: make -j1 returned exit code 2 > make: *** [build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > make[2]: Leaving directory > `/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu' > make[1]: Leaving directory > `/build/buildd-yoshimi_0.056-1-alpha-LunhCW/yoshimi-0.056/obj-alpha-linux-gnu' A full build log can be found at: http://buildd.debian.org/build.php?arch=alpha&pkg=yoshimi&ver=0.056-1 Note that alot of those options you're trying to are not supported on all arches. Using something like -march=native also does not make sense to build packages for a binary distribution. It means that it will not run on older CPUs than the one it was build on, and that clearly is not something we want. Using something like -msse is very likely also a problem for the same reason. Kurt ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
rtmpdump_2.2e-2_i386.changes is NEW
(new) librtmp-dev_2.2e-2_i386.deb extra libdevel toolkit for RTMP streams (development files) A small dumper for media content streamed over the RTMP protocol (like BBC's iPlayer high quality streams). Supplying an rtmp url will result in a dumped flv file, which can be played/transcoded using ffmpeg/mplayer, etc. . This package contains the development libraries, header files needed by programs that want to compile with libvpx. (new) rtmpdump_2.2e-2.diff.gz extra web (new) rtmpdump_2.2e-2.dsc extra web (new) rtmpdump_2.2e-2_i386.deb extra web A small dumper for media content streamed over the RTMP protocol A small dumper for media content streamed over the RTMP protocol (like BBC's iPlayer high quality streams). Supplying an rtmp url will result in a dumped flv file, which can be played/transcoded using ffmpeg/mplayer, etc. (new) rtmpdump_2.2e.orig.tar.gz extra web Changes: rtmpdump (2.2e-2) unstable; urgency=low . * update debian/copyright after consulting upstream . rtmpdump (2.2e-1) unstable; urgency=low . * New upstream release. . rtmpdump (2.2d-1) unstable; urgency=low . * Initial release (Closes: #529974) Override entries for your package: Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 529974 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: RFS: Scenic 0.6.0 - Telepresence software for live performances and installations
Hello! By the way, I will setup a Debian sid box tomorrow... If that can reassure you guys on my sincerity. :) I used to use mainly Debian for at least a year, but got lazy since Ubuntu is so easy - but there's a tradeoff to it. Anyways, back to work! a 2010/6/3 Felipe Sateler : > On Thu, Jun 3, 2010 at 11:59, Alexandre Quessy wrote: > >>> > The binary package is arch: any, but the configure.ac checks for > linux/videodev2.h which I suspect means that the package will only > succesfully compile on Linux architectures. If correct, then the best > would > probably be to fix it upstream to avoid Linux-specific parts when on > non-linux archs, or alternatively to tighten to package only on Linux > archs. > Well, for now, Scenic relies heavily on the GNU/Linux kernel. (For the dc1394 module and V4L2) Should we put something like uclinux-*? >>> >>> I don't know what you mean by uclinux-*. >> >> `dpkg-architecture -L` lists me a whole lot of uclinux-something: >> uclinux-armel >> uclinux-i386 >> uclinux-ia64 >> uclinux-alpha >> uclinux-amd64 >> uclinux-armeb >> uclinux-arm >> uclinux-avr32 >> uclinux-hppa >> uclinux-m32r >> uclinux-m68k >> uclinux-mips >> uclinux-mipsel >> uclinux-powerpc >> uclinux-ppc64 >> uclinux-s390 >> uclinux-s390x >> uclinux-sh3 >> uclinux-sh3eb >> uclinux-sh4 >> uclinux-sh4eb >> uclinux-sparc >> ...that might be the list I am looking for. > > No, thats not it. That is probably linux + uClibc, which is not what > you are after. You could use linux-any in the Architecture field, but > I'm not sure if that really works in practice (last time I heard about > this the buildds did not work correctly). > > Anyway, since this is a new package, you might just want to put > architecture:any and let it fail on unsupported archs. > > -- > > Saludos, > Felipe Sateler > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers > -- Alexandre Quessy http://alexandre.quessy.net/ ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of rtmpdump_2.2e-2_i386.changes
rtmpdump_2.2e-2_i386.changes uploaded successfully to localhost along with the files: rtmpdump_2.2e.orig.tar.gz librtmp-dev_2.2e-2_i386.deb rtmpdump_2.2e-2.dsc rtmpdump_2.2e-2.diff.gz rtmpdump_2.2e-2_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
yoshimi_0.056-1_i386.changes ACCEPTED
Accepted: yoshimi-data_0.056-1_all.deb to main/y/yoshimi/yoshimi-data_0.056-1_all.deb yoshimi_0.056-1.debian.tar.gz to main/y/yoshimi/yoshimi_0.056-1.debian.tar.gz yoshimi_0.056-1.dsc to main/y/yoshimi/yoshimi_0.056-1.dsc yoshimi_0.056-1_i386.deb to main/y/yoshimi/yoshimi_0.056-1_i386.deb yoshimi_0.056.orig.tar.gz to main/y/yoshimi/yoshimi_0.056.orig.tar.gz Override entries for your package: yoshimi-data_0.056-1_all.deb - optional sound yoshimi_0.056-1.dsc - optional sound yoshimi_0.056-1_i386.deb - optional sound Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 581155 Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mplayer packaging branch, ubuntu, updated. debian/1.0.rc3++final-0ubuntu2
On Do, Jun 03, 2010 at 18:41:24 (CEST), Felipe Sateler wrote: > On Thu, Jun 3, 2010 at 12:32, Reinhard Tartler wrote: > # Build architecture-independent packages > binary-indep: install-indep > diff --git a/debian/source/format b/debian/source/format > index d3827e7..163aaf8 100644 > --- a/debian/source/format > +++ b/debian/source/format > @@ -1 +1 @@ > -1.0 > +3.0 (quilt) > diff --git a/debian/source/options b/debian/source/options > new file mode 100644 > index 000..98a0c1a > --- /dev/null > +++ b/debian/source/options > @@ -0,0 +1,2 @@ > +single-debian-patch this fixes the filename of the generated patch. >>> >>> I'm not quite sure this is correct... You already have >>> debian/patches/*. What is your intended purpose with this flag? >> >> ,[From the dpkg-source(1): >> | >> | --single-debian-patch >> | >> | Use debian/patches/debian-changes instead of >> | debian/patches/debian-changes-version for the name of the >> | automatic patch generated during build. This option is >> | particularly useful when the package is maintained in a VCS >> | and a patch set can't reliably be generated. Instead the >> | current diff with upstream should be stored in a single >> | patch. When using this option, it is recommended to create a >> | debian/source/patch-header file explaining how the Debian >> | changes can be best reviewed, for example in the VCS that is >> | used. >> | > > I have already read that, thanks. What I mean is why do you want it > enabled, *if you already have patches in debian/patches*?. In other > words, why is the version suffix not desired? Note that this would > only apply for autogenerated patches (for example, in a NMU). hm. actually, good question. My main motivation was to make the naming not dependent on getting the version number right in debian/changelog. But since those patches are not intended to be committed under this name anyways, this is probably a rather weak argument... -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mplayer packaging branch, ubuntu, updated. debian/1.0.rc3++final-0ubuntu2
On Thu, Jun 3, 2010 at 12:32, Reinhard Tartler wrote: # Build architecture-independent packages binary-indep: install-indep diff --git a/debian/source/format b/debian/source/format index d3827e7..163aaf8 100644 --- a/debian/source/format +++ b/debian/source/format @@ -1 +1 @@ -1.0 +3.0 (quilt) diff --git a/debian/source/options b/debian/source/options new file mode 100644 index 000..98a0c1a --- /dev/null +++ b/debian/source/options @@ -0,0 +1,2 @@ +single-debian-patch >>> >>> this fixes the filename of the generated patch. >> >> I'm not quite sure this is correct... You already have >> debian/patches/*. What is your intended purpose with this flag? > > ,[From the dpkg-source(1): > | > | --single-debian-patch > | > | Use debian/patches/debian-changes instead of > | debian/patches/debian-changes-version for the name of the > | automatic patch generated during build. This option is > | particularly useful when the package is maintained in a VCS > | and a patch set can't reliably be generated. Instead the > | current diff with upstream should be stored in a single > | patch. When using this option, it is recommended to create a > | debian/source/patch-header file explaining how the Debian > | changes can be best reviewed, for example in the VCS that is > | used. > | I have already read that, thanks. What I mean is why do you want it enabled, *if you already have patches in debian/patches*?. In other words, why is the version suffix not desired? Note that this would only apply for autogenerated patches (for example, in a NMU). -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
qtractor 0.4.6-1 MIGRATED to testing
FYI: The status of the qtractor source package in Debian's testing distribution has changed. Previous version: 0.4.5-2 Current version: 0.4.6-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/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mplayer packaging branch, ubuntu, updated. debian/1.0.rc3++final-0ubuntu2
On Do, Jun 03, 2010 at 17:04:56 (CEST), Felipe Sateler wrote: > On Thu, Jun 3, 2010 at 09:26, Reinhard Tartler wrote: >> On Do, Jun 03, 2010 at 15:05:04 (CEST), siret...@users.alioth.debian.org >> wrote: >> >>> +clean: >>> dh_testdir >>> dh_testroot >>> [ ! -f config.mak ] || $(MAKE) distclean >>> dh_clean build-arch-stamp configure-arch-stamp snapshot_version >>> + ! test -d .git || quilt pop -a || test $$? = 2 >> >> This line expects that if we are building in a git repo, that quilt is >> installed on the developer system. I guess this to is a reasonable >> assumption. > > I agree, but may be confusing in the case that it does fail. Maybe a > note in README.source would be useful? good idea. done. >> >>> # Build architecture-independent packages >>> binary-indep: install-indep >>> diff --git a/debian/source/format b/debian/source/format >>> index d3827e7..163aaf8 100644 >>> --- a/debian/source/format >>> +++ b/debian/source/format >>> @@ -1 +1 @@ >>> -1.0 >>> +3.0 (quilt) >>> diff --git a/debian/source/options b/debian/source/options >>> new file mode 100644 >>> index 000..98a0c1a >>> --- /dev/null >>> +++ b/debian/source/options >>> @@ -0,0 +1,2 @@ >>> +single-debian-patch >> >> this fixes the filename of the generated patch. > > I'm not quite sure this is correct... You already have > debian/patches/*. What is your intended purpose with this flag? ,[From the dpkg-source(1): | | --single-debian-patch | | Use debian/patches/debian-changes instead of | debian/patches/debian-changes-version for the name of the | automatic patch generated during build. This option is | particularly useful when the package is maintained in a VCS | and a patch set can't reliably be generated. Instead the | current diff with upstream should be stored in a single | patch. When using this option, it is recommended to create a | debian/source/patch-header file explaining how the Debian | changes can be best reviewed, for example in the VCS that is | used. | ` >> >>> +skip-patches >> >> Does anyone object to this? I hoped that it would have effect on >> building a source package, unfortunately, it has not. > > This options should be applied at extract time. It has no meaning at > build time (patches are never applied when building a source package, > they are stored in the debian.tar.gz). Yeah, that's slightly annoying... -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mplayer packaging branch, ubuntu, updated. debian/1.0.rc3++final-0ubuntu2
On Do, Jun 03, 2010 at 17:08:53 (CEST), Felipe Sateler wrote: > On Thu, Jun 3, 2010 at 09:06, wrote: >> +# Support multiple makes at once >> +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) >> +NUMJOBS = -j$(patsubst parallel=%,%,$(filter >> parallel=%,$(DEB_BUILD_OPTIONS))) >> +else >> +# on i386 and amd64, we query the system unless overriden by >> DEB_BUILD_OPTIONS >> +ifeq ($(DEB_HOST_ARCH),i386) >> +NUMJOBS := -j$(shell getconf _NPROCESSORS_ONLN 2>/dev/null || echo 1) >> +else ifeq ($(DEB_HOST_ARCH),amd64) >> +NUMJOBS := -j$(shell getconf _NPROCESSORS_ONLN 2>/dev/null || echo 1) >> +endif >> +endif >> + > > For this particular case, I think what you actually want is > DEB_BUILD_ARCH. correct. I'll fix this in both the mplayer and ffmpeg package. > However, I'm not sure enabling parallel building by default is a good > idea. There have been no complaints this far and makes building packages on my machines faster. > For example, buildds probably do more than one build at a time. Really? AFAIUI, at least buildd doesn't support this OOTB. I'd rather leave that in until a buildd admin asks us to stop doing that. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: RFS: Scenic 0.6.0 - Telepresence software for live performances and installations
On Thu, Jun 3, 2010 at 11:59, Alexandre Quessy wrote: >> The binary package is arch: any, but the configure.ac checks for linux/videodev2.h which I suspect means that the package will only succesfully compile on Linux architectures. If correct, then the best would probably be to fix it upstream to avoid Linux-specific parts when on non-linux archs, or alternatively to tighten to package only on Linux archs. >>> >>> Well, for now, Scenic relies heavily on the GNU/Linux kernel. (For the >>> dc1394 module and V4L2) Should we put something like uclinux-*? >> >> I don't know what you mean by uclinux-*. > > `dpkg-architecture -L` lists me a whole lot of uclinux-something: > uclinux-armel > uclinux-i386 > uclinux-ia64 > uclinux-alpha > uclinux-amd64 > uclinux-armeb > uclinux-arm > uclinux-avr32 > uclinux-hppa > uclinux-m32r > uclinux-m68k > uclinux-mips > uclinux-mipsel > uclinux-powerpc > uclinux-ppc64 > uclinux-s390 > uclinux-s390x > uclinux-sh3 > uclinux-sh3eb > uclinux-sh4 > uclinux-sh4eb > uclinux-sparc > ...that might be the list I am looking for. No, thats not it. That is probably linux + uClibc, which is not what you are after. You could use linux-any in the Architecture field, but I'm not sure if that really works in practice (last time I heard about this the buildds did not work correctly). Anyway, since this is a new package, you might just want to put architecture:any and let it fail on unsupported archs. -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: RFS: Scenic 0.6.0 - Telepresence software for live performances and installations
Hello again. :) 2010/6/3 Jonas Smedegaard : > Some additional packaging comments: > > The project includes python code. We must then follow to Debian Python > Policy! > > Since the Python code apparently is all handled with GNU autotools I > recommend to include python-autotools.mk (instead of autotools.mk), add the > needed hints to debian/control, and create debian/control.in to help track > CDBS-related build-dependencies. > I must confess that my computers are running Ubuntu Lucid ! I guess I could use git-pbuilder with DIST=sid. I am shopping for a nice virtualization tool to create a sid environment... The problem is that python-autotools.mk is not provided by cdbs on Ubuntu Lucid right now. Maybe I could compile and install it from the sources? > Again, see morituri for an example of this. > > You might find debian/README.source of morituri a useful read - and if you > like it then feel free to adopt if, off course :-) > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQIcBAEBCgAGBQJMB4dyAAoJECx8MUbBoAEhnSwP/iQ7V1/uqi4eYJWSAUQipDZh > RVO0VxxIsH3KlF+0U/RlqU1d0X6/bezBVHEyw5Akt9EXzfIuz8Ukv8jltQRha0Qh > IgW/uBCl3GjuLwIFvisjSsVsTYki/SPQJKxmMFHTCiHZa2r4qEgJHSemZ0Y7dDng > TKeKQ/1mnYrOtowY0iGCN7DnXS74arxVZEGqaH1jhaty+8DaSjbVr1ngz59W82I2 > qcRc2OjphhSDxR0x1sDKFo0ljgde49DI1So5GfK7RoUsM/8ke4AgVCm4eO0pkIEA > +PdR2p1ues4NOVgkaM8COT6dgIvweb8gseoKF45t98MQ3BkTMI27Me3WsN6Sr+1o > 2UW9JDP5bOe9FuNhw3pC5FLBDU6dtoYECNIBriigC6pmqQszDxoQhXCd+mY93uqq > /VGdFV3wVdsOBf5ar5r3a4Zfe+64QLq8aN9KVJdav8i+d9GeGyyLFAnP6tlcoENg > XXTbogPSLwskLomAZGmB9APkLV2MT4ApvPKbehL0EUZ3uFU2nbsek9rLPKxwXfdO > ia04MAUcJtD1qHbdM4xrYYeqhc6/XFlmTrljv0jaFHfyT91/bTkLbCPYFvIA4eSL > a4Z1ZFuZW96aGfn2HX/h2V7nNfWyi8ToIPRZmpqW+I0K+qdHZ9A+5ixa7eigm7ii > c0CVMhwaSfJNhWqWJDxP > =Vb8Q > -END PGP SIGNATURE- > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers > > -- Alexandre Quessy http://alexandre.quessy.net/ ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#582274: Isn't VP8 released as BSD?
On Do, Jun 03, 2010 at 16:22:28 (CEST), Nathan A. Stine wrote: > On Thu, 2010-06-03 at 08:51 +0200, Sebastian Dröge wrote: >> On Wed, 2010-06-02 at 23:10 -0400, Nathan A. Stine wrote: >> > Or so I thought. >> > >> > Diego Biurrun marked it as non-free upstream, but I'd think Debian Legal >> > should take a look at the license to make their own determination. >> >> Well, it's IMHO not non-free (as in not DFSG free) but it's definitely >> GPLv2 incompatible because of the restriction in the patent license >> (interesting here: if they didn't include a patent license nobody >> would've complained although they had no official rights to use the >> patents...). If your software is (L)GPLv2+ or v3 I guess everything is >> fine, if it's LGPLv2 it's probably fine too. >> >> But you're right, Debian Legal should probably look at it as well. I've >> already asked the ftp-masters to give their statement about the license >> and compatibility with other licenses but they didn't answer yet. > > FFmpeg states that it is available under (L)GPL2+. the debian FFmpeg package is distributed under *GPL2*. We do enable important parts (e.g., in libswscale) that are not enable in LGPL mode. GPL3 would make linking other GPL2 only packages problematic. In theory, I guess we could provide an additional LGPL only variant of ffmpeg in some special, non-standard path, but I'm not convinced at all that this will a) helping here and b) worth the trouble. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: RFS: Scenic 0.6.0 - Telepresence software for live performances and installations
Hello! Some updates, since I'm currently working on this... I have to fix the make clean upstream. There are still *.pyc files not cleaned. (fixed) Some files are removed from the dist target. (It will be effective in the next upstream release, which is 0.5.12) There are "_trial_temp" and ".libs" directories which will be cleaned up as well. 2010/6/3 Jonas Smedegaard : > On Wed, Jun 02, 2010 at 10:52:23PM -0400, Alexandre Quessy wrote: >> >> 2010/6/2 Jonas Smedegaard : >>> >>> After a nice meal I now have some comments on your packaging: >>> >>> First of all: Please package using git-buildpackage and upload to the >>> pkg-multimedia repository - more info here: >>> http://wiki.debian.org/DebianMultimedia/DevelopPackaging >>> >> >> Done. Everything seems to be OK, as far as I know. > > Looks ok to me too. You should probably add a debian/gbp.conf file to > ensure pristine-tar is used in the future too. See e.g. morituri package > for an example of that. > Done. I will have to add your license to the copyright of some of the Debian packaging. Actually, git-buildpackage doesn't work anymore with this. I removed it locally... I am missing some point on how to use pristine-tar. It needs the upstream tarball in the parent directory, or so... working on this. > (it is not that morituri is the most excellent package out there, I just > picked one that is tiny and has little unusual stuff - I generally seek to > evolve all packagings that I am invovled in into examples for others to > reuse, so tell me if you want an example of some specific quirk and I'll try > find a package demonstrating it!). > [removed some replied-to text...] > > On a related note, I see that you bumped to debhelper 7. Beware that this > might provide no benefits over debhelper 6, and may make it more difficult > to backport, if you happen to care about that. > I decreased it to version 6. I am not sure that backporting will ever be possible, since Scenic (milhouse) relies on recent versions of GStreamer plugins. We'll see. :) > >>> The binary package is arch: any, but the configure.ac checks for >>> linux/videodev2.h which I suspect means that the package will only >>> succesfully compile on Linux architectures. If correct, then the best would >>> probably be to fix it upstream to avoid Linux-specific parts when on >>> non-linux archs, or alternatively to tighten to package only on Linux archs. >>> >> >> Well, for now, Scenic relies heavily on the GNU/Linux kernel. (For the >> dc1394 module and V4L2) Should we put something like uclinux-*? > > I don't know what you mean by uclinux-*. `dpkg-architecture -L` lists me a whole lot of uclinux-something: uclinux-armel uclinux-i386 uclinux-ia64 uclinux-alpha uclinux-amd64 uclinux-armeb uclinux-arm uclinux-avr32 uclinux-hppa uclinux-m32r uclinux-m68k uclinux-mips uclinux-mipsel uclinux-powerpc uclinux-ppc64 uclinux-s390 uclinux-s390x uclinux-sh3 uclinux-sh3eb uclinux-sh4 uclinux-sh4eb uclinux-sparc ...that might be the list I am looking for. > > What is common to do is to replace "any" in "Architecture: any" with all > known-to-work Debian targets that is supported by the project. > > I dislike such hardcoded lists, however, and prefer to instead > semi-automatically resolve it, either through dependent package (see e.g. > calf for an example of that) or using type-handling (can't find an example > of that right now). > > It does seem, however, from a quick glance, that some parts of the project > is not arch-limited. It might be a good idea to split packaging to provide > most possible to all archs. > That would be nice, but it's probably going to be difficult. The jack-info, dc-ctl and midistream utilities could be packages separately, and should be useful for the multimedia-loving masses. Since scenic relies on milhouse, they could be packaged together. Again, I am a close-to-beginner in packaging, so I am not sure where to start, especially that the current build process is unified and using a single autotools configure.ac script. It would imply splitting it upstream, no? > >>> Either json or simplejson is used upstream. Are you aware that those >>> implementations are not fully interchangeable (one of them - I forgot which >>> - do not follow JSON specs!), and they might be slow too? The Sugar project >>> switched to python-cjson for these reasons. >>> >> >> Ok. Being the main upstream author for the Python in Scenic, I will >> try check if switching to python-cjson is seemless. Note that in the >> Python code, I check if the "json" module is the same as the former >> "simplejson" module. Simplejson is part of the standard Python library >> as "json" since Python 2.6. I could depend on either python >= 2.6 or >> python-simplejson. See http://docs.python.org/library/json.html ... I >> don't know why Python named the module the same name as the former >> json module but replaced it by a new - different one. > > I am no expert in the area. Tell me if you would find it usef
Re: [SCM] mplayer packaging branch, ubuntu, updated. debian/1.0.rc3++final-0ubuntu2
On Thu, Jun 3, 2010 at 09:06, wrote: > +# Support multiple makes at once > +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) > +NUMJOBS = -j$(patsubst parallel=%,%,$(filter > parallel=%,$(DEB_BUILD_OPTIONS))) > +else > +# on i386 and amd64, we query the system unless overriden by > DEB_BUILD_OPTIONS > +ifeq ($(DEB_HOST_ARCH),i386) > +NUMJOBS := -j$(shell getconf _NPROCESSORS_ONLN 2>/dev/null || echo 1) > +else ifeq ($(DEB_HOST_ARCH),amd64) > +NUMJOBS := -j$(shell getconf _NPROCESSORS_ONLN 2>/dev/null || echo 1) > +endif > +endif > + For this particular case, I think what you actually want is DEB_BUILD_ARCH. However, I'm not sure enabling parallel building by default is a good idea. For example, buildds probably do more than one build at a time. -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mplayer packaging branch, ubuntu, updated. debian/1.0.rc3++final-0ubuntu2
On Thu, Jun 3, 2010 at 09:26, Reinhard Tartler wrote: > On Do, Jun 03, 2010 at 15:05:04 (CEST), siret...@users.alioth.debian.org > wrote: > >> +clean: >> dh_testdir >> dh_testroot >> [ ! -f config.mak ] || $(MAKE) distclean >> dh_clean build-arch-stamp configure-arch-stamp snapshot_version >> + ! test -d .git || quilt pop -a || test $$? = 2 > > This line expects that if we are building in a git repo, that quilt is > installed on the developer system. I guess this to is a reasonable > assumption. I agree, but may be confusing in the case that it does fail. Maybe a note in README.source would be useful? > >> # Build architecture-independent packages >> binary-indep: install-indep >> diff --git a/debian/source/format b/debian/source/format >> index d3827e7..163aaf8 100644 >> --- a/debian/source/format >> +++ b/debian/source/format >> @@ -1 +1 @@ >> -1.0 >> +3.0 (quilt) >> diff --git a/debian/source/options b/debian/source/options >> new file mode 100644 >> index 000..98a0c1a >> --- /dev/null >> +++ b/debian/source/options >> @@ -0,0 +1,2 @@ >> +single-debian-patch > > this fixes the filename of the generated patch. I'm not quite sure this is correct... You already have debian/patches/*. What is your intended purpose with this flag? > >> +skip-patches > > Does anyone object to this? I hoped that it would have effect on > building a source package, unfortunately, it has not. This options should be applied at extract time. It has no meaning at build time (patches are never applied when building a source package, they are stored in the debian.tar.gz). > > > -- > Gruesse/greetings, > Reinhard Tartler, KeyID 945348A4 > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers > -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: RFS: Scenic 0.6.0 - Telepresence software for live performances and installations
On Thu, Jun 3, 2010 at 06:23, Jonas Smedegaard wrote: > As a related not, there are several ways to keep track of packaging changes, > common ones being dch+dcommit and git+git-dch. > > Probably the most common one generally in Debian is to make your packaging > change, add a changelog entry using dch, and commit both the actual change > and the changelog update using dcommit. > > I prefer the alternative of making packaging changes, commit the actual > change, and only occationally (and at minimum right before a packaging > release) do a git-dch, maybe adjust the changelog file by hand (e.g. I > prefer to add a newline before bug-closures for improved readability), and > then commit the changelog update separately from the actual code changes. > > One thing I like about that git+git-dch approach is the code changes being > separate, which eases potential later reverts or cherry-picking across > branches. Note that the team policy is to generate the changelog with git-dch at release time, precisely due to cherry-pick and revert ease. This is documented in the wiki page. -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#582274: Isn't VP8 released as BSD?
On Thu, 2010-06-03 at 08:51 +0200, Sebastian Dröge wrote: > On Wed, 2010-06-02 at 23:10 -0400, Nathan A. Stine wrote: > > Or so I thought. > > > > Diego Biurrun marked it as non-free upstream, but I'd think Debian Legal > > should take a look at the license to make their own determination. > > Well, it's IMHO not non-free (as in not DFSG free) but it's definitely > GPLv2 incompatible because of the restriction in the patent license > (interesting here: if they didn't include a patent license nobody > would've complained although they had no official rights to use the > patents...). If your software is (L)GPLv2+ or v3 I guess everything is > fine, if it's LGPLv2 it's probably fine too. > > But you're right, Debian Legal should probably look at it as well. I've > already asked the ftp-masters to give their statement about the license > and compatibility with other licenses but they didn't answer yet. FFmpeg states that it is available under (L)GPL2+. I suppose if the license does meet muster, adding VP8 support would necessarily mean that the entire work would be LGPLv2+ or GPLv3. I wouldn't see how that is a problem. We could just add another build option --enable-gplv3 and put libvpx under it as we do with swscale. Nathan A. Stine ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mplayer packaging branch, ubuntu, updated. debian/1.0.rc3++final-0ubuntu2
On Do, Jun 03, 2010 at 15:05:04 (CEST), siret...@users.alioth.debian.org wrote: > The following commit has been merged in the ubuntu branch: > commit 7a46da8f787ed0f224d3cf851264170edaa0f0cd > Author: Reinhard Tartler > Date: Wed Jun 2 18:07:21 2010 +0200 > > convert to source Format: 3.0 (quilt) FYI, I've now converted the mplayer package in the ubuntu branch to Format 3.0 (quilt). These steps were necessary: > diff --git a/debian/control b/debian/control > index 4d74686..1a16ec5 100644 > --- a/debian/control > +++ b/debian/control > @@ -60,7 +60,6 @@ Build-Depends: debhelper (>= 7), > libxxf86vm-dev, > libvdpau-dev [i386 amd64], > pkg-config, > - quilt, > vstream-client-dev, > x11proto-core-dev, > xsltproc, > diff --git a/debian/rules b/debian/rules > index c9c88c0..953cf73 100755 > --- a/debian/rules > +++ b/debian/rules > @@ -1,7 +1,5 @@ > #!/usr/bin/make -f > > -include /usr/share/quilt/quilt.make > - > # This has to be exported to make some magic below work. > export DH_OPTIONS > > @@ -88,7 +86,7 @@ endif > # https://wiki.ubuntu.com/DistCompilerFlags > CLEAN_ENV=env -u CFLAGS -u CPPFLAGS -u LDFLAGS -u FFLAGS -u CXXFLAGS > > -install-arch: $(QUILT_STAMPFN) > +install-arch: > dh_testdir > dh_prep -a > [ ! -f config.mak ] || $(MAKE) distclean > @@ -133,12 +131,12 @@ install-indep-stamp: > > clean > > -clean: clean-real unpatch > -clean-real: > +clean: > dh_testdir > dh_testroot > [ ! -f config.mak ] || $(MAKE) distclean > dh_clean build-arch-stamp configure-arch-stamp snapshot_version > + ! test -d .git || quilt pop -a || test $$? = 2 This line expects that if we are building in a git repo, that quilt is installed on the developer system. I guess this to is a reasonable assumption. > # Build architecture-independent packages > binary-indep: install-indep > diff --git a/debian/source/format b/debian/source/format > index d3827e7..163aaf8 100644 > --- a/debian/source/format > +++ b/debian/source/format > @@ -1 +1 @@ > -1.0 > +3.0 (quilt) > diff --git a/debian/source/options b/debian/source/options > new file mode 100644 > index 000..98a0c1a > --- /dev/null > +++ b/debian/source/options > @@ -0,0 +1,2 @@ > +single-debian-patch this fixes the filename of the generated patch. > +skip-patches Does anyone object to this? I hoped that it would have effect on building a source package, unfortunately, it has not. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#581748: marked as done (libavcodec52: contains files that are not versioned)
Your message dated Thu, 03 Jun 2010 12:47:46 + with message-id and subject line Bug#581748: fixed in ffmpeg 4:0.5.2-1 has caused the Debian Bug report #581748, regarding libavcodec52: contains files that are not versioned 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.) -- 581748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libavcodec52 Version: 4:0.5.1-3 Severity: wishlist Hi, please move the content of /usr/share/ffmpeg/ to the ffmpeg package. After I reported a file conflict when switching from the official ffmpeg packages to the packages from debian-multimedia.org, Christian Marillat wrote: ... > The ffpreset files are only used by ffmpeg so these files should go > in the ffmpeg packages. ... > A bug report should be filed against the official package. ... Andreas -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (800, 'testing'), (800, 'stable'), (600, 'unstable'), (130, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-0-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libavcodec52 depends on: ii libavutil49 4:0.5.1-3ffmpeg utility library ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libdirac-encoder0 1.0.2-3 open and royalty free high quality ii libfaad22.7-4freeware Advanced Audio Decoder - ii libgsm1 1.0.13-3 Shared libraries for GSM speech co ii libopenjpeg21.3+dfsg-4 JPEG 2000 image compression/decomp ii libschroedinger-1.0-0 1.0.9-2 library for encoding/decoding of D ii libspeex1 1.2~rc1-1The Speex codec runtime library ii libtheora0 1.1.1+dfsg.1-3 The Theora Video Compression Codec ii libvorbis0a 1.3.1-1 The Vorbis General Audio Compressi ii libvorbisenc2 1.3.1-1 The Vorbis General Audio Compressi ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime libavcodec52 recommends no packages. libavcodec52 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: ffmpeg Source-Version: 4:0.5.2-1 We believe that the bug you reported is fixed in the latest version of ffmpeg, which is due to be installed in the Debian FTP archive: ffmpeg-dbg_0.5.2-1_i386.deb to main/f/ffmpeg/ffmpeg-dbg_0.5.2-1_i386.deb ffmpeg-doc_0.5.2-1_all.deb to main/f/ffmpeg/ffmpeg-doc_0.5.2-1_all.deb ffmpeg_0.5.2-1.diff.gz to main/f/ffmpeg/ffmpeg_0.5.2-1.diff.gz ffmpeg_0.5.2-1.dsc to main/f/ffmpeg/ffmpeg_0.5.2-1.dsc ffmpeg_0.5.2-1_i386.deb to main/f/ffmpeg/ffmpeg_0.5.2-1_i386.deb ffmpeg_0.5.2.orig.tar.gz to main/f/ffmpeg/ffmpeg_0.5.2.orig.tar.gz libavcodec-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavcodec-dev_0.5.2-1_i386.deb libavcodec52_0.5.2-1_i386.deb to main/f/ffmpeg/libavcodec52_0.5.2-1_i386.deb libavdevice-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavdevice-dev_0.5.2-1_i386.deb libavdevice52_0.5.2-1_i386.deb to main/f/ffmpeg/libavdevice52_0.5.2-1_i386.deb libavfilter-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavfilter-dev_0.5.2-1_i386.deb libavfilter0_0.5.2-1_i386.deb to main/f/ffmpeg/libavfilter0_0.5.2-1_i386.deb libavformat-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavformat-dev_0.5.2-1_i386.deb libavformat52_0.5.2-1_i386.deb to main/f/ffmpeg/libavformat52_0.5.2-1_i386.deb libavutil-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavutil-dev_0.5.2-1_i386.deb libavutil49_0.5.2-1_i386.deb to main/f/ffmpeg/libavutil49_0.5.2-1_i386.deb libpostproc-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libpostproc-dev_0.5.2-1_i386.deb libpostproc51_0.5.2-1_i386.deb to main/f/ffmpeg/libpostproc51_0.5.2-1_i386.deb libswscale-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libswscale-dev_0.5.2-1_i386.deb libswscale0_0.5.2-1_i386.deb to main/f/ffmpeg/libswscale0_0.5.2-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 581...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reinhard Tartler (supplier of updated ffmpeg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive adminis
ffmpeg_0.5.2-1_i386.changes ACCEPTED
Accepted: ffmpeg-dbg_0.5.2-1_i386.deb to main/f/ffmpeg/ffmpeg-dbg_0.5.2-1_i386.deb ffmpeg-doc_0.5.2-1_all.deb to main/f/ffmpeg/ffmpeg-doc_0.5.2-1_all.deb ffmpeg_0.5.2-1.diff.gz to main/f/ffmpeg/ffmpeg_0.5.2-1.diff.gz ffmpeg_0.5.2-1.dsc to main/f/ffmpeg/ffmpeg_0.5.2-1.dsc ffmpeg_0.5.2-1_i386.deb to main/f/ffmpeg/ffmpeg_0.5.2-1_i386.deb ffmpeg_0.5.2.orig.tar.gz to main/f/ffmpeg/ffmpeg_0.5.2.orig.tar.gz libavcodec-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavcodec-dev_0.5.2-1_i386.deb libavcodec52_0.5.2-1_i386.deb to main/f/ffmpeg/libavcodec52_0.5.2-1_i386.deb libavdevice-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavdevice-dev_0.5.2-1_i386.deb libavdevice52_0.5.2-1_i386.deb to main/f/ffmpeg/libavdevice52_0.5.2-1_i386.deb libavfilter-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavfilter-dev_0.5.2-1_i386.deb libavfilter0_0.5.2-1_i386.deb to main/f/ffmpeg/libavfilter0_0.5.2-1_i386.deb libavformat-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavformat-dev_0.5.2-1_i386.deb libavformat52_0.5.2-1_i386.deb to main/f/ffmpeg/libavformat52_0.5.2-1_i386.deb libavutil-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libavutil-dev_0.5.2-1_i386.deb libavutil49_0.5.2-1_i386.deb to main/f/ffmpeg/libavutil49_0.5.2-1_i386.deb libpostproc-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libpostproc-dev_0.5.2-1_i386.deb libpostproc51_0.5.2-1_i386.deb to main/f/ffmpeg/libpostproc51_0.5.2-1_i386.deb libswscale-dev_0.5.2-1_i386.deb to main/f/ffmpeg/libswscale-dev_0.5.2-1_i386.deb libswscale0_0.5.2-1_i386.deb to main/f/ffmpeg/libswscale0_0.5.2-1_i386.deb Override entries for your package: ffmpeg-dbg_0.5.2-1_i386.deb - extra debug ffmpeg-doc_0.5.2-1_all.deb - optional doc ffmpeg_0.5.2-1.dsc - source video ffmpeg_0.5.2-1_i386.deb - optional video libavcodec-dev_0.5.2-1_i386.deb - optional libdevel libavcodec52_0.5.2-1_i386.deb - optional libs libavdevice-dev_0.5.2-1_i386.deb - optional libdevel libavdevice52_0.5.2-1_i386.deb - optional libs libavfilter-dev_0.5.2-1_i386.deb - optional libdevel libavfilter0_0.5.2-1_i386.deb - optional libs libavformat-dev_0.5.2-1_i386.deb - optional libdevel libavformat52_0.5.2-1_i386.deb - optional libs libavutil-dev_0.5.2-1_i386.deb - optional libdevel libavutil49_0.5.2-1_i386.deb - optional libs libpostproc-dev_0.5.2-1_i386.deb - optional libdevel libpostproc51_0.5.2-1_i386.deb - optional libs libswscale-dev_0.5.2-1_i386.deb - optional libdevel libswscale0_0.5.2-1_i386.deb - optional libs Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 581748 Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of ffmpeg_0.5.2-1_i386.changes
ffmpeg_0.5.2-1_i386.changes uploaded successfully to localhost along with the files: ffmpeg_0.5.2-1.dsc ffmpeg_0.5.2.orig.tar.gz ffmpeg_0.5.2-1.diff.gz ffmpeg_0.5.2-1_i386.deb ffmpeg-dbg_0.5.2-1_i386.deb ffmpeg-doc_0.5.2-1_all.deb libavutil49_0.5.2-1_i386.deb libavcodec52_0.5.2-1_i386.deb libavdevice52_0.5.2-1_i386.deb libavformat52_0.5.2-1_i386.deb libavfilter0_0.5.2-1_i386.deb libpostproc51_0.5.2-1_i386.deb libswscale0_0.5.2-1_i386.deb libavutil-dev_0.5.2-1_i386.deb libavcodec-dev_0.5.2-1_i386.deb libavdevice-dev_0.5.2-1_i386.deb libavformat-dev_0.5.2-1_i386.deb libavfilter-dev_0.5.2-1_i386.deb libpostproc-dev_0.5.2-1_i386.deb libswscale-dev_0.5.2-1_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
rtmpdump_2.2e-1_i386.changes REJECTED
Hi maintainer! librtmp/* seems to be licensed under the terms of the LGPL 2.1+. Please add that to your copyright file. Best regards, Alexander === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: RFS: Scenic 0.6.0 - Telepresence software for live performances and installations
Some additional packaging comments: The project includes python code. We must then follow to Debian Python Policy! Since the Python code apparently is all handled with GNU autotools I recommend to include python-autotools.mk (instead of autotools.mk), add the needed hints to debian/control, and create debian/control.in to help track CDBS-related build-dependencies. Again, see morituri for an example of this. You might find debian/README.source of morituri a useful read - and if you like it then feel free to adopt if, off course :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: RFS: Scenic 0.6.0 - Telepresence software for live performances and installations
On Wed, Jun 02, 2010 at 10:52:23PM -0400, Alexandre Quessy wrote: 2010/6/2 Jonas Smedegaard : After a nice meal I now have some comments on your packaging: First of all: Please package using git-buildpackage and upload to the pkg-multimedia repository - more info here: http://wiki.debian.org/DebianMultimedia/DevelopPackaging Done. Everything seems to be OK, as far as I know. Looks ok to me too. You should probably add a debian/gbp.conf file to ensure pristine-tar is used in the future too. See e.g. morituri package for an example of that. (it is not that morituri is the most excellent package out there, I just picked one that is tiny and has little unusual stuff - I generally seek to evolve all packagings that I am invovled in into examples for others to reuse, so tell me if you want an example of some specific quirk and I'll try find a package demonstrating it!). I pushed my changes again to alioth. Should I update the vesion number to 0.5.11-2 now? I know that when it's ready to upload we should keep only the last entry - with the "Initial packaging" message - closing the ITP bug. Generally for all Debian packaging we should bump the release number only when actually releasing as packaging in Debian. So the answer is "No!". As a related not, there are several ways to keep track of packaging changes, common ones being dch+dcommit and git+git-dch. Probably the most common one generally in Debian is to make your packaging change, add a changelog entry using dch, and commit both the actual change and the changelog update using dcommit. I prefer the alternative of making packaging changes, commit the actual change, and only occationally (and at minimum right before a packaging release) do a git-dch, maybe adjust the changelog file by hand (e.g. I prefer to add a newline before bug-closures for improved readability), and then commit the changelog update separately from the actual code changes. One thing I like about that git+git-dch approach is the code changes being separate, which eases potential later reverts or cherry-picking across branches. Another related note is how to handle Debian-based non-Debian packaging releases. I prefer to treat Debian as the master, do variations off of that, and not include "noise" from derived packaging in the main Debian branch. If I borrow from e.g. an Ubuntu packaging not done by myself, then I cherry-pick the actual packaging code changes but do not preserve the derived changelog entries: Debian IMO have no use of documenting version numbers not ever being released in a Debian context! Long descriptions should be line-wrapped at 72 chars. Done. (I thought it was 80) The classic terminal width is 80 chars. A common line-wrapping length is 72 chars to leave some chars for e.g. quoting in MUAs. So yes, I wouldnt be surprised if the Debian Policy limit is 80 chars, but I will nevertheless still recommend to use 72 chars in reality :-) It is bad style to invoke dh_install again (in addition to the included debhelper.mk snippet). Instead either add a debian/scenic.install file, or set DEB_DH_INSTALL_ARGS. I am not sure where you found this. Was it in scenic 0.5.10-2? I am now editing starting from 0.5.11-1, in which I can't find any dh_install. Yes, I looked at the packaging that you originally provided a URL for, which indeed was 0.5.10-2. Now we are both tracking same Git and you are right, it is gone :-) Are you sure you need to build-depend on bash-completion? No. :) Removed it. I assume the /etc/bash_completion.d/ directory will be created? If not, I should create it? Yes, in my experience underlying directories are automagically created when installing files through debhelper. Not sure what version of debhelper started doing so, but I am pretty confident that at least version 5 is safe. On a related note, I see that you bumped to debhelper 7. Beware that this might provide no benefits over debhelper 6, and may make it more difficult to backport, if you happen to care about that. The binary package is arch: any, but the configure.ac checks for linux/videodev2.h which I suspect means that the package will only succesfully compile on Linux architectures. If correct, then the best would probably be to fix it upstream to avoid Linux-specific parts when on non-linux archs, or alternatively to tighten to package only on Linux archs. Well, for now, Scenic relies heavily on the GNU/Linux kernel. (For the dc1394 module and V4L2) Should we put something like uclinux-*? I don't know what you mean by uclinux-*. What is common to do is to replace "any" in "Architecture: any" with all known-to-work Debian targets that is supported by the project. I dislike such hardcoded lists, however, and prefer to instead semi-automatically resolve it, either through dependent package (see e.g. calf for an example of that) or using type-handling (can't find an example o
ardour_2.8.9-1_amd64.changes ACCEPTED
Accepted: ardour_2.8.9-1.debian.tar.gz to main/a/ardour/ardour_2.8.9-1.debian.tar.gz ardour_2.8.9-1.dsc to main/a/ardour/ardour_2.8.9-1.dsc ardour_2.8.9-1_amd64.deb to main/a/ardour/ardour_2.8.9-1_amd64.deb ardour_2.8.9.orig.tar.bz2 to main/a/ardour/ardour_2.8.9.orig.tar.bz2 Override entries for your package: ardour_2.8.9-1.dsc - source sound ardour_2.8.9-1_amd64.deb - optional sound Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Request to join the team
On Wed, Jun 2, 2010 at 6:00 PM, Andrew Gee wrote: > My alioth username is andrewgee-guest. Please request to join the project [1] on Alioth then I'll add you to the team. [1] https://alioth.debian.org/projects/pkg-multimedia/ -- Alessio Treglia Debian & Ubuntu Developer | Homepage: http://www.alessiotreglia.com 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Hey Adi, Here we go again... Ardour 2.8.9 released!
On Wed, Jun 02, 2010 at 07:14:41PM -0700, i...@bandshed.net wrote: > Hi again Adrian, Hi! > Apparently the mute button issue has now been corrected in the source > code and they have an updated release. Thanks again!! Uploaded. HTH -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of ardour_2.8.9-1_amd64.changes
ardour_2.8.9-1_amd64.changes uploaded successfully to localhost along with the files: ardour_2.8.9-1.dsc ardour_2.8.9.orig.tar.bz2 ardour_2.8.9-1.debian.tar.gz ardour_2.8.9-1_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of ardour_2.8.9-1_amd64.changes
ardour_2.8.9-1_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: ardour_2.8.9-1.dsc ardour_2.8.9.orig.tar.bz2 ardour_2.8.9-1.debian.tar.gz ardour_2.8.9-1_amd64.deb Greetings, Your Debian queue daemon (running on host kassia.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#584319: marked as done (ffmpeg from experimental uninstallable: trying to overwrite file)
Your message dated Thu, 03 Jun 2010 10:27:38 +0300 with message-id <4c07596a.4040...@gmail.com> and subject line Re: Bug#584319: Acknowledgement (ffmpeg from experimental uninstallable: trying to overwrite file) has caused the Debian Bug report #584319, regarding ffmpeg from experimental uninstallable: trying to overwrite file 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.) -- 584319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ffmpeg Version: 4:0.5.1-3 Severity: normal Tags: experimental Preparing to replace libavdevice-dev 4:0.5.1-3 (using .../libavdevice-dev_4%3a0.6~svn20100505-1_amd64.deb) ... Unpacking replacement libavdevice-dev ... Preparing to replace ffmpeg 4:0.5.1-3 (using .../ffmpeg_4%3a0.6~svn20100505-1_amd64.deb) ... Unpacking replacement ffmpeg ... dpkg: error processing /var/cache/apt/archives/ffmpeg_4%3a0.6~svn20100505-1_amd64.deb (--unpack): trying to overwrite '/usr/share/ffmpeg/libx264-lossless_slow.ffpreset', which is also in package libavcodec52 4:0.5.1-3 dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/ffmpeg_4%3a0.6~svn20100505-1_amd64.deb This happens when running this command: $ apt-get install ffmpeg -t experimental Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libavcodec-dev libavcodec52 libavdevice-dev libavdevice52 libavfilter1 libavformat-dev libavformat52 libavutil-dev libpostproc-dev libpostproc51 libswscale-dev libswscale0 Suggested packages: libfaad-dev The following packages will be REMOVED: libavfilter0 The following NEW packages will be installed: libavfilter1 The following packages will be upgraded: ffmpeg libavcodec-dev libavcodec52 libavdevice-dev libavdevice52 libavformat-dev libavformat52 libavutil-dev libpostproc-dev libpostproc51 libswscale-dev libswscale0 12 upgraded, 1 newly installed, 1 to remove and 648 not upgraded. Upgrading libavcodec52 to the version in experimental is not possible either: apt-get install libavcodec52 -t experimental Reading package lists... Done Building dependency tree Reading state information... Done You might want to run `apt-get -f install' to correct these: The following packages have unmet dependencies: ffmpeg: Depends: libavcodec52 (< 4:0.5.1-99) but 4:0.6~svn20100505-1 is to be installed or libavcodec-extra-52 (< 4:0.5.1-99) but it is not installable -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-00179-gdebb980 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ffmpeg depends on: ii libavcodec52 4:0.5.1-3 ffmpeg codec library pn libavdevice52 | libavdevice-e (no description available) ii libavfilter0 4:0.5.1-3 ffmpeg video filtering library pn libavformat52 | libavformat-e (no description available) ii libavutil49 4:0.5.1-3 ffmpeg utility library ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib pn libpostproc51 | libpostproc-e (no description available) ii libsdl1.2debian 1.2.14-6 Simple DirectMedia Layer pn libswscale0 | libswscale-extr (no description available) ffmpeg recommends no packages. ffmpeg suggests no packages. -- no debconf information -- debsums errors found: prelink: /usr/bin/ffplay: at least one of file's dependencies has changed since prelinking debsums: changed file /usr/bin/ffplay (from ffmpeg package) prelink: /usr/bin/ffserver: at least one of file's dependencies has changed since prelinking debsums: changed file /usr/bin/ffserver (from ffmpeg package) prelink: /usr/bin/ffmpeg: at least one of file's dependencies has changed since prelinking debsums: changed file /usr/bin/ffmpeg (from ffmpeg package) --- End Message --- --- Begin Message --- Actually I fixed this by completely removing ffmpeg and reinstalling: apt-get -f install (removed ffmpeg and everything related) Then apt-get install ffmpeg -t experimental installed the proper version of packages. Look like simply selecting ffmpeg 'force version' from synaptic installed some incompatible set of packages? --Edwin --- End Message ---
Bug#584319: ffmpeg from experimental uninstallable: trying to overwrite file
Package: ffmpeg Version: 4:0.5.1-3 Severity: normal Tags: experimental Preparing to replace libavdevice-dev 4:0.5.1-3 (using .../libavdevice-dev_4%3a0.6~svn20100505-1_amd64.deb) ... Unpacking replacement libavdevice-dev ... Preparing to replace ffmpeg 4:0.5.1-3 (using .../ffmpeg_4%3a0.6~svn20100505-1_amd64.deb) ... Unpacking replacement ffmpeg ... dpkg: error processing /var/cache/apt/archives/ffmpeg_4%3a0.6~svn20100505-1_amd64.deb (--unpack): trying to overwrite '/usr/share/ffmpeg/libx264-lossless_slow.ffpreset', which is also in package libavcodec52 4:0.5.1-3 dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/ffmpeg_4%3a0.6~svn20100505-1_amd64.deb This happens when running this command: $ apt-get install ffmpeg -t experimental Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libavcodec-dev libavcodec52 libavdevice-dev libavdevice52 libavfilter1 libavformat-dev libavformat52 libavutil-dev libpostproc-dev libpostproc51 libswscale-dev libswscale0 Suggested packages: libfaad-dev The following packages will be REMOVED: libavfilter0 The following NEW packages will be installed: libavfilter1 The following packages will be upgraded: ffmpeg libavcodec-dev libavcodec52 libavdevice-dev libavdevice52 libavformat-dev libavformat52 libavutil-dev libpostproc-dev libpostproc51 libswscale-dev libswscale0 12 upgraded, 1 newly installed, 1 to remove and 648 not upgraded. Upgrading libavcodec52 to the version in experimental is not possible either: apt-get install libavcodec52 -t experimental Reading package lists... Done Building dependency tree Reading state information... Done You might want to run `apt-get -f install' to correct these: The following packages have unmet dependencies: ffmpeg: Depends: libavcodec52 (< 4:0.5.1-99) but 4:0.6~svn20100505-1 is to be installed or libavcodec-extra-52 (< 4:0.5.1-99) but it is not installable -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-00179-gdebb980 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ffmpeg depends on: ii libavcodec52 4:0.5.1-3 ffmpeg codec library pn libavdevice52 | libavdevice-e (no description available) ii libavfilter0 4:0.5.1-3 ffmpeg video filtering library pn libavformat52 | libavformat-e (no description available) ii libavutil49 4:0.5.1-3 ffmpeg utility library ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib pn libpostproc51 | libpostproc-e (no description available) ii libsdl1.2debian 1.2.14-6 Simple DirectMedia Layer pn libswscale0 | libswscale-extr (no description available) ffmpeg recommends no packages. ffmpeg suggests no packages. -- no debconf information -- debsums errors found: prelink: /usr/bin/ffplay: at least one of file's dependencies has changed since prelinking debsums: changed file /usr/bin/ffplay (from ffmpeg package) prelink: /usr/bin/ffserver: at least one of file's dependencies has changed since prelinking debsums: changed file /usr/bin/ffserver (from ffmpeg package) prelink: /usr/bin/ffmpeg: at least one of file's dependencies has changed since prelinking debsums: changed file /usr/bin/ffmpeg (from ffmpeg package) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
