Bug#664606: additional information

2012-03-19 Thread Simon Josefsson
Mark Purcell writes: > On Mon, 19 Mar 2012 21:32:09 Simon Josefsson wrote: >> I noticed this site: >> >> http://www.webrtc.org/ilbc-freeware > > Simon, > > In 2006 you filed the same bug report: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393402 > > Since then we have _not_ shipped ilbc i

Bug#664606: additional information

2012-03-19 Thread Faidon Liambotis
On 03/19/12 13:28, Simon Josefsson wrote: > Some even further information, as I seen that others have identified the > problem, see for example: > > http://yate.null.ro/mantis/view.php?id=295 > > There exists a libilbc library with a clear license here: > > https://github.com/dekkers/libilbc >

Bug#664606: additional information

2012-03-19 Thread Simon Josefsson
Faidon Liambotis writes: > On 03/19/12 13:28, Simon Josefsson wrote: >> Some even further information, as I seen that others have identified the >> problem, see for example: >> >> http://yate.null.ro/mantis/view.php?id=295 >> >> There exists a libilbc library with a clear license here: >> >>

Bug#664606: additional information

2012-03-19 Thread Mark Purcell
On Mon, 19 Mar 2012 21:32:09 Simon Josefsson wrote: > I noticed this site: > > http://www.webrtc.org/ilbc-freeware Simon, In 2006 you filed the same bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393402 Since then we have _not_ shipped ilbc in Debian, until this year when Google

Bug#664606: additional information

2012-03-19 Thread Simon Josefsson
Some even further information, as I seen that others have identified the problem, see for example: http://yate.null.ro/mantis/view.php?id=295 There exists a libilbc library with a clear license here: https://github.com/dekkers/libilbc It is labeled as a "drop-in replacement for the non-free co

Bug#664606: additional information

2012-03-19 Thread Simon Josefsson
I noticed this site: http://www.webrtc.org/ilbc-freeware However I cannot find any license statement that applies to the iLBC reference implementation. Maybe you could use the iLBC implementation from WebRTC instead? It seems quite heavily modified from the reference implementation though. It