Dear Chris Bagwell,
Could you check your messages at cnpbagwell.com about a bug that were
sent from my address?
Thank you.
smime.p7s
Description: S/MIME cryptographic signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lis
El dl 10 de 04 de 2017 a les 23:06 +0200, Peter Hanappe va escriure:
> However, it seems that chorus.c is now under the LGPL license. From
> https://sourceforge.net/p/sox/code/ci/master/tree/COPYING:
As I understand, fluidsynth_chorus.c was imported from SoX rather than
the original project by Jue
El dl 10 de 04 de 2017 a les 09:24 +0200, David Henningsson va escriure:
> What makes things slightly easier for us as upstream is that FluidSynth
> is released under LGPL rather than GPL. LGPL allows linking to custom
> licenses.
This is not the case because fluid_chorus.c is part of the librar
Dear Chris Bagwell,
In 1999, you imported src/chorus.c to SoX on SourceForge.[6] File is
copyrighted by Juergen Mueller and sundry contributors. Could you tell
us where we could find the original project or how to contact Juergen
Mueller?
Thank you.
--
[6]
https://sourceforge.net/p/sox/code/ci/
Regarding SoX and Debian bug #92969, the copyright handling in wav.c is
dubious.[5] Assuming this modification is allowed, wav.c changes the
notice
XAnim Copyright (C) 1990-1997 by Mark Podlipec.
[...]
This software may be freely copied, modified and redistributed
w
El dv 07 de 04 de 2017 a les 19:13 +0100, James Cowgill va escriure:
> FYI the license in question is the SoX license which has been in Debian
> and basically all distributions for 20 years (as part of SoX)...
So SoX and derivatives are affected too. The problem was not
detected.[3]
> The SoX pro
Source: fluidsynth
Version: 1.1.6-4
Severity: wishlist
fluid_chorus.c is under a custom license, granting the following:
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 c
compilation with Clang on C++11 mode.
Author: Javier Serrano Polo
Index: libgig-3.3.0/src/gig.h
===
--- libgig-3.3.0.orig/src/gig.h 2015-08-04 23:22:14.0 +
+++ libgig-3.3.0/src/gig.h 2017-01-04 17:52:46.0 +
@@ -431,11
Package: libjack-jackd2-0
Version: 1.9.10+20150825git1ed50c92~dfsg-2
Severity: wishlist
Control: clone -1 -2
Control: reassign -2 libsoundio1
Control: retitle -2 libsoundio1: Missing hard dependency on libjack-jackd2-0
Control: found -2 1.0.2-1
libsoundio1 depends on jack_set_port_rename_callback,
Control: reassing -1 vocoder-ladspa
Control: affects -1 swh-plugins
I will ask to upload a new version of lmms to remove vocoder-ladspa.
smime.p7s
Description: S/MIME cryptographic signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-ma
El dt 31 de 05 de 2016 a les 14:09 +, Jaromír Mikeš va escriure:
> + * Fix multi-arch path.
Will the plug-ins be installed under /usr/lib/*/ladspa? I would be in
favor, but AFAIK this would be the first Debian package to ship LADSPA
plug-ins under a multiarch folder instead of /usr/lib/ladspa
El dj 19 de 05 de 2016 a les 19:41 +0200, Jaromír Mikeš va escriure:
> Yes, that would be definitely possible, but I would to to know where
> next releases will be published to tune watch file accordingly.
Nine years have passed without a release. I think a watch file is
obsolete. I would rely on
Package: swh-plugins
Version: 0.4.15+1-8
Severity: wishlist
The upstream project is maintained at https://github.com/swh/ladspa . It
includes a vocoder plug-in that is shipped with the lmms package. To
reuse this plug-in, lmms could put it under /usr/lib/ladspa, but that
would conflict with a new
Package: zynaddsubfx
Version: 2.5.2-2
Severity: wishlist
According to
https://github.com/LMMS/lmms/issues/2752#issuecomment-217043740 , it
looks like the license should be GPL-2+ despite what individual files
say.
smime.p7s
Description: S/MIME cryptographic signature
14 matches
Mail list logo
