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 >

Accepted fluidsynth 1.1.10-1 (source amd64) into unstable

<pkg-multimedia-maintainers@lists.alioth.debian.org> Changed-By: Fabian Greffrath <fab...@debian.org> Description: fluidsynth - Real-time MIDI software synthesizer libfluidsynth-dev - Real-time MIDI software synthesizer (development files) libfluidsynth1 - Real-time MIDI software

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 ___

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

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

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. > > > > --

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

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

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

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

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

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

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. ;) -

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

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.

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

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

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

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

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

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

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

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

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!

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

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

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

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

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,

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 =

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

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

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+.

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

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

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

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

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

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

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.

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

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

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

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

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

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

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 >

Bug#842235: handbrake: Crashes with unusable output file on some DVD titles

fmpeg-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? >

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

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? -

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 >

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.

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

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

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

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

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

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

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

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!  -

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

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

Bug#740710: problem with SF3 playback

Vorbis compressed samples Author: Fabian Greffrath <fab...@debian.org> 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 @@ -

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 t

Bug#720603: closed by Sebastian Ramacher <sramac...@debian.org> (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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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:

Bug#798341: [inkscape] impossible to install inkscape

Am Mittwoch, den 09.09.2015, 14:46 +0200 schrieb Marco Righi: > Moreover, a pure Debian testing freezes on a Supermicro board after > the installation at the first reboot. The problem has born during > these day so I think that it is bind to the new Debian release. The > board works fine with the

Bug#798341: [inkscape] impossible to install inkscape

Am Mittwoch, den 09.09.2015, 09:52 +0200 schrieb Marco Righi: > The following packages have unmet dependencies: > inkscape : Depends: libatkmm-1.6-1 (>= 2.22.1) but it is not going to > be installed This is most likely because of the libatkmm-1.6-1 -> libatkmm-1.6-1v5 transition. You better wait

Bug#797838: faac: build with mp4v2

Am Donnerstag, den 03.09.2015, 13:42 +0200 schrieb Christoph Anton Mitterer: > On Thu, 2015-09-03 at 07:11 +0200, Fabian Greffrath wrote: > > this is because libmp4v2 is licensed under the MPL-1.1 whereas faac > > is > > licensed under the GPL. Since both lice

  1   2   3   4   5   6   7   8   9   10   >