Re: MuseScore (and soundfonts) backporting plans
Hi Thorsten, thanks for the heads-up! Thorsten Glaser wrote: > I had not planned to backport fluidr3mono-gm-soundfont also, but given that > it already entered stretch-backports by means of src:musescore there might > be demand for the binary package to not vanish. Perhaps I should just upload > it right now so it can enter backports-NEW already⦠Have you considered to trigger a transition in backports from fluidr3mono-gm-soundfont to musescore-general-soundfont by turning the former into a dummy package with a dependency on the latter? - 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
Accepted fluidsynth 1.1.10-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 15 Mar 2018 17:27:53 +0100 Source: fluidsynth Binary: fluidsynth libfluidsynth1 libfluidsynth-dev Architecture: source amd64 Version: 1.1.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Fabian Greffrath Description: fluidsynth - Real-time MIDI software synthesizer libfluidsynth-dev - Real-time MIDI software synthesizer (development files) libfluidsynth1 - Real-time MIDI software synthesizer (runtime library) Changes: fluidsynth (1.1.10-1) unstable; urgency=medium . * Team upload. . [ Jaromír Mikeš ] * Drop explicit Testsuite field, not needed anymore. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Fabian Greffrath ] * New upstream version 1.1.10 Checksums-Sha1: c3595304d4555dd9f6dd6ff3ca9b7ae5a1a96c16 2390 fluidsynth_1.1.10-1.dsc 07a3183298375914021536a7685991e5beb92a0d 633628 fluidsynth_1.1.10.orig.tar.gz 24bbce01877f674c1c9febdc8ff83facc47820ef 13684 fluidsynth_1.1.10-1.debian.tar.xz f0a12bf850463afbbe77f907b744a9cd5c57aa61 18860 fluidsynth-dbgsym_1.1.10-1_amd64.deb 91e841a8abd3fabecf81a6b487913642d7e4a31d 9309 fluidsynth_1.1.10-1_amd64.buildinfo 6c538375bd07840162439877015445e505911daa 49688 fluidsynth_1.1.10-1_amd64.deb b91eff168ab6ad5a66c9728b25bea2beabc0012e 48672 libfluidsynth-dev_1.1.10-1_amd64.deb d06c860427ae0fba3856283a24d2760d75d4cfaf 433584 libfluidsynth1-dbgsym_1.1.10-1_amd64.deb 61cba3de707ba472c9106e0878e4e42c6de40363 167148 libfluidsynth1_1.1.10-1_amd64.deb Checksums-Sha256: 000ecd2b128ba5f1646432bf490d42d415b5749c5f2a4c194719bc5f174a2fbd 2390 fluidsynth_1.1.10-1.dsc b74801d0fdd726c4555149bf075b76dc4074658ec0a8f7a3753f4a64589e5300 633628 fluidsynth_1.1.10.orig.tar.gz 2188d1424a7eda8702216fb16ee1a50d256f8c70fca2054b3aae0c91cf555f9c 13684 fluidsynth_1.1.10-1.debian.tar.xz 1361d2a8f3b15e9ecbdb36a732a1e6482fcd494b42e1b055e08eb9ebc315f277 18860 fluidsynth-dbgsym_1.1.10-1_amd64.deb f687de420089d662abf738c97ac04d8d8a355c332c2b20141816f8cb559cc6d5 9309 fluidsynth_1.1.10-1_amd64.buildinfo 75c6e215e678bf8da769e63e242c38af5621b91f7ad3568c008d46c5610228c3 49688 fluidsynth_1.1.10-1_amd64.deb ded976007823256dc6da1ae92771a9743667a9a6b7855aebfa5cca05f265b337 48672 libfluidsynth-dev_1.1.10-1_amd64.deb 359c756e084a8593f269c381aba23f1d637301795365a276bec0e99b46ee3e54 433584 libfluidsynth1-dbgsym_1.1.10-1_amd64.deb 3c14504aa08f396bd60f8961f2ccb42a8993305614233ff700e3fc7366844771 167148 libfluidsynth1_1.1.10-1_amd64.deb Files: 9af3494bc4981c341e4a0dc5ea589a12 2390 sound optional fluidsynth_1.1.10-1.dsc df0bc67f4d8fa8b75b5b005091be957b 633628 sound optional fluidsynth_1.1.10.orig.tar.gz 7689ff773f5a32c8cad58004c6119d9c 13684 sound optional fluidsynth_1.1.10-1.debian.tar.xz 2f51ef6cb1acf5866e315a5a2b80329c 18860 debug optional fluidsynth-dbgsym_1.1.10-1_amd64.deb 3a55b1484a57b6266e7771b38873e9b8 9309 sound optional fluidsynth_1.1.10-1_amd64.buildinfo 12baba346a3fc1327351d0c3f8d40302 49688 sound optional fluidsynth_1.1.10-1_amd64.deb 25ab7d94fccda870f9a05414378703e3 48672 libdevel optional libfluidsynth-dev_1.1.10-1_amd64.deb 141b4a0e64ecc29c984c60f251c14c08 433584 debug optional libfluidsynth1-dbgsym_1.1.10-1_amd64.deb 2b1ad389561acd5a0e072485f8dacd2e 167148 libs optional libfluidsynth1_1.1.10-1_amd64.deb -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlqqoWoVHGZhYmlhbkBn cmVmZnJhdGguY29tAAoJEMvqjpcMzVnf5DUP/jicb6KuiMiiuRxuTlq9Y3LefF/7 8j27T5WVtEdnTvyxz9y5/thovXwP52vtBK0WMQyaToGw4pPtkmYOwofmGuyXHNUc FOPkD+5Ii+tfCCFv9tggQS/Cg7q7ToY1EGXes/BTTHjykCV93mb6c8ZJKreFudaB l1/60zEfI9J2nI2vWdAhhpFwhGZcJA/rMxXFc/cZWWZqJ6xWR0Vhtctl3PDQbCB4 Ms7F/94tC2o1nFKsLiGunkxWOrtRrm5xBEv4L0BeubNsTMCn6qpamwGTFir3laqZ iSmyepzVvdoL4n7d4gA/pF9LpMC7DEbF0gwJ7Qwrz1dDBiN29P0iDoizfrezeN5l nLwPGFBeVFAW98lt8f2/hzV5u/kFyHjlVVlz51aPl54WYBoS2nm4EfNoxOfHCAqV G+NisKdBnc9stfF4mrmPGj8zUQr4XhJu1/eAVrn3aNocST79hDk62bomekIJeEsQ PF3gpu6mF3nuRWIujz8p9r9jA1N5pC+R82xvIRNrNDl6DI7GYuOFG5Y4SL10j+za 8uvFTlXvXO4XuE9p2XwzfkMcPnQKYfrw4ikOULhLnzT6dSfdreFq+D27eKR7LO6Z +h6mlfnvIUEO1fqT9YIOntt1kEVpGjhX4wyE9VK/E2koi3rlfgEoVKg6XUhYInSI 9Lw1K286nFGPDvSQ =MtOE -END PGP 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
Bug#892083: smplayer: recodes filenames to wrong encoding
Am Montag, den 05.03.2018, 06:28 +0300 schrieb Oleg Broytman: > ii mpv 1:0.27.2-dmo1+deb9u1 Please try again with Debian's mpv package. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#855198: Adding i386 support
Am Mittwoch, den 07.03.2018, 11:58 -0300 schrieb Ignacio Losiggio: > I know that not _every_ x86 machine has sse2 support but i think that > having a usable package for those who use x86 on post-2003 computers Why is an i386 package only usable if compiled with sse2 instructions? If you are targeting post-2003 computers, why aren't you using an amd64 build anyway? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#889915: libfaad2 in Wheezy contains patches for some security bugs. They were not backported to Jessie.
Hi Salvatore, Salvatore Bonaccorso wrote: > The current issues which were fixed in DLA-1077-1 are all no-dsa, so > thei did not warrant a DSA via security.d.o. Can you fix those issues > via upcoming point releases? yes, probably. But I guess that's not Mikulas' point: Both wheezy and jessie had package version 2.7-8. While wheezy got a fixed package with 2.7-8+deb7u1, jessie didn't. The fix should be as straight as uploading the same (source) package to jessie that got uploaded to wheezy. CC:ing Markus Koschany who did the upload to wheezy. Thanks! - 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#889915: libfaad2 in Wheezy contains patches for some security bugs. They were not backported to Jessie.
tags 889915 +security +jessie thanks Forwarding this to the security team. Mikulas Patocka wrote: > Package: libfaad2 > Version: 2.7-8 > Severity: normal > > Dear Maintainer, > > Libfaad2 in Wheezy contains some security patches. But the patches were > not > backported to Jessie. > > > > -- System Information: > Debian Release: 8.10 > APT prefers oldstable-updates > APT policy: (500, 'oldstable-updates'), (500, 'oldstable') > Architecture: i386 (i586) > > Kernel: Linux 4.14.16 (PREEMPT) > Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2) > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > > Versions of packages libfaad2 depends on: > ii libc6 2.19-18+deb8u10 > ii multiarch-support 2.19-18+deb8u10 > > libfaad2 recommends no packages. > > libfaad2 suggests no packages. > > -- no debconf information > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintainers@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers > > ___ 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: How to handle translation bug?
JaromÃr MikeÅ¡ wrote: > But I am not still sure about correct workflow. I would forward it upstream. Someone there must have done the translation and this one will likely merge the suggestion. - 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#881536: ffmpeg: Breaks sound in kodi
Am Montag, den 13.11.2017, 18:53 +0100 schrieb Robert Luberda: > I can confirm that too. Impressive! Good work, James. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#879513: lame will not run at all
Hi Klaumi, Am Sonntag, den 22.10.2017, 15:24 +0200 schrieb Klaumi Klingsporn: > Maybe it helps to upgrade libmp3lame0 to 3.100-2 as well? > In this case lame should depend on this version (or above) > of course! the point is that in the lame 3.100-2 upload the library got a symbols file that maps all symbols to a dependency on libmp3lame0 (>= 3.100). So, lame 3.100-2 should have pulled in the 3.100-2 library package. Alex, can you confirn that? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#879513: lame will not run at all
control: tags -1 +unreproducible Am Sonntag, den 22.10.2017, 14:01 +0100 schrieb Alex Dekker: > Package: lame > Version: 3.100-2 Hi Alex, I cannot reproduce your issue. > ii libmp3lame0 1:3.99.5-0.1 Ahem, please update the library package as well. Thanks, - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#879129: lame: new upstream version
Hi Rogerio, Rogério Brito wrote: > After a long hiatus, a new version of lame was released (3.100) thanks for the reminder! I am on it, will probably upload this evening. - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: fluidsynth_1.1.8-1_amd64.changes ACCEPTED into unstable
Am Samstag, den 14.10.2017, 05:03 + schrieb Debian FTP Masters: > Source: fluidsynth > Version: 1.1.8-1 > Changed-By: Jaromír Mikeš Cool, thanks for that! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package
Hi Thorsten, Am Mittwoch, den 11.10.2017, 20:53 +0200 schrieb Thorsten Glaser: > Thanks. Have a look at the git repository to see whether I > bungled editing it or if it’s good now. Looks perfect now, thanks! > I suppose this alone isn’t worth a new upload of its own? No, of course not. ;) - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package
Hello Thorsten, I have problems parsing the last sentence in the package description for fluidr3mono-gm-soundfont. I am sure you dodn't mean a "slow footprint" and the sentence could be split into three or at least two sentences. Let me suggest the following: "It can be used with most modern MIDI synthesisers which support the SF3 format and has a low installed size footprint, while providing the large GM sound set. As it comes under the MIT licence, it can be used in most settings." Thanks, - 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#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package
Am Dienstag, den 10.10.2017, 21:18 +0200 schrieb Thorsten Glaser: > They could switch to a different one, is what I meant. > > (or embed it in the C source… *shudder*) Whoa, I think both these cases would be incentive enough to package it on its own. > Exactly. Good that we’re on the same page. Indeed! > Uploaded, should enter NEW any time now. Great, thank you! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package
Hi again, Am Dienstag, den 10.10.2017, 17:41 +0200 schrieb Thorsten Glaser: > What if they decide to stop shipping it? then we would proceed as we did for the previous soundfont they provided, i.e. timgm6mb-soundfont. That is, we would continue to package it in its own source package. .o(On the other hand, musescore requires a soundfont to be installed in order to work, so why should they ever stop shipping one? In that case, we would have to ship the soundfont in its own source package anyway, and in the meantime musescore could/would have to use one of the other soundfonts already packaged in Debian -- it is still able to read the SF2 format after all.) > Yes, but, I’m a MuseScore user, and so really really *really* wish > to not prevent getting a newer version. I don't think the soundfont is to blame for the slow adaption of musescore 2.0 in Debian. It was just the usual packaging glue. ;) If future problems arise with the soundfont, we will package it in its own source package and upload new musescore releases to experimental in the mean time. I don't see why this should be so much different from any other "transition". ;) > I can do that, but thanks. Cool, thank you! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package
Hi Thorsten, Thorsten Glaser wrote: > as far as Iâm informed, the soundfont is not an âAPIâ of MuseScore, > i.e. it can, and possibly will, change without notice. If upstream finds a way to further improve the soundfont and decides to ship a modified version in the next release, I am fine with that. The actual file format, I believe, can be considered stable, though. It has already been adopted by other upstreams than musescore and fluidsynth. > Sure, we can split it off, and itâll be versioned with the version > of the corresponding MuseScore package, but thatâll be all of it, > unless someone actively maintains the soundfont. Sure, as long as musescore keeps shipping this soundfont, it will be part of that source package. > Furthermore, MuseScore may cease shipping this, or ship an > incompatible version, in the future. I *really* wish to avoid > a repeat of #768524 where we could not upgrade MuseScore because > something used the old soundfont. I'd rather see it as a positive sign that musescore's soundfont has proved useful outside of its original scope. > If Fabian insists, [...] I do, please split the soundfont off into a separate package. ;) > If anyone cares about it and would maintain the soundfont split > off if necessary, do share. I can take care of implementing the soundfont split-off in the musescore Debian package and I would also volunteer to maintain it in a separate source package should musescore ever decide to break it or not ship it anymore. Thanks! - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: fluidsynth_1.1.7-1_amd64.changes ACCEPTED into unstable
Hey Jaromir, thank you very much for upgrading the fluidsynth package so promptly, but... Am Montag, den 02.10.2017, 11:34 + schrieb Debian FTP Masters: >* New upstream version 1.1.7 (Closes: #859793, #877308, #740710) only one of these three bugs asks for upgrading to the new upstream version. The other two bugs are separate issues that merely happen to be fixed by upgrading the upstream release, too. Please, take the time and add a short separate changelog entry for each of them, e.g. * New upstream version 1.1.7 (Closes: #877308) + consistently relicense libfluidsynth under LGPL-2.1+ (Closes: #859793) + add support of vorbis-compressed sf3 sound fonts (Closes: #740710) Thank you very much! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#877308: libfluidsynth1: New upstream version 1.1.7 available
Package: libfluidsynth1 Version: 1.1.6-4 Severity: wishlist Dear pkg-multimedia team, a new upstream version 1.1.7 of fluidsynth has been released on Sep 04, 2017. Among others, this release fixes the following issues which have also bee filed as bugs in Debian: consistently relicense libfluidsynth under LGPL-2.1+ (also addressing fluid_chorus.c, #165) add support of vorbis-compressed sf3 sound fonts (#140, thanks to @fabiangreffrath) Please consider packaging it ASAP, thanks! - Fabian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libfluidsynth1 depends on: ii libasound21.1.3-5 ii libc6 2.24-17 ii libglib2.0-0 2.54.0-1 ii libjack0 [libjack-0.125] 1:0.125.0-2 ii libpulse0 11.1-1 ii libreadline7 7.0-3 ii libsndfile1 1.0.28-4 libfluidsynth1 recommends no packages. libfluidsynth1 suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: musescore_2.1.0+dfsg1-0.2~bpo9+1_amd64.changes is NEW
Hi Thorsten, Thorsten Glaser wrote: > I think you're confused ;-) apparently, yes, I missed the "backports" part. ;) Thanks for taking care of musescore! Cheers, - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: musescore_2.1.0+dfsg1-0.2~bpo9+1_amd64.changes is NEW
Hi Thorsten, Am Mittwoch, den 06.09.2017, 17:54 + schrieb Debian FTP Masters: > binary:musescore is NEW. > binary:musescore-common is NEW. > binary:musescore-common is NEW. > binary:musescore-dbgsym is NEW. > binary:musescore is NEW. > source:musescore is NEW. if you had to go through NEW anyway, why didn't you consider to separate the SF3 soundfont out into a separate package as I requested in #871920? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#867724: Multiple security issues
Hi Markus, Markus Koschany wrote: > I uploaded a security update for faad2 to wheezy-security a few hours > ago. I am attaching the debdiff to this bug report. thank you very much for that! > Do you intend to fix the issue in Stretch too? I could prepare the > update for Jessie and ask the release team for a jessie-pu. I don't have any plans to do that. Cheers, - 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#867724: Multiple security issues
Am Sonntag, den 27.08.2017, 20:33 +0200 schrieb Markus Koschany: > Are you aware of any issues with your patch? Yes, there was an issue with my patch! I added a field to a struct to keep track of reading errors, but the struct was defined in two different places in the source code. This led to a crash when free()ing a pointer to this struct on Linux, but not on Windows which I used to develop the patch (don't ask). Applying this patch on top of the one I sent to the Debian BTS should fix this issue, although upstream decided to go a different way and entirely replace the mp4ff library. https://sourceforge.net/p/faac/bugs/209/?limit=25&page=1#d838 - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Two autdio packages for adoption
> i've adopted both packages on behalf of the pkg-multimedia team (moved > them into the team's git space, changed the maintainer's field). > i've added myself to the uploaders, but not fabian or anybody else > (please do that yourself at your earliest convenience). Thank you very much for that! - 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#871920: musescore-common: please split out the FluidR3Mono_GM.sf3 sound font into a separate package
Package: musescore-common Version: 2.1.0+dfsg1-0.2 Severity: normal Hi there, the next version of fluidsynth (1.1.7) will be able to use sound fonts in the SF3 format that musescore introduced. It is thus appropriate to split out the FluidR3Mono_GM.sf3 sound font that comes bundled with musescore into its own package, install it into /usr/share/sounds/sf3/ and add a symlink to the musescore-common package. This way, packages that use fluidsynth for MIDI rendering, e.g. SDL_Mixer, do not need to install the whole of musescore-common in order to be able to use this sound font. I suggest to use fluidr3mono-gm-soundfont as the name for the new package. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Two autdio packages for adoption
Hi Erik, Am Samstag, den 12.08.2017, 19:48 +1000 schrieb Erik de Castro Lopo: > libsamplerate needs a new release to close debian bug #860159, but since libsamplerate is a dependency of chocolate-doom, which I already maintain, I am interested in maintaining this package in Debian as well. (I could also have an eye on libsndfile, which interests me as well.) I am currently on vacation with little free time for Debian activities, but I plan to add myself to Uploaders once I am back home next week. Cheers, - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#865909: faac: CVE-2017-9129 CVE-2017-9130
control: tags -1 +patch +fixed-upstream This has been fixed in upstream GIT. Please find attached the cumulated patch - Fabian faac_865909.patch Description: Binary data ___ 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#867724: Multiple security issues
control: tags -1 +patch +fixed-upstream This has been fixed in upstream GIT. Please find attached the cumulated patch - Fabian faad2_867724.patch Description: Binary data ___ 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: Wheezy update of lame?
Hi Raphael, thank you very much for asking! In fact, I was about to start trying to work on this. But the fact that ASAN, which I have no experience with yet, is required to reproduce the vulnerabilities does not really help. :/ Also, upstream has already been made aware of the vulnerabilities, but I consider it very unlikely that the issues will be fixed there. The discussion has so far only lead to considering replacement of the internal mpeglib code with linking with mpeg123 which does not really help here: https://sourceforge.net/p/lame/mailman/message/35918740/ Am Dienstag, den 11.07.2017, 14:31 +0200 schrieb Raphael Hertzog: > PS: A member of the LTS team might start working on this update at > any point in time. You can verify whether someone is registered > on this update in this file: I woulnd't mind if someone else started working on this. Quite the contrary, I would be grateful. Nevertheless, I will probably try to get behind these issues myself and hope that our efforts don't clash. Maybe we'll end up with similar solutions at the end of the day. ;) Cheers, - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#865909: faac: CVE-2017-9129 CVE-2017-9130
control: forwarded -1 https://sourceforge.net/p/faac/bugs/208/
control: tags -1 +patchdiff --git a/frontend/main.c b/frontend/main.c
index 60f687b..33e39b8 100644
--- a/frontend/main.c
+++ b/frontend/main.c
@@ -806,6 +806,13 @@ int main(int argc, char *argv[])
hEncoder = faacEncOpen(infile->samplerate, infile->channels,
&samplesInput, &maxBytesOutput);
+if (hEncoder == NULL)
+{
+fprintf(stderr, "Couldn't open encoder instance for input file %s\n", audioFileName);
+wav_close(infile);
+return 1;
+}
+
#ifdef HAVE_LIBMP4V2
if (container != MP4_CONTAINER && (ntracks || trackno || artist ||
title || album || year || art ||
diff --git a/libfaac/frame.c b/libfaac/frame.c
index 5c203b2..94887ac 100644
--- a/libfaac/frame.c
+++ b/libfaac/frame.c
@@ -288,7 +288,7 @@ int FAACAPI faacEncSetConfiguration(faacEncHandle hpEncoder,
hEncoder->srInfo->num_cb_short);
/* load channel_map */
- for( i = 0; i < 64; i++ )
+ for( i = 0; i < MAX_CHANNELS; i++ )
hEncoder->config.channel_map[i] = config->channel_map[i];
/* OK */
@@ -303,6 +303,9 @@ faacEncHandle FAACAPI faacEncOpen(unsigned long sampleRate,
unsigned int channel;
faacEncStruct* hEncoder;
+if (numChannels > MAX_CHANNELS)
+ return NULL;
+
*inputSamples = FRAME_LEN*numChannels;
*maxOutputBytes = (6144/8)*numChannels;
@@ -342,7 +345,7 @@ faacEncHandle FAACAPI faacEncOpen(unsigned long sampleRate,
hEncoder->config.shortctl = SHORTCTL_NORMAL;
/* default channel map is straight-through */
- for( channel = 0; channel < 64; channel++ )
+ for( channel = 0; channel < MAX_CHANNELS; channel++ )
hEncoder->config.channel_map[channel] = channel;
/*
signature.asc
Description: This is a digitally signed message part
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: drumkv1 repo - failed merge
JaromÃr MikeÅ¡ wrote: > Can someone advise me how to fix it pls? Do you have any patches applied? If yes, unapply them before attempting to merge the new upstream release. If this doesn't help, try calling "git checkout -- " on the files git complains about. - 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#862171: vlc-plugin-qt: VLC uses QT 4 C++ widget instead of QT 5
Just a wild guess, but may this mismatch have to do with it? Erez Geva wrote: > ii libvlc-bin 2.2.5-1 > ii libvlc5 2.2.5-1~deb8u1 > ii libvlccore8 2.2.5-1 - 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#859793: fluidsynth: Package has infringed GPL
Am Freitag, den 07.04.2017, 14:16 +0200 schrieb Javier Serrano Polo: > This source code is freely redistributable and may be used for > any purpose. > > The license does not grant the right to modify the software. Therefore, > it is not compatible with GPL-2.1+ (sic) or LGPL-2.0+. Well, it could be argued that software modification is a purpose in itself, but I agree that the wording is unfortunate/ambigious. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#834581: handbrake-cli: make symlink handbrake-cli to /usr/bin/HandBrakeCLI
Control: tags -1 +upstream Paul wrote: > I propose a symlink is created, linking /usr/bin/handbrake-cli to > /usr/bin/HandBrakeCLI. While I generally agree with you, this isn't something that we should introduce in the Debian package. Consider someday people will write scripts that work only in Debian but not on other systems. So, please take this suggestion upstream. Thank you! - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#852869: say where the log file(?) is
ç©ä¸¹å°¼ Dan Jacobson wrote: > Anyways, imagine if Facebook just said "see the log file." but didn't Never listen to Facebook. ___ 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#852290: inkscape: saving as "optimised SVG" fails, due to error when importing scourString
Mattia Rizzolo wrote: > Note that it can't be workarounded in the packaging side by backporting > the newer python-scour and forcing an higher version, as python-scour is > only "Recommend"ed, and versioned recomends are not really considered. Not directly, but you can still enforce higher versions by using a Breaks relation against the older version. - 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#850446: handbrake: New upstream release 1.0.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Dienstag, den 10.01.2017, 20:30 +0100 schrieb Sebastian Ramacher: > Please push the changes if possible. Just pushed. - Fabian -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlh2YJ4ACgkQy+qOlwzN Wd8Nhw/+LLk4Vk8ocl5V03oE0V3lccyzV9wWy4EortadLk6wfXNQFPshWUkqmeZI 1uKJejQCOB3BM+fm7jgS5Ipe9brvSNui3uQIQMwrwuDw5kefHrjwentYwbxOgpet UL8Y/01KMjPvUhiWrh/t3vAj91StBkXrvAoofbRl4mTOAbF/KZQjvT0MrHJ5nVf2 B33o8Xs8ayvYuv1pUm0B1MfRopKYZAYFyE05OZX1+AOSsUaFyde64FLLaV3b8Ssd ZdBgTHQ3fNMfp6y2l09JA5LrQ8ecta1YpuBvB6PRw2Wge2uz04CEFMnx3qSnFAPD giQQzEFrbUvPjwlifPTaKMdKIAvydz3NBG4iOCrkgyO24zipITmOd6guS7WFZ+oE 7Jw6CfswVbfTkzPfdhZuI7i0SMkyMqqWCNGcBJoTpNyC4FA1EyaJPATdFqp88fa1 tc+7Mt1VmljMoLvevA4ALX0Xw0oJZuC8rk4Np7VAIoI1xUxzVV2Zqoliy34fynLm p5aSIWN3crz0CJJRihZmIrNJofkd9pZJlEKofin41fucIx4RhoZPP45Xsv/N/Ue1 a9NMM00q8Fi7v0sX82R2Oba3UeskFYULkHcmtqVoT0Cf93zK9ZlU8b/E7/GejlMS T+cBqS9flJLgPbRgiDi3Owx+vvnPmSL3coUh5XR7jmd294i0sIw= =VIj2 -END PGP 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
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#850446: handbrake: New upstream release 1.0.1
Package: handbrake
Version: 0.10.5+ds1-2+b2
Severity: wishlist
Hi team,
there is a new upstream release 1.0.1 of handbrake available. I have
already had a look at packaging it and this is as far as I got:
- Add --disable-df-fetch and --disable-df-verify to configure flags.
- Remove patches 001 and 003.
- Refresh patch 005.
- Force-push and refresh patch 002.
- Add libjansson-dev to Build-Depends.
However, then the build fails with something that looks like an API
mismatch in libbluray:
../libhb/bd.c: In function 'show_clip_list':
../libhb/bd.c:251:29: error: 'BLURAY_CLIP_INFO {aka struct bd_clip}'
has no member named 'clip_id'
ti->clips[ii].clip_id, hh, mm, ss);
^
../libhb/module.rules:12: recipe for target 'libhb/bd.o' failed
make[1]: *** [libhb/bd.o] Error 1
I am not sure, though, if this merely requires a newer libbluray
upstream snapshot or if handbrake uses and expects a locally patched
version of that library...
- Fabian
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'experimental'),
(500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages handbrake depends on:
ii libass5 0.13.4-1
ii libavcodec577:3.2.2-1
ii libavformat57 7:3.2.2-1
ii libavresample3 7:3.2.2-1
ii libavutil55 7:3.2.2-1
ii libbluray1 1:0.9.3-3
ii libc6 2.24-8
ii libcairo2 1.14.8-1
ii libdbus-glib-1-20.108-1
ii libdvdnav4 5.0.3-3
ii libdvdread4 5.0.3-2
ii libgdk-pixbuf2.0-0 2.36.2-1
ii libglib2.0-02.50.2-2
ii libgstreamer-plugins-base1.0-0 1.10.2-1
ii libgstreamer1.0-0 1.10.2-1
ii libgtk-3-0 3.22.5-1
ii libgudev-1.0-0 230-3
ii libnotify4 0.7.7-1
ii libpango-1.0-0 1.40.3-3
ii libsamplerate0 0.1.8-8
ii libswscale4 7:3.2.2-1
ii libtheora0 1.1.1+dfsg.1-14
ii libvorbis0a 1.3.5-4
ii libvorbisenc2 1.3.5-4
ii libx264-148 2:0.148.2728+git4d5c8b0-1
ii libx265-95 2.1-2
Versions of packages handbrake recommends:
ii gstreamer1.0-libav 1.10.2-1
ii gstreamer1.0-pulseaudio 1.10.2-1
ii gstreamer1.0-x 1.10.2-1
handbrake suggests no packages.
-- no debconf information
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#850443: libdvd-pkg: Please recommend the regionset package
Package: libdvd-pkg Version: 1.4.0-1-2 Severity: wishlist Hi there, it is nearly always required to at least once set a region code on a new DVD drive. Thus, please add the "regionset" package as a Recommends, either of the libdvd-pkg package itself or of the resulting libdvdcss library package. Thanks! - Fabian -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ___ 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#843638: same problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Montag, den 19.12.2016, 12:56 +0100 schrieb folkert: > > > Yes. Well it no longer segfaults at start-up. Things like finding > loops > in samples works fine. Wait, did you rebuild the package with autoconf/configure or cmake? It seems that the former links the plugin against libfftw3, whereas the latter links it against libfftw3f. - Fabian -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlhYAy4ACgkQy+qOlwzN Wd+DDxAAvVCUZZUkgqFh2DAPe7ixDXi79PpnsO15lQbFNTJd4LZpNIlEpngeUcQF itL/keShvg6jP1/1GPoEzcEBhwN8pp6dkg3FiqWwDSEMM9PvFzhdXa7uglryeGhB K6dUI6LvA9LtVdZJY5iEfBTmgcWWEQAnT2WCt7S8EALHa5BryI/zAL73DqlQwtsS G67soufdAmQ0t2y4yy6KyqFO8vW77rWX+NV0AIelKHCKmG43kzg/LHS/A3D8Cm56 Sag5fSA0yeP8B9b1Ff0GSwjSpjntoGymO9ZqvWl+B9YeJbQEmYcQBz5vGyOzzQrY g8Tpcs7xQBfW7KyR266PwITQtpdWt8+/A7wQI2e9ob/akLdVNLHozqqmXJlCTOSi 8PYxP4qlflUFaAskDeTI2AhXPdX7YQ2q0yqrRWc/iddYs//N1DT6TN7YvYwpjk+P mWpBqvJpa0iY480kXuh6EU0ZWdTZ5/aWp6QnI9YV6qDZPTUsveMmUPHDyfEaNC5g nX+PK6dUoUq1JsPGHw8PZKnDI/+Bx7oxUGSGiypil7e8rHczbzL7U0zJrFCU1yhQ HxEtl9Xg0p31EDSzl5OBJZXeqioUiRhsT8NHSMQtSoSG7CmHoo1cDK+C5Xfnhj2a 3AP+9cibRV5htNqfIt8G0pEfmdfCh5tMyjRPYFkjFh4e9nImgKI= =GHPs -END PGP 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
Bug#843638: same problem
folkert wrote: > Apparently autogen and intltool were missing and not in the build-dep. You seem to use the package from testing. Package swami (2.0.0+svn389-4) from unstable already has this build-dependency fixed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837841 > After building the package from the sources from the deb-src, the > program runs fine! Even the fftune plugin? That'd be strange, since the code calls both fftw_free() and fftwf_free(), whereas the libfftw3f.so.3 library, against which the plugin links, only exports the latter. - 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#843638: same problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Freitag, den 16.12.2016, 18:51 +0100 schrieb Folkert van Heusden: > You mean build-essential? > That I have installed. Also libtool. Nope, I meant "apt-get build-dep " to install a package's build-dependencies. - Fabian -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAlhUMw4ACgkQy+qOlwzN Wd/V5g/9F0Q/iIWcGwdZtyzmbTmcGR9+rbnEg3g7ebfCfPnkRdtrxWCxVIdqfuYu hOv3TdwnnHiBajmW3F4EOaBc8q7yzgcyyxrJJmB7W09XemeIm/qn3jmY/d98FYyB HG6kkx35v8JjYBBbn1rXijwBxvAkFfajAqnBG7m52I7O3VL0DftqKcZQsaYxBKly bfrEhtSTxkbaZmF9jS7fi7Cl5Q7MMC066mLg1rnjSs6xwcwKITZbZmtW1Y+lZnYu Gc6Ue5qZs9jiH3LfC7w7Y4Mi+lNIsoS+amZr0IqYF8zt/uPStn1kA1IYZ85f+Ocs ke1p8SzBJlZtNGc4lWOI7srPkQB97411XeoWIb4N/yiRp8/+Lkz518p0qpS0ppPd sDUOFrUPUEwdAPg2ZabCt24kUS/8uI3VCldoED4Cyhw68JBUZ/i/opAP/RrGs70Z UBvYG2MPvOQQQ/3dQuRT17evQ+4U02ihTSDnsO+QfyJ7IrSzM55uNI5MYX+0lnCK qRiCbUXNJVi/lTHg3vX2/4SG5N6frbwJ1YT7SXrH6v8o1FZGZPe2hXK96aVOh0U/ 1EtxeyWs/BIqvD1WLZmJBDD5HSD5LccKcLqai5ssoaLJEqcAkmVN5lVCs0Cim1lE m+P8b3pSA+i9LtFhuRRXt84zHb/Hc2nb4piG3d8ddnr4YE91CX8= =ziRE -END PGP 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
Bug#843638: same problem
folkert wrote: > Tried building it from source (apt-get source + dpkg-buildpackage) You seem to forget "apt-get build-dep". - 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#843173: libfaad-dev: Implicit SBR detection via AudioSpecificConfig fails when char is signed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: forwarded -1 https://sourceforge.net/p/faac/bugs/207/ control: tags -1 + patch -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYH0/0AAoJEMvqjpcMzVnf2tcQAKUTqkG1Wgv8eOjkMwgf6LI5 v4Iq93y2das6g/3VrXbmaba3x2I1ZnIONP6HBa/+9qpXkqkw4qvPpCNZ9F8XBcUf lS7BQUfINosIX0Z1WAuaKUtxT+TP8h1RlAiPyYjY/wD8QRl0zbycDqfzLnX1iWbB ee0Bf9GMPQI2RlR/1g4qJhSSG6aUcBwgejq1xRiJlB0EFj97XAAAXNmwp2Hirfy6 xDXpzMJDNuk14f/YU4ZYjMRrqh6ts4xI+rBgjDvoeX8e1qDDoCp44fAv6MbTyp4x bCEGvGkaY/dz2MCYDTZZpBgA0eNlT2sd69hZZCZyKYIJREBXwMhXd4YJPOlmHuj9 ghs3pJgkDW6gOZ7WCD9lvSfZI3Tc9/OcAKgN38CPMxBP7WEDaE2yC6oBh5HRL25L 59xeYX82RrzCGoUBPFO41so3UB33UClSdTP6TicCXpW6Vqc8ZVZFtCYFgE+jt/jC CgRx4TQqAdsjokIw7i2ni3Q9eUDy23viWSIz+BU45YVf5yU6B/LPfQ2mTOy+MJih tRbitqYao8FgVKqHRRIZngIXRrBEPF+TTqykwLeGTpahzKngRcyLLTJ3nJ/m1Yw1 38dBWYos97C3C3eUv1SF5tPl3a2C9FJpSdwm9b9FKJ/iqEbQv/8GhVs7+itN5OWh td8T0q0hVhv7suGqmN5G =yzLX -END PGP 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
Bug#843173: libfaad-dev: Implicit SBR detection via AudioSpecificConfig fails when char is signed
Hi again,
will it help if we explicitely cast the (-1) to char in the two
occasions where it is used for sbr_present_flag?
- Fabian
diff --git a/libfaad/mp4.c b/libfaad/mp4.c
index 72b2af6..14e607a 100644
--- a/libfaad/mp4.c
+++ b/libfaad/mp4.c
@@ -174,7 +174,7 @@ int8_t AudioSpecificConfigFromBitfile(bitfile *ld,
#endif
#ifdef SBR_DEC
-mp4ASC->sbr_present_flag = -1;
+mp4ASC->sbr_present_flag = (char)-1;
if (mp4ASC->objectTypeIndex == 5)
{
uint8_t tmp;
@@ -276,7 +276,7 @@ int8_t AudioSpecificConfigFromBitfile(bitfile *ld,
/* no SBR signalled, this could mean either implicit signalling or no SBR in this file */
/* MPEG specification states: assume SBR on files with samplerate <= 24000 Hz */
-if (mp4ASC->sbr_present_flag == -1)
+if (mp4ASC->sbr_present_flag == (char)-1)
{
if (mp4ASC->samplingFrequency <= 24000)
{
signature.asc
Description: This is a digitally signed message part
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#843173: libfaad-dev: Implicit SBR detection via AudioSpecificConfig fails when char is signed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Stefan, thanks for the bug report! Did you mean to write "fails when char is unsigned" in the subject line? Am Freitag, den 04.11.2016, 16:18 +0100 schrieb Stefan Pöschel: > One way to fix this is to make the struct variable sbr_present_flag > signed. > Another way is to enforce signed char by compiling FAAD2 with > -fsigned-char. I see that the fix is rather trivial, but wouldn't it introduce an ABI (not API) break? - Fabian -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYHjQrAAoJEMvqjpcMzVnfgkoQAOMWHhbkhl5QJ4c+O3EEmtBQ Doyz8HezqGLWud0PmHf9YOO7EK+gQusqN/3M/T/Qpe0/xbRE35ZiDO1kxNmiZk0O OPdrihKkSF5LWbYqJE3QgZ9gRcFtWx0OB4YeVkjoCTi+bhEPDwPrzxLQtAo2sqtB Sf39DsK6++zQfQNAzyxRZyVw6oKg9B9XuDblFcNUD16MgOCxlVlTswVR2iCD0+Pd 299geikSfG292LrFGiZD8PBE9S961mt4QXDAtcEdiznKrI6oZRpyShOPWWQPyqqm x6y/MlatAUeBEXfngRibdxyIT23edZUPAhyfvuhD0blgB5cYYYHZ/vKnXZjfEurA lEpor/KZA9QueKt31nLN5cpFPOGN5DtQX9Sy7AG9Cthcqyky9BWK2FnEEd8YFsYL NgJa4kbFEYbOl1UnBbSarQz8g69tXcfk2gshzJvU/+SaQKNEsyBrLoWNen9gkYEd c+3z0TPBAXVNw/MNA8LASapRPU6SLT7liqnb+RkdNB8Qnj+HLkwtWQyq67o+O9de UvU2jXkwCK4tTSjM++fMRKJFSAV7aCFQR4KeGrvfPDz9E89rkzPwPeI6uUnGSaND hYnYBGAPLZ37eDYA2uUkSf0ShGJn/OGOcyIyGji9XJyeWBKfewBG3KGO/JpNsSHB Aw1oAfQjVWnAoWuGfSal =wauB -END PGP 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
Bug#842235: handbrake: Crashes with unusable output file on some DVD titles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please do not answer to me privately, but do always reply to the bug address, thank you! 1) Please add the debug repositories to your sources.list file: https://wiki.debian.org/AutomaticDebugPackages 2) Please install the ffmpeg-dbgsym and the handbrake-dbgsym packages 3) Please install gdb and run handbrake from gdb, e.g. $ gdb handbrake (gdb) r 4) Please proceed until the assertion kicks in and provide a backtrace from there: (gdb) thread apply all bt full This is desribed in more detail here: https://wiki.debian.org/HowToGetABacktrace Please report the backtrace to the bug, thanks! - Fabian Am Donnerstag, den 27.10.2016, 18:55 +0200 schrieb Ax. St.: > Absolutely. Please tell me which debug symbols package I need to > install and how to get > the information you need. > > Axel > > $ aptitude search 'ffmpeg' > p cmus-plugin-ffmpeg 0 sound lightweight > ncurses audio player (FFmpeg plugin) stable > p ffmpeg 0 video Tools for > transcoding, streaming and playing of jessie-backports > p ffmpeg- > doc 0 docDocumentation of the > FFmpeg multimedia framework jessie-backports > p ffmpeg2theora 0 video Theora video > encoder using ffmpegstable > i A ffmpegthumbnailer 0 video fast and > lightweight video thumbnailer stable > p ffmpegthumbnailer-dbg 0 debug debugging > informations for ffmpegthumbnailer stable > p ffmpegthumbs 0 kdevideo > thumbnail generator using ffmpeg stable > p gmerlin-encoders-ffmpeg0 libs ffmpeg > encoders for Gmerlin stable > p libffmpegthumbnailer-dev 0 libdevel development > files for ffmpegthumbnailer stable > i A libffmpegthumbnailer4 1 libs shared > library for ffmpegthumbnailer stable > p libtaoframework-ffmpeg-cil-dev 0 cli-mono Tao CLI > binding for FFmpeg - development files stable > p libtaoframework-ffmpeg0.4-cil 0 cli-mono Tao CLI > binding for FFmpeg stable > p libxine2-ffmpeg0 libs MPEG-related > plugins for libxine2stable > p moc-ffmpeg-plugin 0 sound ncurses > based console audio player - ffmpeg plug stable > > On Thu 2016-10-27 12.17.40, Fabian Greffrath wrote: > > > reproduce the crash in GDB with the ffmpeg debug symbols installed > > and > > provide a backtrace? > > -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJYElzBAAoJEMvqjpcMzVnfb2YQAKkL/K85S0v5wqcjopp1Yv5T QkgrHXz1cATAzCo6PlarwgA9OX68ID9Ag/0bRl+NVYT51qEXoWPxIJscY2hyoRNz U3KLWqIi7C5jj8/KgHNeSTHZxLYfJZ4L2UsHsc6E4+3EAQtzo9bXF4B2okc8Ze31 n+dMECgWZRKVW1kQQPnuiDG7lS03Al0fkaoHsWLkWt5t+Be1sZre38/XSJLptpjX sGA+IsBB7iuYGS7j7zYhEiG5Z59xjdCaplgbychjDEpX3UlIfvMx65cufFxB5rtS JgLhfVAml4VC+s2/Z7FGlOptHqYzJhHJhnNmWvsDrX2Xd3NKRa44l+gFCmY0lJC9 dSQJ1ftUWSQ8xHZM9doWhQQxwmoQob4BFGK3FW09RwtZyCtX7R4SBNfB4cBqRxMR 4bkIHXWiVlUWUf3tOerYX1tyuBnYsdKg3wZCv+UMsul3NnIlcZOxcaqd5wO2WVyR fg+73iwzgkeFWxgrpTj2Gvw01FmlCXeq8PYwvGuvl3FTphzLm2AoO0oBhtRHMOE2 IzJkK9rno+dNtxs4ho2FdwHsx/JDyOODwUqVjk5KzPaNW0J2bwOJ59PMdwKFi6Ad tTTskxeubbNRvgBXdEqWepdc9o9paEWTnZj+SgTMJh5IiuZLg9hovpUYyBlO0K5M CdvoX/43TmmKADvubbM3 =R72Z -END PGP 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
Bug#842235: handbrake: Crashes with unusable output file on some DVD titles
Axel Stammler wrote: > 00h01m30s)HandBrakeCLI: > /build/libav-Ofh2VJ/libav-11.8/libavcodec/put_bits.h:139: > put_bits: Assertion `n <= 31 && value < (1U << n)' failed. > Aborted Since this hits an assertion in an ffmpeg header, could you please reproduce the crash in GDB with the ffmpeg debug symbols installed and provide a backtrace? - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: remove xbmc from Debian testing/unstable?
Bálint Réczey wrote: > Are you suggesting some other solution? I'm not sure I understand it then. > Xbmc has epoch which I got rid of with kodi. I'd suggest to re-apply (and maybe even increment) xbmc's epoch for kodi. What's the point in getting rid of an epoch, why is it even important? - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: remove xbmc from Debian testing/unstable?
Bálint Réczey wrote: > If you have any good idea please share it, otherwise I'm revert to > provide the transitional packages from xbmc. Epochs have been invented for this exact use case. - 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#841868: Segfault in Gtk::Widget::show() since upgrading to 5.*
It's just a wild guess, but this Pietro Battiston wrote: > Package: ardour > Version: 1:5.4.0~dfsg-1 [...] > ii ardour-data 1:4.2~dfsg-5 just doesn't seem corect to me! - 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#840373: Instructions are wrong for MP3 conversion
Akkana Peck wrote: > The instructions also say to add the deb-multimedia repository to > apt sources; but even after I did that, This is nearly always wrong for all but very unusual requirements and I am a bit shocked to see upstreams still recommend it! > I know the page is part of the upstream project, but I'm hesitant to > be the one to tell them to change it in case there are other > versions of Debian for which it's right. Maybe they need to specify > different instructions for different Debian versions? Lame and its gstreamer plugin are available in all supported Debian releases. The only difference is that it's gstreamer0.10-* in oldstable and gstreamer1.0-* in stable and newer, AFAICT. > Versions of packages soundconverter suggests: > pn gstreamer1.0-plugins-ugly Maybe this should get promoted to a Recommends and everything will be fine. - 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#840242: mpv fails to load libmp3lame.so.0
Nicolas Braud-Santoni wrote: > The error might belong to libmp3lame, > but I'm not entirely sure how to check this. Please report your libmp3lame0 package version $ dpkg -l libmp3lame\* and the library path chosen by the dynamic linker $ ldd /usr/bin/mpv | grep mp3lame Thanks! - 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#838186: [handbrake] No audio in output file
Hi there, first, what version of reportbug have you used to submit this bug report? The version numbers for the ffmpeg (and many other) libraries are not reported in the template. Am Sonntag, den 18.09.2016, 09:17 +0100 schrieb Antonio Marcos López Alonso: > Debian Release: stretch/sid > 900 testing ftp.pt.debian.org > 500 xenial ppa.launchpad.net > 500 wilyppa.launchpad.net > 500 unstableftp.pt.debian.org > 500 trusty ppa.launchpad.net > 500 stable update.devolo.com > 500 stable kxstudio.linuxaudio.org > 500 stable dl.google.com > 500 sid linux.dropbox.com > 500 lucid ppa.launchpad.net Erm, this doesn't really read like a valid combination of package sources that we might want to support. Please make sure all library packages that are reported as dependencies for handbrake are the ones from the official Debian mirrors. Thanks! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: dvd-slideshow depends
Herbert Fortes wrote: > I did not understand. xorriso[0] Debian package is from > libisoburn source package. Sorry for causing confusion! I just remembered that GNU xorriso was not exactly the same as libisoburn's xorriso. We package the latter in Debian, but the link you provided in the context of missing UDF support pointed to the GNU xorriso page. Anyway, the only difference seems to be that GNU xorriso has all the libraries bundled togther and is statically linked, whereas libisoburn's xorriso requires all the other libburn libraries separately and is dynamically linked. Feature-wise, they seem to be identical. Cheers, Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: dvd-slideshow depends
Am Montag, den 12.09.2016, 15:41 -0300 schrieb Herbert Fortes: > So mkisofs will be replaced by genisoimage. I said xorrisofs > before, but it seems that xorrisofs "does not produce UDF > filesystems"[2]. Bad because xorriso project is more active > (2016). genisoimage stopped in 2014. I am not sure if GNU xorriso has the same features as the program of the same name from the libburn project? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Mayhem bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Montag, den 08.08.2016, 23:59 +0200 schrieb Jaromír Mikeš: > Ok ... I am going forward them upstream. Oh, wow! Has upstream really fixed all of the Mayhem crashes with two simple code changes in the 1.0n release? Cool! ;) - Fabian -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXthBCAAoJEMvqjpcMzVnf2tEP/2xfDI3aI8Iju7gibu0YVna0 tbkp+cEaug/pF9gN6BG3rWSXWhqahvBJt49oMHPHPwl6dh1ZxCB7LftLTLODbdNp /r36uxgVCviIo3z4BcJMvMrXxDkM/VBwS+zf627saj/PmUcu0U9UXjCmhssATPx2 evqOwtgNFtHNmEV4w8PTq+Dtxss1eHq/ey5ZmH+6n2aCetfWqx3N6HhBoFgdUYvJ l03kzGHgOLDQ/VJpK+DRkpS+cx3nsJaJRhvrR4ZUaH2mUMR22fOalpO4DKiPehFA YvuhvQbncuFzwG5nroqJqQlk/LdqNY5M09t+zHZbxSH+yltW1tkYOk5B/jDe7nL/ PVyJ9Zpb8x6ejAJvdKlz2Q4T1XAJZGmVR7BsAIi3bWSVu4MfQc6mjzwBNdtvZGba aja5eSRB+KOKYet6CRO/ux/fUa4e9pg/lNb/EvpSqq43lSIjCK0eu0fVF7P+fHZh KqtPh/CkkhaRsH0XiWN2FOqc8onnMBMCeW3fCy4tLztSSUZ4l4OqYKGwLoaylpT5 sq9lULIF+5I4z90T57BP8w43Jg3IT+vDM62Xli4CTBpy/IX+crmAUjCzXqI7M2zd jPLzm4kYqP+sM4ZxkF8pAiPTwQd5/BToGYKwGagF28/eBGQQmIPuIZt6PHzshShY csku4SeKxUHs9Rd+h6qS =fJE0 -END PGP 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: Re: Source: libvpx vs hardening all
> Yes, this is a short comming in the Debian package build process. > There are source packages (like libvpx) from which library AND binary > packages are build. s/binary/executable/ ? > https://wiki.debian.org/Hardening should a little bit more concise about > this! Reportedly, "libtool filters -fPIE, -pie and -fpie when compiling shared libraries, so anything using autotools + libtool should automatically be covered": https://lists.debian.org/debian-devel/2016/05/msg00302.html - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] giada/master: Add patch to build with gcc6 (Closes: ##831183).
Am Montag, den 25.07.2016, 15:56 +0200 schrieb Jaromír Mikeš: > I will pass this question to upstream. This question was rhetoric, it won't fit. You have 8 bytes in the buffer, two of them are used by " L" or " R", respectively, and another one for the '\0' delimiter. This means 5 bytes are left for the floating point number, of which one is the decimal dot. That it, you must delimit the floating point formater to something like "%3.1f" for it to fit into the string buffer. Or, given that upstream apparently intended to output integers, maybe "%5.0f". - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] giada/master: Add patch to build with gcc6 (Closes: ##831183).
> this patch fixing build of giada package with gcc6, but now it is not > build with gcc5 with pbuilder :( > Help needed please. I can only guess since you are not providing any build logs, but there is one thing in your patch that made me wonder. You are writing floating point numbers in 'char buf[8];' buffers. Are you sure that they will fit? - 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#824956: Re. the Musescore situation in sid
Am Sonntag, den 17.07.2016, 16:24 +0100 schrieb James Cowgill: > Woops I think that was my fault. It should be fixed in 2.0.3+dfsg1-2. Thanks for taking care of this! Is there a way to tell pbuilder to build arch:all and arch:any parts separately, so bugs like this become apparent during a usual build? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#824956: Re. the Musescore situation in sid
Am Samstag, den 16.07.2016, 19:17 + schrieb Thorsten Glaser: > I’ll compile and test it now (modulo time needed for cooking, > eating, etc). and mail back. Ah, whatever. It compiled fine and so I uploaded it. So users can upgrade their sid systems. Everything else could be buffed out in a revision -2 upload. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Re. the Musescore situation in sid
Hi Thorsten, I could do a team upload of the current state in GIT this evening. Could you confirm this is fine for uploading as it is now? - Fabian Am Samstag, den 16.07.2016, 12:18 + schrieb Thorsten Glaser: > Hi everyone, > > the version in the packaging repository allegedly fixes the > problem with the new Qt version. If it works as-is, can an > NMU be done to get people able to dist-upgrade their sid > systems at least, even if the version in the packaging git > is UNRELEASED? > > I’m considering building it as 2.0.3+dfsg1-0.1 locally (on > x32) and testing that it at least works for basic functions, > but I need a willing sponsor. Otherwise, if someone else > does it, that’d be just fine with me as well. > > Thanks in advance, > //mirabilos (current hat: music performer) signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: musescore 2.0.3+dfsg-1
Hi Peter, Am Freitag, den 15.07.2016, 14:16 +0100 schrieb Peter Jonas: > the policy itself. This policy explicitly allows bundling when a > package is "explicitly intended to be used in this way." MuseScore is I am sorry but I believe that Jonas is right and you misunderstood this part of Policy. It reads "Debian packages should not make use of these convenience copies unless the included package is explicitly intended to be used in this way". In this case *the included package* is freetype and it is definitely not intended to be used this way. Policy is rather explicit on how to further proceed in this case: https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles So, what libraries could probably be intended to be used this way? I think there are only very few exception, for example speed-optimized math libraries with hand-crafted ASM code that would suffer from register shortage on certain architecture of compiled as PIC (e.g. djbfft); or maybe header-only libraries that only consist of static inline functions and macros (though I currently have no example for these at hand). > not likely to be a priority for the developers of Freetype. MuseScore > needs to know the exact size and position of every symbol on the page > to be able to lay them out efficiently without causing collisions. In > an ordinary text document slight differences in kerning between > operating systems might cause a word to be moved onto the next line, It seems to me what Musescore is actually looking for is an entire static font rendering stack. Please note that freetype is only a part (though a very important) of the whole font rendering stack. There are plenty other libraries involved that could modify the result of fonts being rendered on screen, e.g. harfbuzz, fontconfig and pango/cairo. I am sure you are not going to include known-working copies of these as well. Also: $ zgrep CVE /usr/share/doc/libfreetype6/changelog.Debian.gz | wc -l 53 So, no, please don't do that! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: musescore 2.0.3+dfsg-1
Hi again, Am Donnerstag, den 14.07.2016, 17:18 +0100 schrieb Peter Jonas: > Freetype is included because not included for convenience. It is > included because MuseScore's code has been tailored towards a > specific > version of Freetype and other versions of Freetype have been known to > cause problems in the past. hm, I still don't really buy this argument. Some more thoughts on this matter: 1) Debian Policy should always have top-priority for decisions to be made regarding software that is maintained in Debian. If "but upstream may complain" is reason enough to grant an exception from Debian Policy, then we may sooner or later end up with more exceptions than rules. 2) We should ask ourselves *why* upstream is embedding libfreetype. If they want the best font rendering result for their users, please feel certain that Debian wants to achieve the same result with its own library package. I don't see why musescore is so much more tied to a specific font rendering library version than other more complex applications. And if it is, this somehow tastes like bad practice. 3) We should ask ourselves *what* upstream is actually embedding. If they are embedding a pristine copy of libfreetype, I don't see any problem with using Debian's version either. If they are embedding a modified version with non-upstreamed changes, they are actually creating a fork. Are we as the pkg-multimedia team in a position to maingain a fork of a library such as freetype for the sole purpose of being used in one single package? Also, please keep in mind that for some time especially freetype could have been used to sneek in potentially patented font rendering code paths -- although I am not saying that this is happening here or has ever happened at all. Cheers, - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: musescore 2.0.3+dfsg-1
Hi there, Am Donnerstag, den 14.07.2016, 11:18 -0400 schrieb Tiago Bortoletto Vaz: > lot! I agree with Peter about Freetype inclusion. I've had a not so > good > experience on reporting issues to upstreams when using a slightly > modified version of MuseScore. So, for the sake of piece I'd just > keep sorry, but I have to disagree. Debian has a policy and that explicitely discourages embedding convenience library copies in §4.13: https://www.debian.org/doc/debian-policy/ch-source.html#s-embeddedfiles - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#591904: libavcodec52: text relocations on AMD64
Control: tags -1 moreinfo Am Sonntag, den 03.07.2016, 18:54 +0200 schrieb Carl Eugen Hoyos: > Is this still reproducible? > Why is this an issue? I don't remember that this was ever reported > upstream > (text relocations on x86-32 are reported on a regular basis). Tagging as moreinfo. signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#493705: ffmpeg-debian: Libraries have text relocations
Control: tags -1 wontfix Am Sonntag, den 03.07.2016, 18:47 +0200 schrieb Carl Eugen Hoyos: > Same as for #528080: This will not be fixed in FFmpeg upstream, so I > suggest > to close as wont-fix. Tagging as wontfix, but not closing. signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#528080: ffmpeg-debian: ffmpeg still has shlib-with-non-pic-code lintian errors
Control: tags -1 wontfix Am Sonntag, den 03.07.2016, 18:45 +0200 schrieb Carl Eugen Hoyos: > Different FFmpeg developers have explained repeatedly (including > recently) > that this will not be fixed within FFmpeg, so I suggest to close this > bug > report as wont-fix. Tagging wontfix, though not closing. signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Bug#625944: libavcodec52: JPEG produced with Intel JPEG lib loaded upside-down
Hi Carl Eugen, Am Sonntag, den 03.07.2016, 18:17 +0200 schrieb Carl Eugen Hoyos: > This issue was fixed five years ago in FFmpeg, please close. you can close bugs yourself by sending a mail to -d...@bugs.debian.org i.e. just append "-done" to the bug's general mail address. No need to ask others to do this. ;) Cheers, Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: bluray burning
Hi Nicholas, > issue... Given that cdrkit still cannot reliably burn BDRs, and a have you already checked libburnia and its cdrecord-clone cdrskin? https://packages.debian.org/sid/cdrskin > precedent for allowing CDDL software in the archive, with minor > acrobatics, I believe it is possible package a cdrecord-building > package similar to ttf-mscorefonts-installer, one of the ZFS packages, > or maybe libdvd-pkg. I would like to do the work myself and to Rumor has it that the main problem with cdrecord was not only its license... > Is libdvd-pkg the most appropriate package to model mine on? From I am still not sure about this model. It seems to have its own set of issues, like this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824078 Cheers, 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#823940: blender: please make the build reproducible (timestamps)
Source: blender
Version: 2.77.a+dfsg0-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi!
While working on the "reproducible builds" effort [1], we have noticed
that blender could not be built reproducibly.
Specifically, the current system time is used to define BUILD_DATE and
BUILD_TIME in build_files/cmake/buildinfo.cmake, obviously rendering
the build unreproducible.
The attached patch uses SOURCE_DATE_EPOCH [2] instead of the current
time. This should make the build reproducible.
Regards,
Fabian Wolff
[1] https://wiki.debian.org/ReproducibleBuilds
[2] https://reproducible-builds.org/specs/source-date-epoch/
--- a/build_files/cmake/buildinfo.cmake
+++ b/build_files/cmake/buildinfo.cmake
@@ -134,8 +134,13 @@
# BUILD_PLATFORM and BUILD_PLATFORM are taken from CMake
# but BUILD_DATE and BUILD_TIME are platform dependent
if(UNIX)
- execute_process(COMMAND date "+%Y-%m-%d" OUTPUT_VARIABLE BUILD_DATE OUTPUT_STRIP_TRAILING_WHITESPACE)
- execute_process(COMMAND date "+%H:%M:%S" OUTPUT_VARIABLE BUILD_TIME OUTPUT_STRIP_TRAILING_WHITESPACE)
+ if(DEFINED ENV{SOURCE_DATE_EPOCH})
+ execute_process(COMMAND date "-u" "-d" "@$ENV{SOURCE_DATE_EPOCH}" "+%Y-%m-%d" OUTPUT_VARIABLE BUILD_DATE OUTPUT_STRIP_TRAILING_WHITESPACE)
+ execute_process(COMMAND date "-u" "-d" "@$ENV{SOURCE_DATE_EPOCH}" "+%H:%M:%S" OUTPUT_VARIABLE BUILD_TIME OUTPUT_STRIP_TRAILING_WHITESPACE)
+ else()
+ execute_process(COMMAND date "+%Y-%m-%d" OUTPUT_VARIABLE BUILD_DATE OUTPUT_STRIP_TRAILING_WHITESPACE)
+ execute_process(COMMAND date "+%H:%M:%S" OUTPUT_VARIABLE BUILD_TIME OUTPUT_STRIP_TRAILING_WHITESPACE)
+ endif()
endif()
if(WIN32)
execute_process(COMMAND cmd /c date /t OUTPUT_VARIABLE BUILD_DATE OUTPUT_STRIP_TRAILING_WHITESPACE)
___
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#817199: transcode: should this package be removed?
Am Sonntag, den 13.03.2016, 21:25 +0100 schrieb Sebastian Ramacher: > Yes, dvdwizard would have to be RoQ-ed if we are going to remove > transcode. But it's also dead upstream and orphaned. Alright, let's go for it. Anyway, since transcode is a command-line utility, it should be rather straightforward to convert dvdwizard to use something more advanced, e.g. ffmpeg. But until someone who urgently needs dvdwizard volunteers to do this, I think it should be alright to remove it from the archive. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#817199: transcode: should this package be removed?
Am Dienstag, den 08.03.2016, 23:39 +0100 schrieb Sebastian Ramacher: > What do you think? No objections, except for this: $ apt-cache rdepends transcode transcode Reverse Depends: transcode-doc xjadeo transcode-dbg multimedia-video python-mecavideo dvdwizard It appears that at least dvdwizard has a hard Depends on transcode. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#740710: problem with SF3 playback
Hey Hamish, Am Dienstag, den 01.12.2015, 15:30 +1100 schrieb Hamish Moffatt: > I've reported it to MuseScore: > https://musescore.org/en/node/89216 > > and also to sftools, since the issue could be there: > https://github.com/wschweer/sftools/issues/14 > this is great, thank you very much! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#740710: problem with SF3 playback
Hi again, Am Samstag, den 28.11.2015, 11:14 +1100 schrieb Hamish Moffatt: > loopstart = loopend = 0 fixes it. > > Yes, I do see the problem in MuseScore (2.0.2 release). Interesting. Maybe it would help if you could report the issues you encountered over at MuseScore. They are somehow "upstream" for the SF3 sound font format and it would be interesting to know their opinion e.g. about the stray notes. Please tell them how you composed your compressed sound fonts and also that forcing loopstart = loopend = 0 apparently fixes the issues. Would you do that, please? Thank you! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#740710: problem with SF3 playback
Am Samstag, den 28.11.2015, 11:14 +1100 schrieb Hamish Moffatt: > loopstart = loopend = 0 fixes it. > > Yes, I do see the problem in MuseScore (2.0.2 release). Interesting. Hah, I think this is good news. Since MuseScore is the reference implementation for sf3 sound fonts support I consider it a success that FluidSynth with my patch sounds the same. Even if this means that there are the same artifacts. Honestly, I think now the sound font or the software that created it is to blame for setting wrong loopstart and loopend values. Resetting them both to 0 is really just a hack that should be avoided. Thank you very much for testing my patch! Cheers, Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#740710: problem with SF3 playback
Am Freitag, den 27.11.2015, 12:39 +1100 schrieb Hamish Moffatt: > I'm afraid that while this plays correctly with FluidR3Mono_GM.sf3, I > have stray notes again with other sound fonts. Do you also have these stray notes if you play back the MIDI in Musescore using these other sound fonts? Do you also have these stray notes if you forcefully reset loopstart and loopback, like in my previous workaround? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#740710: problem with SF3 playback
Hi Hamish,
Am Dienstag, den 24.11.2015, 22:40 +1100 schrieb ham...@cloud.net.au:
> Thanks Fabian. I will try tomorrow.
I think I found the real culprit: I had an off-by-one error in the
calculation of the sample sizes. In FluidSynth, sample->end points to
the last valid point in a sample, not to the first point after. This
means that all samples were calculated one byte too short.
Now, all samples are correctly decoded, i.e. there are no samples with
sfinfo.frames == 0 anymore. This also means that the loopstart and
loopend variables are now correctly set; the workaround of setting them
both to 0 that I previously suggested is not necessary anymore. Also,
most of the quality loss that I originally blamed on the compression
seems to be gone now.
Please find a new patch attached.
Thanks,
Fabian
Description: Add support for sound fonts in SF3 format that contain Ogg Vorbis compressed samples
Author: Fabian Greffrath
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740710
Forwarded: https://sourceforge.net/p/fluidsynth/tickets/142/
Last-Update: 2015-11-26
--- a/include/fluidsynth/sfont.h
+++ b/include/fluidsynth/sfont.h
@@ -270,6 +270,7 @@ struct _fluid_sample_t
#define FLUID_SAMPLETYPE_RIGHT 2 /**< Flag for #fluid_sample_t \a sampletype field for right samples of a stereo pair */
#define FLUID_SAMPLETYPE_LEFT 4 /**< Flag for #fluid_sample_t \a sampletype field for left samples of a stereo pair */
#define FLUID_SAMPLETYPE_LINKED 8 /**< Flag for #fluid_sample_t \a sampletype field, not used currently */
+#define FLUID_SAMPLETYPE_OGG_VORBIS 0x10 /**< Flag for #fluid_sample_t \a sampletype field for Ogg Vorbis compressed samples */
#define FLUID_SAMPLETYPE_ROM 0x8000 /**< Flag for #fluid_sample_t \a sampletype field, ROM sample, causes sample to be ignored */
--- a/src/sfloader/fluid_defsfont.c
+++ b/src/sfloader/fluid_defsfont.c
@@ -26,6 +26,10 @@
/* Todo: Get rid of that 'include' */
#include "fluid_sys.h"
+#if LIBSNDFILE_SUPPORT
+#include
+#endif
+
/***
*
* SFONT LOADER
@@ -1582,6 +1586,14 @@ new_fluid_sample()
int
delete_fluid_sample(fluid_sample_t* sample)
{
+ if (sample->sampletype & FLUID_SAMPLETYPE_OGG_VORBIS)
+ {
+#if LIBSNDFILE_SUPPORT
+if (sample->data)
+ FLUID_FREE(sample->data);
+#endif
+ }
+
FLUID_FREE(sample);
return FLUID_OK;
}
@@ -1598,6 +1610,61 @@ fluid_sample_in_rom(fluid_sample_t* samp
/*
* fluid_sample_import_sfont
*/
+#if LIBSNDFILE_SUPPORT
+// virtual file access rountines to allow for handling
+// samples as virtual files in memory
+static sf_count_t sfvio_pos;
+
+static sf_count_t
+sfvio_get_filelen(void* user_data)
+{
+ fluid_sample_t *sample = (fluid_sample_t *)user_data;
+
+ return (sf_count_t)(sample->end + 1 - sample->start);
+};
+
+static sf_count_t
+sfvio_seek(sf_count_t offset, int whence, void* user_data)
+{
+ fluid_sample_t *sample = (fluid_sample_t *)user_data;
+
+ switch (whence)
+ {
+case SEEK_SET:
+ sfvio_pos = offset;
+ break;
+case SEEK_CUR:
+ sfvio_pos += offset;
+ break;
+case SEEK_END:
+ sfvio_pos = sfvio_get_filelen(user_data) + offset;
+ break;
+ }
+
+ return sfvio_pos;
+};
+
+static sf_count_t
+sfvio_read(void* ptr, sf_count_t count, void* user_data)
+{
+ fluid_sample_t *sample = (fluid_sample_t *)user_data;
+
+ if (count > sfvio_get_filelen(user_data) - sfvio_pos)
+ count = sfvio_get_filelen(user_data) - sfvio_pos;
+
+ memcpy(ptr, (char *)sample->data + sample->start + sfvio_pos, count);
+ sfvio_pos += count;
+
+ return count;
+};
+
+static sf_count_t
+sfvio_tell (void* user_data)
+{
+ return sfvio_pos;
+};
+#endif
+
int
fluid_sample_import_sfont(fluid_sample_t* sample, SFSample* sfsample, fluid_defsfont_t* sfont)
{
@@ -1612,6 +1679,87 @@ fluid_sample_import_sfont(fluid_sample_t
sample->pitchadj = sfsample->pitchadj;
sample->sampletype = sfsample->sampletype;
+ if (sample->sampletype & FLUID_SAMPLETYPE_OGG_VORBIS)
+ {
+#if LIBSNDFILE_SUPPORT
+SNDFILE *sndfile;
+SF_INFO sfinfo;
+SF_VIRTUAL_IO sfvio = {
+ sfvio_get_filelen,
+ sfvio_seek,
+ sfvio_read,
+ NULL,
+ sfvio_tell
+};
+short *sampledata_ogg;
+
+// initialize file position indicator and SF_INFO structure
+sfvio_pos = 0;
+memset(&sfinfo, 0, sizeof(sfinfo));
+
+// open sample as a virtual file in memory
+sndfile = sf_open_virtual(&sfvio, SFM_READ, &sfinfo, sample);
+if (!sndfile)
+{
+ FLUID_LOG(FLUID_ERR, sf_strerror(sndfile));
+ return FLUID_FAILED;
+}
+
+// empty sample
+if (!sfinfo.frames || !sfinfo.channels)
+{
+ sample->start = sample->end =
+ sample->loopstart = sample->loopend =
+ sample->valid = 0;
+ sample->data = NULL;
Bug#740710: problem with SF3 playback
Am Dienstag, den 24.11.2015, 11:09 +0100 schrieb Fabian Greffrath:
> This sure needs further investigation.
Got a bit further:
I forgot to adjust the sample->loopstart and sample->loopend values and
I am not even sure if they make sense at all for compressed samples. If
you wipe away this whole block in src/sfloader/fluid_defsfont.c that my
patch adds to fluid_sample_import_sfont()
/* loop is fowled?? (cluck cluck :) */
if (sample->loopend > sample->end ||
sample->loopstart >= sample->loopend ||
sample->loopstart <= sample->start)
{
/* can pad loop by 8 samples and ensure at least 4 for loop (2*8+4) */
if ((sample->end - sample->start) >= 20)
{
sample->loopstart = sample->start + 8;
sample->loopend = sample->end - 8;
}
else /* loop is fowled, sample is tiny (can't pad 8 samples) */
{
sample->loopstart = sample->start + 1;
sample->loopend = sample->end - 1;
}
}
and replace it with a simple
sample->loopstart = sample->loopend = 0;
the MIDI plays back as expected.
- Fabian
signature.asc
Description: This is a digitally signed message part
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#740710: problem with SF3 playback
Dear Hamish, thank you very much for tewsting my patch. Am Dienstag, den 24.11.2015, 16:26 +1100 schrieb Hamish Moffatt: > If you play the attached MIDI file with the FluidR3Mono_GM.sf3 file > (from MuseScore) loaded, you'll hear some extra garbage notes played at > the end. I can confirm this issue, but currently it is a complete mystery to me. I fail to see how the choice of a sound font (format) should affect the notes being played at the end of the MIDI? This sure needs further investigation. Thanks, Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#720603: closed by Sebastian Ramacher (Re: Bug#720603: missing files in devel package)
Hello, Am Montag, den 16.11.2015, 12:00 -0430 schrieb PICCORO McKAY Lenz: > seems that liblivemedia backports for squeeze do not have all files, > but wors its that Sebastian Ramacher does not help so much, he can > made a forward mail event "close" the bug! what a help! This is not Sebastian's fault. We cannot track bugs for backported packages in the regular Debian bug tracker. This is why he pointed you to this document ... > > For bugs in backported packages please contact debian-backports@lis > > ts.debian.org > > as described at [1]. > > > > Cheers > > > > [1] http://backports.debian.org/FAQ/ ... which properly describes what to do in this case. If you don't read this, it's hardly his fault. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: devede_4.3-1_amd64.changes ACCEPTED into unstable
Hi Alessio, Am Samstag, den 07.11.2015, 15:35 + schrieb Debian FTP Masters: > * New upstream release: > - Upstream's name changed to devedeng, this > keeps the old one. so, does this mean this is devede-ng? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: ardour transitional dummy packages
Am Dienstag, den 20.10.2015, 09:31 +0200 schrieb IOhannes m zmölnig (Debian/GNU): > when we should drop "transitional dummy packages"? > > until stretch has been released. s/until/after/ ? or "not until"? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: inquery about "GPL with commercial exception"
Am Donnerstag, den 08.10.2015, 23:39 +0200 schrieb Francesco Poli: > Just to be clear, my own personal opinion is that > "GPLv2 + restrictions" is self-contradictory and thus possibly void: > I would not consider software released under such terms as safely > distributable. FWIW, I share this view. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#798341: [inkscape] impossible to install inkscape
Am Dienstag, den 22.09.2015, 17:26 +0330 schrieb Tsu Jan: > I'm not a new Debian user: when I said I removed deb-multimedia, I > implicitly meant I removed all its packages too, although I reinstalled > them after I realized deb-multimedia was innocent -- because I needed them. Apart from the inkscape issue. Could you please tell us which packages from d-m.o you really need? Because, you know, we have already incorporated many of them into the official Debian archive and would really like to know which ones are considered missing. > I think you might know that the problem is deeper than Inkscape's case. > Several reports could be made for packages that aren't even remotely > related to deb-multimedia. It's a bit unfortunate that Debian doesn't do mass rebuilds of all packages, so transitions could happen "at once". Instead, packages are rebuilt one after another, often after manual intervention, and thus reach testing one after another, rendering packages in testing uninstallable until other rebuilt packages follow... > Last but not least, I like Debian and hope it won't have a fate like > that of Gnome3, although I see similarities in attitudes nowadays. Not sure what you mean here. But raising the finger while being vague about what features are considered missing (first paragraph) or what issues are encountered with other packages (second paragraph) is unfortunately not very helpful. :/ - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: setbfree DM flag
Am Dienstag, den 22.09.2015, 08:26 +0200 schrieb Jaromír Mikeš: > Thank you Fabian it is very flattering, but I am not sure if I am > skilled already enough. You are currently maintaining 111(!) packages, most of them single -handedly. Think about it, you've got my approval anyway. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: setbfree DM flag
Am Montag, den 21.09.2015, 20:01 +0200 schrieb Jaromír Mikeš: > ping ;) Done. You should really condider applying as a DD! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#760209: fluidsynth config file
Am Dienstag, den 22.09.2015, 00:13 +0200 schrieb Jaromír Mikeš: > my second email haven't been answered :( > Maybe I should subscribe to dev mailing list and post questions > there. Never mind then, I could do this myself. I was hoping you were in more direct contact with upstream somehow. Thank you! Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: Re: licenses for h2o drumkits (was Re: Sinevibes contact)
Am Montag, den 21.09.2015, 17:08 +0200 schrieb Jonas Smedegaard: > I would prefer the topmost of above. For non-code files I'd rather prefer a CC-* type of license instead of the GPL. Define the "prefered form for modification" for a drum kit? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#760209: fluidsynth config file
Am Montag, den 14.09.2015, 11:20 +0200 schrieb Jaromír Mikeš: > I discussed this with upstream ... If you are in contact with upstream, could you maybe ask them for a statement regarding this patch, please? https://sourceforge.net/p/fluidsynth/tickets/142/ Thank you! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#798341: [inkscape] impossible to install inkscape
Am Sonntag, den 20.09.2015, 15:15 +0430 schrieb Tsu Jan: > Dear maintainers, if by "unofficial repositories" you mean the excellent > work that is being done at "deb-multimedia.org", it's not to be blamed: Please elaborate what "excellent work" you are talking about specifically. > the current mess persists after removing it from "sources.list". I have This is not enough. You will also have to remove all packages installed from these repositories. Though, as has already been pointed out several times in this bug report, it does not help in this specific case. The solution is to wait until (1) libraries have migrated to testing and (2) packages rebuilt against migrated libraries have migrated to testing. If you are using Debian testing, you are using a rolling release. Either you get over the fact that it is "rolling" or you should use stable instead. > IMHO, the word "transition" has become a widespread excuse for the poor > maintenance. Each maintainer MAY do his/her job well enough but the lack > of coordination is obvious. Say, how would you organize a C++ ABI transition that affects some 1000 packages then? Also, applauding for the "excellent work" being done at d-m.o and at the same time complaining about lack of coordination among maintaners isn't going to support your point. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Bug#799338: ardour-data: fails to upgrade from 'testing' - trying to overwrite /usr/share/ardour4/locale/en_GB/LC_MESSAGES/gtk2_ardour4.mo
Am Samstag, den 19.09.2015, 09:49 +0200 schrieb Jaromír Mikeš: > add Breaks+Replaces ardour3 in ardour-data package and upload? Yes, please. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Intent to join the pkg-multimedia Team
Hi Anthony, could you please visit the project page on Alioth and click the "Request to Join" link (bottom right)? Then one of us can add you with a single click. https://alioth.debian.org/projects/pkg-multimedia/ Thank you very much, Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: hydrogen-drumkits package
Am Mittwoch, den 16.09.2015, 13:22 +0200 schrieb IOhannes m zmölnig: > CC; and 'Lightning1024' says "Free!" whatever this means) If it doesn't explicitely grant rights, it doesn't qualify. :( - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: DM flag fluidsynth
Am Montag, den 14.09.2015, 14:21 +0200 schrieb Jaromír Mikeš: > I added myself as uploader of fluidsynth ... > Can someone grant me DM flag? > So I can close 2 bug Done, thanks! - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: ardour3 4.1~dfsg-1 MIGRATED to testing
Am Sonntag, den 13.09.2015, 19:58 +0200 schrieb IOhannes m zmölnig: > personally i'm in favour of using it, but i only recently got involved. For those not involved, could you point me to a *single* advantage of this workflow? The only difference I am able to point out is two nearly identical files and a list of backslash-escaped Build-Depends in debian/rules instead of debian/control. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: Fwd: ardour3 4.1~dfsg-1 MIGRATED to testing
Am Freitag, den 11.09.2015, 21:14 +0200 schrieb Jaromír Mikeš: > ifneq (,$(findstring :$(DEB_HOST_ARCH_CPU):,:amd64:)) > CXXFLAGS+=-msse -msse2 -mfpmath=sse > endif Please don't second-guess the compiler, it will choose "the right flags" [tm] on amd64. - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: ardour3 4.1~dfsg-1 MIGRATED to testing
Am Donnerstag, den 10.09.2015, 23:46 +0200 schrieb IOhannes m zmölnig: > the new "ardour" package will be exactly a single "ardour" binary > package (no more -dbg, -i686 and -altivec packages) - should we add > "Provides" for those who need that? Cleanest solution would be to provide transitional packages, or not? - Fabian signature.asc Description: This is a digitally signed message part ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
