bs1770gain_0.4.12-2~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
bs1770gain_0.4.12-2~bpo8+1.dsc
bs1770gain_0.4.12.orig.tar.gz
bs1770gain_0.4.12-2~bpo8+1.debian.tar.xz
bs1770gain_0.4.12-2~bpo8+1_amd64.deb
Greetings,
Your Debian queue daemon (running
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 10 Apr 2017 23:53:34 +0200
Source: bs1770gain
Binary: bs1770gain
Architecture: source amd64
Version: 0.4.12-2~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Debian Multimedia Team
Changed-By: W
Hello all,
I agree that the licenses in fluidsynth are not completely consisted and
Debian is right to make sure that they are.
However, it seems that chorus.c is now under the LGPL license. From
https://sourceforge.net/p/sox/code/ci/master/tree/COPYING:
SoX source code is distributed under
#
# bts-link upstream status pull for source package inkscape
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #858617 (http://bugs.debian.org/858617)
# Bug title: Fails to load certain JPEG files
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
Hi.
This came as a surprise for me. What's worse, it seems like none of the
maintainers are currently active in Fluidsynth, and AFAIK none of us
have time to either rewrite fluid_chorus.c, or track down all
contributors to it since 1998.
What makes things slightly easier for us as upstream i
