Bug#850446: handbrake: New upstream release 1.0.1
Sebastian Ramacher wrote: > The patch is in the process of being upstreamed: > https://mailman.videolan.org/pipermail/libbluray-devel/2016-December/002518.html Thanks for the pointer! So, let's just delay the packaging of handbrake 1.x until this new libbluray has entered unstable. I could push what I already have to the git repo, although that's really nothing fancy. - 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
Bug#850771: include doc/keys.en.html in binary package
Package: inkscape Version: 0.92.0-2 Severity: wishlist The Inkscape "Help" menu needs internet access to work. This is annoying for airgapped users. IIRC most of the menu items link to non-DFSG content, but one menu item is easy to fix: inkscape_help_keys.inx. The inkscape source package contains the same content: -rw-r--r-- 0/0 4250 inkscape-0.92.0/doc/keys.css -rw-r--r-- 0/0381998 inkscape-0.92.0/doc/keys.be.html -rw-r--r-- 0/0351116 inkscape-0.92.0/doc/keys.de.html -rw-r--r-- 0/0389980 inkscape-0.92.0/doc/keys.el.html -rw-r--r-- 0/083 inkscape-0.92.0/doc/keys.en.html -rw-r--r-- 0/0351169 inkscape-0.92.0/doc/keys.fr.html -rw-r--r-- 0/0356171 inkscape-0.92.0/doc/keys.ja.html -rw-r--r-- 0/0335584 inkscape-0.92.0/doc/keys.zh_TW.html Please install these somewhere like file:///usr/share/doc/inkscape/html/ or file:///usr/share/inkscape/doc/html/, and patch inkscape_help_keys.inx to point to them instead of http://inkscape.org/doc/keys092.html. UPDATE: one problem I hadn't considered is language detection. I presume the HTTP version does this via Accept-Language[0]. The keys.*.html files don't link to one another, so inkscape_help_keys.inx or launch_webbrowser.py might need to be extended provide equivalent functionality based on $LANG? [0] https://en.wikipedia.org/wiki/Content_negotiation PS: the keys.*.html in inkscape are copied from the separate inkscape-docs package (not in Debian). Packaging that might be a better approach, I dunno. At a glance, everything in it appears to be synced into the normal inkscape source tarball: http://bazaar.launchpad.net/~inkscape.dev/inkscape-docs/trunk/files/ ___ 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: libopenmpt modplug compat in Debian
Hi, On 01/09/2017 11:59 PM, James Cowgill wrote: Lionel found (and he may be able to expand on this) a large number of potential security bugs in libmodplug recently which have not yet been fixed. To try and improve the security situation of various package in Debian, he requested that the security team start to move packages away from libmodplug. From this Moritz (security team member) concluded that widely used packages (like gstreamer and VLC) cannot use libmodplug at all in stretch. The suggestion was to use the libopenmpt modplug compatibility layer as a "free" way to fix this since it would require no code changes to the affected packages. I'm guessing it was just a coincidence that Johannes raised the issue with me the previous week. That's the context I was missing, thanks for explanation. So, I gather the plan here is to re-link VLC and gstreamer (and maybe others) against the libopenmpt modplug compat layer for Stretch, right? Given the time pressure, that choice appears logical now. ffmpeg already has native libopenmpt support. I'll refer to the 2 different ways of packaging the libopenmpt libmodplug compat layer as per [2]. While option 1 is surely the safe choice, it is probably also rather useless in general. The chances of programs opting in to use libopenmpt instead of libmodplug is probably zero. After all, neither the libmodplug nor the libopenmpt API is that complicated at all. It probably only takes some hours to convert existing code from one to the other, which programs which actually want to switch could do easily. I do not expect it to matter much at all whether the compat layer gets included this way in Stretch or not. I agree that in the long run it isn't the best option, but it is the easiest way to keep functionality for Stretch. If the relevant packages can be ported in time for Stretch (you have maybe 2 weeks at the most) that's great, but if they can't be then this can be used as a fallback. I also don't see many downsides in making the compat layer available for use (even if nothing uses it) especially given that I've already packaged it! Well, the only "real" downside may be that something might start actually depending on it. Especially, I would rather not want to see any upstream projects integrating support for linking the libopenmpt modplug compat layer instead of porting to the libopenmpt API. Option 2 has of course risks associated with it. Please see the comment at the top of libopenmpt_modplug_cpp.cpp [3]. While, to the best of my knowledge, libopenmpt emulates the libmodplug C API/ABI completely and 100% compatible (it ignores DSP post-processing effects though, libopenmpt just does not include the corresponding code, and misses some other (almost certainly irrelevant) features (see the FAQ [4])), emulating the C++ API is in a really hacky state. Thus, personally, I'd feel rather uneasy if Debian is going to rely on that in any package at all (to my knowledge, the original xmms-modplug plugin and the libmodplug gstreamer plugin are using the C++ API, but there might also be other users). I think the problem with option 2 is that it requires checking every package which uses libmodplug to see if it works properly with the compat layer (as opposed to a few packages using option 1). Having 2 packages providing the same library also complicates things. I see. For Buster, I think we should completely replace libmodplug with the libopenmpt compatibility layer while at the same time trying to port as much stuff away from the libmodplug api as possible. It's too late to do that for Stretch though. Longer term, there already exists a gstreamer plugin using libopenmpt in the gst-nonstream-audio project [6] , which IMHO should be much preferred to using the existing libmodplug gstreamer plugin with the libopenmpt libmodplug compat layer. This is a good idea for Buster. So, at least for Buster, the overall plan seems clear ;) Regards, Jörn ___ 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: libopenmpt modplug compat in Debian
Hi, On 09/01/17 20:44, Jörn Heusipp wrote: > Hello > > CCing James Cowgill and Stephen Kitt (Debian libmodplug maintainer) > > On 01/09/2017 05:05 PM, Lionel Debroux wrote: > >> James Cowgill uploaded an update to the existing Debian openmpt source >> package, containing the libmodplug compat layer. At the time of this >> writing, it's still "NEW" ( https://ftp-master.debian.org/new.html ), >> but it should transition into unstable well in time for the hard freeze >> of Stretch. And even if it didn't, chances are that the security team >> will insist for the libmodplug compat layer to become available in >> Stretch, per the discussion I started several days ago... > > What was that discussion about? > Is it available in public (quick googling did only turn up [1] and [2] > regarding libopenmpt and Debian). It wasn't CCed to any public mailing lists. My (hopefully accurate) summary of it: Lionel found (and he may be able to expand on this) a large number of potential security bugs in libmodplug recently which have not yet been fixed. To try and improve the security situation of various package in Debian, he requested that the security team start to move packages away from libmodplug. From this Moritz (security team member) concluded that widely used packages (like gstreamer and VLC) cannot use libmodplug at all in stretch. The suggestion was to use the libopenmpt modplug compatibility layer as a "free" way to fix this since it would require no code changes to the affected packages. I'm guessing it was just a coincidence that Johannes raised the issue with me the previous week. > I'll refer to the 2 different ways of packaging the libopenmpt > libmodplug compat layer as per [2]. > > While option 1 is surely the safe choice, it is probably also rather > useless in general. The chances of programs opting in to use libopenmpt > instead of libmodplug is probably zero. After all, neither the > libmodplug nor the libopenmpt API is that complicated at all. It > probably only takes some hours to convert existing code from one to the > other, which programs which actually want to switch could do easily. I > do not expect it to matter much at all whether the compat layer gets > included this way in Stretch or not. I agree that in the long run it isn't the best option, but it is the easiest way to keep functionality for Stretch. If the relevant packages can be ported in time for Stretch (you have maybe 2 weeks at the most) that's great, but if they can't be then this can be used as a fallback. I also don't see many downsides in making the compat layer available for use (even if nothing uses it) especially given that I've already packaged it! > Option 2 has of course risks associated with it. Please see the comment > at the top of libopenmpt_modplug_cpp.cpp [3]. While, to the best of my > knowledge, libopenmpt emulates the libmodplug C API/ABI completely and > 100% compatible (it ignores DSP post-processing effects though, > libopenmpt just does not include the corresponding code, and misses some > other (almost certainly irrelevant) features (see the FAQ [4])), > emulating the C++ API is in a really hacky state. Thus, personally, I'd > feel rather uneasy if Debian is going to rely on that in any package at > all (to my knowledge, the original xmms-modplug plugin and the > libmodplug gstreamer plugin are using the C++ API, but there might also > be other users). I think the problem with option 2 is that it requires checking every package which uses libmodplug to see if it works properly with the compat layer (as opposed to a few packages using option 1). Having 2 packages providing the same library also complicates things. For Buster, I think we should completely replace libmodplug with the libopenmpt compatibility layer while at the same time trying to port as much stuff away from the libmodplug api as possible. It's too late to do that for Stretch though. > Also, from my outside view on the security implications of libmodplug, > the situation is probably not worse for the next Debian release than it > already was for the last release. That doesn't mean that we shouldn't try to improve the situation for Stretch :) > Same as already discussed by James and Johannes, I can also see some use > in actually having the compat layer included in Debian, but that use > probably only exists for users if they can actually switch between > original libmodplug and the libopenmpt compat layer by > installing/uninstalling the appropriate packages. That will only work > with option 2 and the two packages conflicting with each other (as I had > outlined in the documentation at [5] already). I do not follow Debian > development closely, but as far as I understand, it's probably way way > too late for that to be implemented in Stretch. Yes I think so. > Longer term, there already exists a gstreamer plugin using libopenmpt in > the gst-nonstream-audio project [6] , which IMHO should be much > preferred to using the exis
Re: Ardour auto removal from testing
2017-01-09 15:24 GMT+01:00 IOhannes m zmölnig (Debian/GNU) : > On 2017-01-09 13:34, Jaromír Mikeš wrote: >> We should also tighten B-D to libfftw3-dev (>= 3.3.5-3~) I guess ... > > i'm not entirely sure whether we should. > generally i find it not a good idea to tighten (Build-)Dependencies to > work around bugs in the dependent pacakges. > specifically i want to keep ardour in Debian though. > > otoh, #850482 should fix this automatically. Ok let's wait for binNMU ;) mira ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Horse Mackerels / Jurel / Chinchard
[ View in browser ]( http://r.newsletter.bonescamail.nl/pr33qdsuoatrf.html ) Coming weeks Special Promotion: Atlantic Horse Mackerels / Scad / Chinchard / Jurel / Kote / Thomson / Stravid Seif / Assatat / Sarun / Sauro / Sawrella / 竹筴魚 / Cá Sòng tra Carapau / Kawre / Likouanga / Nengho / Liouolo 1 box (20 kilo) € 1,39 10 boxes € 1,29 1 palet (48 box) € 1,19 5 palets (240 box) € 21,80/box = € 1,09 per kilo!! Origin: Ireland FAO27 Size: 60 - 65 pieces per 20 kilo box (every box has some overweight) Meat: Oil-rich, high levels of healthy omega-3 fatty acids. Bones: Few and easy to remove. Scales: Mostly easy to remove with a knife. This email was sent to pkg-multimedia-maintainers@lists.alioth.debian.org You received this email because you are registered with Bonesca Import en Export BV [ Unsubscribe here ]( http://r.newsletter.bonescamail.nl/pr33qdsuoatrg.html ) Sent by [ ]( http://r.newsletter.bonescamail.nl/2v0cexj71aoatrd.html ) © 2017 Bonesca Import en Export BV ___ 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#847988: pd-libdir: does not respect current loader path
yes, I'll happily review your fix. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
libopenshot-audio_0.1.2+ds1-1_amd64.changes is NEW
binary:libopenshot-audio-dev is NEW. binary:libopenshot-audio-doc is NEW. binary:libopenshot-audio3 is NEW. binary:libopenshot-audio-dev is NEW. binary:libopenshot-audio-doc is NEW. binary:libopenshot-audio3 is NEW. source:libopenshot-audio is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
libopenshot_0.1.2+ds1-1_amd64.changes is NEW
binary:libopenshot-dev is NEW. binary:libopenshot-doc is NEW. binary:libopenshot9 is NEW. binary:python3-openshot is NEW. binary:libopenshot-doc is NEW. binary:python3-openshot is NEW. binary:libopenshot-dev is NEW. binary:libopenshot9 is NEW. source:libopenshot is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
liblrdf_0.6.1-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 09 Jan 2017 19:50:09 +0100 Source: liblrdf Binary: liblrdf0-dev liblrdf0 Architecture: source amd64 Version: 0.6.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Jonas Smedegaard Description: liblrdf0 - library to manipulate RDF files describing LADSPA plugins liblrdf0-dev - liblrdf0 development files Changes: liblrdf (0.6.1-1) unstable; urgency=medium . [ upstream ] * New release. . [ Jonas Smedegaard ] * Update copyright info: + Stop track autotools files: No longer included upstream. * Update package relations: + Fix stop bogusly build-depend on autotools-dev. Checksums-Sha1: 3cb210968886e97b6c851746290bf4a5572c3ffe 2095 liblrdf_0.6.1-1.dsc 898440c3f4c6b2714eb4ff5d268dfcc32b180b0a 43878 liblrdf_0.6.1.orig.tar.gz 31e573ea571696cc8c21e40821a6a575ce761950 8508 liblrdf_0.6.1-1.debian.tar.xz e09214b5bd904fe672b4db4488c892a343bcc737 26770 liblrdf0-dbgsym_0.6.1-1_amd64.deb 9307b4cc5ed90bf3e35f2650e3a5b2171486636d 25384 liblrdf0-dev_0.6.1-1_amd64.deb 3fad963f71589b49ca797d94e8fe070e59ce14ff 24526 liblrdf0_0.6.1-1_amd64.deb 29c1b51beeaaafbbb6f33cde307a307071a82afa 7542 liblrdf_0.6.1-1_amd64.buildinfo Checksums-Sha256: cdd4f0815883059d73edeec8370f7fe8a6a4ead61c0054605fb88efbeccbb21a 2095 liblrdf_0.6.1-1.dsc d579417c477ac3635844cd1b94f273ee2529a8c3b6b21f9b09d15f462b89b1ef 43878 liblrdf_0.6.1.orig.tar.gz 4ba813c9abec18e74280bae4cfe05a75147fa0a458a0c4eed49e75e517ad7e69 8508 liblrdf_0.6.1-1.debian.tar.xz 0af5b5c0fecb9d8833a7b8ab6534c00bff17031b2f5e5125c96e66a4bdbc844a 26770 liblrdf0-dbgsym_0.6.1-1_amd64.deb 3fcf9fc9e7c303b0976e0cfaaa3c57755856ea34a38fbcb3c7e8b7c3947d27cf 25384 liblrdf0-dev_0.6.1-1_amd64.deb d47ae13fc728885f3c9f55d4ce859aae86f5d385db67f6dfe0af5e8a0b4a6b21 24526 liblrdf0_0.6.1-1_amd64.deb 388154b89b118751582cda508a82a191a31a5d6b7c3f05b5c88fb7d471d95324 7542 liblrdf_0.6.1-1_amd64.buildinfo Files: 5820e1dad6f3bdd24673df99f93bb227 2095 libs optional liblrdf_0.6.1-1.dsc 8bb0ac7e8fe1a5a90083c89776bd3deb 43878 libs optional liblrdf_0.6.1.orig.tar.gz 0d14983b27ebc565c14f3f6dc7e92fd4 8508 libs optional liblrdf_0.6.1-1.debian.tar.xz 2bb90507416e7537d54460baeeaec0aa 26770 debug extra liblrdf0-dbgsym_0.6.1-1_amd64.deb be936f8cbc9aab6feb03715985544219 25384 libdevel optional liblrdf0-dev_0.6.1-1_amd64.deb 2f06548c87682080eb489bc92adfcd25 24526 libs optional liblrdf0_0.6.1-1_amd64.deb 4debb72fda27c69363b9df7b8d4d4bae 7542 libs optional liblrdf_0.6.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYc9zyAAoJECx8MUbBoAEhBUcP/3IhITadUBk3+Yf0UlU98wtD Lm4erltGoyQW/USpnFc8YxPSABXlPqWnMh/ZVCDQSawnZ1jpIiH4kQmDciraEZia 4igDIHbBl/M1CixaP0/jeooRJmKHpj9QIglGSayc4eGT4o4k0+1/WJqM3kkhgWR+ 2NbN+LiCJGXFtRQYXxX8Nz3O44hXvuyKj72f0lYxIFUXCatvYVRnPJH9qBDfKLJ+ zeXGB9NrxYxeKVTm4cmpYf3cLxPNyGwvpfZUyGx7hqd8B8E5wFweBIvc1utOjd0V WmAGSr4kjHhykQPOwfY9uXgNOjNi79cJ1W/TWiWdVmpcOuUoGK9f/DqBxIYuvyA/ 82Hln9ICSdirC7KiXnrF/yBLHUAJUDi3iZZOhVM7sUUORwaNoXLPbjxvnyCtl4sy 0QCJgnR7yZWbdkdX6uoxIMl4QZHP0gZB0OL0xFowIaIcqn/+VYaz02mzsbXDUtMb +Fb+/Q0+C18U3lIhxhK0GA6gHRwhpOOmadukqSDocLm6E+n+1kbk4RyOkf8GRSqB cZRnxKHXW+VHMGrBCazpgjSud49zv/5LFVAeU+6JxMeynXgJ9UhAeokr91vgn1we LX/+6KWs/bt9P4Yz3TNrzUU0Ue8HXRWtTQwJHrFuio+UasrGS3ZXmeZ7mbQ3VBP0 gi1aPP/WjRRc3fBw4QQq =mq7i -END PGP SIGNATURE- 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 libopenshot_0.1.2+ds1-1_amd64.changes
libopenshot_0.1.2+ds1-1_amd64.changes uploaded successfully to localhost along with the files: libopenshot_0.1.2+ds1-1.dsc libopenshot_0.1.2+ds1.orig.tar.gz libopenshot_0.1.2+ds1-1.debian.tar.xz libopenshot-dev_0.1.2+ds1-1_amd64.deb libopenshot-doc_0.1.2+ds1-1_all.deb libopenshot9-dbgsym_0.1.2+ds1-1_amd64.deb libopenshot9_0.1.2+ds1-1_amd64.deb libopenshot_0.1.2+ds1-1_amd64.buildinfo python3-openshot-dbgsym_0.1.2+ds1-1_amd64.deb python3-openshot_0.1.2+ds1-1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.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
Processing of libopenshot-audio_0.1.2+ds1-1_amd64.changes
libopenshot-audio_0.1.2+ds1-1_amd64.changes uploaded successfully to localhost along with the files: libopenshot-audio_0.1.2+ds1-1.dsc libopenshot-audio_0.1.2+ds1.orig.tar.gz libopenshot-audio_0.1.2+ds1-1.debian.tar.xz libopenshot-audio-dev_0.1.2+ds1-1_amd64.deb libopenshot-audio-doc_0.1.2+ds1-1_all.deb libopenshot-audio3-dbgsym_0.1.2+ds1-1_amd64.deb libopenshot-audio3_0.1.2+ds1-1_amd64.deb libopenshot-audio_0.1.2+ds1-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.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
Processing of liblrdf_0.6.1-1_amd64.changes
liblrdf_0.6.1-1_amd64.changes uploaded successfully to localhost along with the files: liblrdf_0.6.1-1.dsc liblrdf_0.6.1.orig.tar.gz liblrdf_0.6.1-1.debian.tar.xz liblrdf0-dbgsym_0.6.1-1_amd64.deb liblrdf0-dev_0.6.1-1_amd64.deb liblrdf0_0.6.1-1_amd64.deb liblrdf_0.6.1-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.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
liblrdf_0.6.0-1_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 09 Jan 2017 18:47:08 +0100 Source: liblrdf Binary: liblrdf0-dev liblrdf0 Architecture: source amd64 Version: 0.6.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Jonas Smedegaard Description: liblrdf0 - library to manipulate RDF files describing LADSPA plugins liblrdf0-dev - liblrdf0 development files Changes: liblrdf (0.6.0-1) unstable; urgency=medium . [ upstream ] * New release. . [ Jonas Smedegaard ] * Update copyright info: + Extend coverage for autotools files. + Fix cover all Makefile.in files. + Fix add Files section for libtool. + Add trailing dot to FSF owner string. + Add Files section for md5 files (in the public domain). * Stop build-depend on libssl-dev: No longer needed. * Unfuzz patch 1001. * Re-add and adapt patch 1002 to rename badly named md5 symbols. * Update symbols file: Add 3 sybols: _lrdf_MD5_*. Checksums-Sha1: 370bcea439cdef9b32cdf322001bd434fa4f8b6b 2113 liblrdf_0.6.0-1.dsc 1fa9100d91fdef00c3d371a682732b205d4661f9 257022 liblrdf_0.6.0.orig.tar.gz d0ca9e6ddb4d3939ec028a842f692021be87bcf3 8960 liblrdf_0.6.0-1.debian.tar.xz 6700050ae092b358a87a5e9dcf1608eafb3753f5 26766 liblrdf0-dbgsym_0.6.0-1_amd64.deb 7f16f3728849888498c02c7fd28b533e9dfe0a36 25756 liblrdf0-dev_0.6.0-1_amd64.deb 05a670f6b2d959991f780dd31a2facaabb835ee7 24884 liblrdf0_0.6.0-1_amd64.deb e97edaed0ac7e49e845181c4178b35a1d77cebc6 7542 liblrdf_0.6.0-1_amd64.buildinfo Checksums-Sha256: d2925103c826386e53c9310aee54c0ad833f8419b403fd37a2f10eca9f82db5d 2113 liblrdf_0.6.0-1.dsc 34a8592bbdfe9e9b80e9be8d8f948aaf7bafd60f65177a30a042246f5b487e1c 257022 liblrdf_0.6.0.orig.tar.gz 494c26832f4e20e1c4e1377de009498b3e4f101354cee37039cca1bb739cb6ed 8960 liblrdf_0.6.0-1.debian.tar.xz 04c40de42f4c97728b311e875ebb8e18fa28a61e6efe0b367125c7cddc9f21e8 26766 liblrdf0-dbgsym_0.6.0-1_amd64.deb 7df59ebe70b2b9b346db988dcf276e5add5882d72a921c9aa704ce36d0a7acf7 25756 liblrdf0-dev_0.6.0-1_amd64.deb fef7ae0b1a7440979cbfcb7ee4063450f5a581734f8e6a669ac48789a963deaa 24884 liblrdf0_0.6.0-1_amd64.deb 326d16bf1a2c1c9c84c5e3635b5940e812155e2df55f0336f6991ca91af4763b 7542 liblrdf_0.6.0-1_amd64.buildinfo Files: 087653b524f3cab070c91020f69f3324 2113 libs optional liblrdf_0.6.0-1.dsc a096e2802a896bd03bc87293dce11b10 257022 libs optional liblrdf_0.6.0.orig.tar.gz bc707f8a0a8549adb13aded1d025ba32 8960 libs optional liblrdf_0.6.0-1.debian.tar.xz fda73ebdfac3efec7fd128537850e750 26766 debug extra liblrdf0-dbgsym_0.6.0-1_amd64.deb 39119ecb61ae750d53eb4561c69f3bc6 25756 libdevel optional liblrdf0-dev_0.6.0-1_amd64.deb 65ba5ab202fe58bb375e49c47aeb6ff4 24884 libs optional liblrdf0_0.6.0-1_amd64.deb c95c6d2ff0207a480aa7d9db039fc7bd 7542 libs optional liblrdf_0.6.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYc88PAAoJECx8MUbBoAEhip4P/1YBhtbLDxMyPH71Dx3MLMip q1ywBMVQ3sATK3U/jrgLJWqt+jJ3U2AHUtt6LQitxkgHZorFE40DVwO47urBN9rV 4UZyFTMwKNQ55YF4GszGKdP3/oAGI4LwRzVyqmuEjH7pWkzrjdZSXxine8XfocnN 6kqxzbticAfrliFeI2hbWjWU/t+mVNxj/YktKbeGSv2gYWANODM+0sEjqTg2Dqzr gBo2en7ct2p4dU7BxtRwSrJVBjyBnqFnzDa22+UVTyzxLpgCucoWd0KvsUyeB2zO ZwufV8CSCz3Sk7SXbehg+/SJ6JFuq+lAvY7mCfkmSIPTCLMZmh9r+JHheWuBBqX2 z8CfImPj77Rdgjw+B/9F3lTJ6j640O7Q0W0MkZLH7cC+8+CoWyCwZ23y2drWkz4s ye8e6AQZRF7i6ZmTgWNCi1mBQATzgZzc2nRfH2LXewzo/1FNUuC9/n/5TL/fF9x4 p2N7ZNGWomG+n0hyK0hSvUyUHaAA4vVAAlgXQr/Uv5X6bYuAGocATA4rK2OEXT+O f6td9ZFP9zbAUl8dtJBhMX7Vgf8lOYxKPAwCIW4F6xV368H/OeAZR5Zwla9V1RqX ZiOSmK4bt/XpEvGw2D6ZVBBPRyRdlHZWZAJU7WTLsyzHTa6Q5yGUx7mZ6jxo0irx NXLodytDKyycim8MC+sm =f2Lg -END PGP SIGNATURE- 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 liblrdf_0.6.0-1_amd64.changes
liblrdf_0.6.0-1_amd64.changes uploaded successfully to localhost along with the files: liblrdf_0.6.0-1.dsc liblrdf_0.6.0.orig.tar.gz liblrdf_0.6.0-1.debian.tar.xz liblrdf0-dbgsym_0.6.0-1_amd64.deb liblrdf0-dev_0.6.0-1_amd64.deb liblrdf0_0.6.0-1_amd64.deb liblrdf_0.6.0-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.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
[bts-link] source package inkscape
# # bts-link upstream status pull for source package inkscape # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #810792 (http://bugs.debian.org/810792) # Bug title: inkscape: systemd-plot.svg can't be read (one example attached) # * https://bugs.launchpad.net/bugs/1653694 # * remote status changed: (?) -> Triaged usertags 810792 + status-Triaged # remote status report for #822579 (http://bugs.debian.org/822579) # Bug title: inkscape: may mess up with hatches, when importing DXF files # * https://bugs.launchpad.net/bugs/1653707 # * remote status changed: (?) -> Triaged usertags 822579 + status-Triaged thanks ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
inkscape_0.92.0-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 Jan 2017 15:03:04 +0100 Source: inkscape Binary: inkscape Architecture: source Version: 0.92.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Mattia Rizzolo Description: inkscape - vector-based drawing program Changes: inkscape (0.92.0-2) unstable; urgency=medium . * Upload to unstable. * Gbp: back to master. * d/control: + require a new enough version of bash-completion, so backports users will still have bash completion after the upgrade. + Recommend python-scour to enable the feature "save as optimized svg". * New patches from upstream trunk: + 0002-Fix-lintian-s-executable-not-elf-or-script.patch + 0003-Install-the-localized-manpages-in-the-correct-path.patch + 0006-Suppress-warnings-on-symbols-dialog.patch * New patches waiting to be upstreamed: + 0004-typos-libcroco.patch + 0005-Fix-typo-in-a-variable-name.patch * d/inkscape.lintian-overrides: drop, lintian warnings fixed by properly installing the manpages. Checksums-Sha1: 1372a64c3a5b7cc7862a5f5bd7810d8b09d757e7 2863 inkscape_0.92.0-2.dsc 7be3c10ea4e872207442c3cb5a86929dbc71283a 28060 inkscape_0.92.0-2.debian.tar.xz Checksums-Sha256: 0e5d6ed78ecb63328547c0e7c491b356074bc49a19e17f8121ee3325293f1757 2863 inkscape_0.92.0-2.dsc 9c792c96f07c7573cda22f73f36bb4c72aab217e0e29c190c61573065334c8d4 28060 inkscape_0.92.0-2.debian.tar.xz Files: 95fb50af2d6ca7cf1adbda09c8270bad 2863 graphics optional inkscape_0.92.0-2.dsc dc513f9ee3299026327a53c0cd563073 28060 graphics optional inkscape_0.92.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlhznggACgkQCBa54Yx2 K62ShRAAu30GwcuV/CKJ8G2Re9WpkkgEiAPFHU23aeFfFuABMwVbW9WbojkuHaIY hI1SaOazyeEkRgfpUpmC3eKd6h/TzuNVUC+/DmXAcx4G5L/ZayvxRZfHe/pE9+IG xVNekZ70H9WYkIo/KmiJZc/3hcxc8Y0RolTyXWmRntx3So48aNemkdUeyz0p/Cq0 ApFhmCRbfqPd0l9MMe4YB3yGxlieSmUUM9iPRlr0liMC1bAvrdvxi9/8oxALmCy5 td8jDmBOEoK8ALP9BfLC6rUAXHseowk10uws6dQioCKPuoN78cPDXtwV3P+ugZCb uAlOi8KgzJS1My9nsOY7Tx64YmbCL+RJkHgPCjEifvLBppaDy1JTE0ZtA64Ealqa RievSjUNwBNUtmsZEoLmHh6E53UP5pr5KpWSDXPcoozwDXLLrkdy+8jl8wLYKBTj V3J6N4L/TBz0IMewYJyUw96A2UH08WB4iBEwjF7rd796Lflu2A5DG3xYQUS641E4 xdMs7RVLGSV7asUuI4DkQXOa3QQPsLXZshwTsNjRR0neMJmpdQPI3VkszNlzHaMN 7hr4YVzDNLYgEFGm7+Hw4D6MKsYbMjMydUOd96uJzf7IYjVhq/A2uvAbV6L8UOB+ TATcLMdw+dUdR9EhmXQKF2nKvlnVRiUuj1bQIi3W4IrwdaHbGHI= =Q3TY -END PGP SIGNATURE- 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 inkscape_0.92.0-2_source.changes
inkscape_0.92.0-2_source.changes uploaded successfully to localhost along with the files: inkscape_0.92.0-2.dsc inkscape_0.92.0-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.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#847988: pd-libdir: does not respect current loader path
On Mon, 12 Dec 2016 23:45:41 +0100 =?UTF-8?Q?IOhannes_m_zm=c3=b6lnig_=28Debian/GNU=29?= wrote: > On 12/12/2016 10:06 PM, IOhannes m zmoelnig wrote: > > please fix the loader, so it respects the 'path' argument. > > > afaict, this is fixed in the upstream-clone at >https://github.com/pure-data/libdir > > however, the code there needs review. do you intend to fix this for stretch? dgasndr IOhannes signature.asc Description: OpenPGP 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: Ardour auto removal from testing
On 2017-01-09 13:34, Jaromír Mikeš wrote: > We should also tighten B-D to libfftw3-dev (>= 3.3.5-3~) I guess ... i'm not entirely sure whether we should. generally i find it not a good idea to tighten (Build-)Dependencies to work around bugs in the dependent pacakges. specifically i want to keep ardour in Debian though. otoh, #850482 should fix this automatically. fgamsdr IOhannes ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
ffdiaporama in sid is outstanding old
Hello maintainers, is there any chance to have the actual version of ffDiaporama available in sid? The version in sid is 1.5 and it is a really old one. The actual version is 2.1 and it is available since Feb 2014. Thank you very much. Kind regards harald ___ 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: Ardour auto removal from testing
2017-01-09 12:29 GMT+01:00 James Cowgill : > On 09/01/17 11:18, Jaromír Mikeš wrote: > The bug in ardour isn't fixed until it gets binNMUed: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850482 > > Uploading anything would also fix it (if it comes to that). We should also tighten B-D to libfftw3-dev (>= 3.3.5-3~) I guess ... best regards mira ___ 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: Bug#850685: [guayadeque] Upstream no longer dead
Processing control commands: > reassign -1 wnpp Bug #850685 [guayadeque] [guayadeque] Upstream no longer dead Bug reassigned from package 'guayadeque' to 'wnpp'. No longer marked as found in versions guayadeque/0.3.7~ds0-2.1. Ignoring request to alter fixed versions of bug #850685 to the same values previously set > retitle -1 RFP: guayadeque -- lightweight music player Bug #850685 [wnpp] [guayadeque] Upstream no longer dead Changed Bug title to 'RFP: guayadeque -- lightweight music player' from '[guayadeque] Upstream no longer dead'. -- 850685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850685 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#850685: [guayadeque] Upstream no longer dead
Control: reassign -1 wnpp Control: retitle -1 RFP: guayadeque -- lightweight music player On 09/01/17 11:37, Reuben wrote: > Package: guayadeque > Version: 0.3.7~ds0-2.1+b1 > Severity: wishlist > > --- Please enter the report below this line. --- > Source is now on Github and there have recent releases. > https://github.com/anonbeat/guayadeque Looks good. They also moved to gstreamer-1.0 so that's been fixed. Someone still has to volunteer to maintain this again though. Thanks, James signature.asc Description: OpenPGP 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: Ardour auto removal from testing
Hi, On 09/01/17 11:18, Jaromír Mikeš wrote: > Hi, > > As the bug 849593 has been closed should be closed also 849589? > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849593 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849589 > > Or it will be done later automatically as bugs are cloned and only > patience is needed? The bug in ardour isn't fixed until it gets binNMUed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850482 Uploading anything would also fix it (if it comes to that). James signature.asc Description: OpenPGP 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
Ardour auto removal from testing
Hi, As the bug 849593 has been closed should be closed also 849589? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849593 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849589 Or it will be done later automatically as bugs are cloned and only patience is needed? best regards mira ___ 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: Bug#850667: gnome-mpv: no more scroll indicator after updating mpv to 0.23.0-1
Processing control commands: > tags -1 patch fixed-upstream Bug #850667 [gnome-mpv] gnome-mpv: no more scroll indicator after updating mpv to 0.23.0-1 Added tag(s) fixed-upstream and patch. > forwarded -1 https://github.com/gnome-mpv/gnome-mpv/issues/241 Bug #850667 [gnome-mpv] gnome-mpv: no more scroll indicator after updating mpv to 0.23.0-1 Set Bug forwarded-to-address to 'https://github.com/gnome-mpv/gnome-mpv/issues/241'. -- 850667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850667 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#850667: gnome-mpv: no more scroll indicator after updating mpv to 0.23.0-1
Control: tags -1 patch fixed-upstream Control: forwarded -1 https://github.com/gnome-mpv/gnome-mpv/issues/241 On 09/01/17 07:39, Stefan Breunig wrote: > Package: gnome-mpv > Version: 0.10-1 > Severity: normal > > Dear Maintainer, > > after updating mpv there is no more scrollbar indicator and the scrollbar does > not work when clicked. I presume I have updated from mpv 0.22.0-1. > > The issue is fixed if I build gnome-mpv from source. Would you kindly either > update to gnome-mpv 0.11 before the freeze or backport the required patch? If > needed, I can bisect the source to figure out which patch fixes gnome-mpv. This is the upstream bug and fixing commit: https://github.com/gnome-mpv/gnome-mpv/issues/241 https://github.com/gnome-mpv/gnome-mpv/commit/27062427415fffc756322428516ab95173615d13 It appears the 0.11 release was made specifically for mpv 0.23 so it would be good to get it in. Thanks, James signature.asc Description: OpenPGP 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
