Bug#319201: kiax in Debian (was Re: Problems rebuilding twinkle)

2006-05-07 Thread George Danchev
On Saturday 06 May 2006 21:44, Santiago Garcia Mantinan wrote:
  We pretty much just need to remove the iLBC and update debian/copyright.
 
  For extra marks we could link to the system provided libspeex/ libgsm 
  portaudio..

 It seems that is already done:

 Version: 0.8.5-2
 Depends: libc6 (= 2.3.6-6), libgcc1 (= 1:4.1.0), libgsm1 (= 1.0.10),
 libportaudio0, libqt3-mt (= 3:3.3.6), libspeex1, libstdc++6 (= 4.1.0),
 libx11-6, libxext6

  George Danchev was talking to upstream to get something along those lines
  in the next upstream release, but I haven't followed anything since.

 Well, George, how did that go? For what I see the new version still carries
 all the stuff we didn't want, including iLBC, so I suppose we should at
 least remove iLBC from our source package.

Upstream said that they distributing the stuff in kiax's lib/ because these 
libraries are not stable enough (sort of true, but we have sonames to handle 
these out) in addition that we can live without lib/ anyway. I sent them a 
patch (ca. November 05) against 0.8.4 to clean the iLBC stuff up. You can 
have it at:

svn co http://svn.openfmi.net/dev/people/danchev/kiax

which was not incorporated in 0.8.5 - reasons unknown for the time being.

 I have tested it and we can remove the hole lib directory and the program
 still compiles, so I guess we could have a source package without this
 directory and that would make half of our problems go away, isn't it?

 What I don't know is what we'd loose by removing this directory, iLBC for
 sure, but that was a wanted effect anyway. But there were some dirs there
 like sox, portmixer, ... that we don't have as a shared lib, so... what
 where those for?

lib/portaudio/LICENSE.txt and 
lib/portmixer/LICENSE.txt sound terribly non-free: 

 * Any person wishing to distribute modifications to the Software is
 * requested to send the modifications to the original developer so that
 * they can be incorporated into the canonical version.

Thus no anonymous modifications are allowed (a-la send me a postcard 
games ;-), so render these bits as DFSG-compliant.

 As for removing iLBC the source is not ready for that and still shows the
 iLBC button and it is enabled, so if you choose it and make a call you get
 in the console:

 ERROR: Codec not supported: 1024
 ERROR: Codec could not be created: 1024

 I'll have to investigate this more, but this poses problems when loading a
 config (iLBC should be changed to some other codec like gsm) and then in
 the preferences window where we should either make iLBC not appear or at
 least make it appear disabled.

 Thoughts on all this?

My impression is that linking against libgsm we already have in Debian should 
be enough. I'm still not sure how to approach upstream that distributing 
(possibly) modified non-free code with their lib/ is pretty dangerous 
solution for them.

P.S. upstream is CC'ed.

-- 
pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#319201: kiax in Debian (was Re: Problems rebuilding twinkle)

2006-05-07 Thread Santiago Garcia Mantinan
 these out) in addition that we can live without lib/ anyway. I sent them a 
 patch (ca. November 05) against 0.8.4 to clean the iLBC stuff up. You can 
 have it at:
 svn co http://svn.openfmi.net/dev/people/danchev/kiax

It doesn't seem to be working right now:

svn co http://svn.openfmi.net/dev/people/danchev/kiax
svn: REPORT request failed on '/dev/!svn/vcc/default'
svn: REPORT of '/dev/!svn/vcc/default': 400 Bad Request
(http://svn.openfmi.net)

But I suppose your patch was more or less like mine (remove all ilbc stuff
and reposition the checkboxes), isn't it?

 which was not incorporated in 0.8.5 - reasons unknown for the time being.

Well, if my patches look ok then we can go with that and I can upload
tonight if nobody complains. ok?

 lib/portaudio/LICENSE.txt and 
 lib/portmixer/LICENSE.txt sound terribly non-free: 

:-) the removal saves us a lot of problems, but... we don't have portmixer
in Debian, so... wasn't it used at all in kiax? if it was used... what was
it used for that we'll be missing now?

 My impression is that linking against libgsm we already have in Debian should 
 be enough. I'm still not sure how to approach upstream that distributing 
 (possibly) modified non-free code with their lib/ is pretty dangerous 
 solution for them.

Well, upstream should be aware of the problems that all that nonfree stuff
has and should probably drop all that from the tarball and instead recommend
the version of those libs that is tested to work well with kiax with a link
to download them from upstream.

Regards...
-- 
Manty/BestiaTester - http://manty.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#319201: kiax in Debian (was Re: Problems rebuilding twinkle)

2006-05-06 Thread Santiago Garcia Mantinan
 We pretty much just need to remove the iLBC and update debian/copyright.
 
 For extra marks we could link to the system provided libspeex/ libgsm  
 portaudio..

It seems that is already done:

Version: 0.8.5-2
Depends: libc6 (= 2.3.6-6), libgcc1 (= 1:4.1.0), libgsm1 (= 1.0.10),
libportaudio0, libqt3-mt (= 3:3.3.6), libspeex1, libstdc++6 (= 4.1.0),
libx11-6, libxext6


 George Danchev was talking to upstream to get something along those lines in 
 the next upstream release, but I haven't followed anything since.

Well, George, how did that go? For what I see the new version still carries
all the stuff we didn't want, including iLBC, so I suppose we should at
least remove iLBC from our source package.

I have tested it and we can remove the hole lib directory and the program
still compiles, so I guess we could have a source package without this
directory and that would make half of our problems go away, isn't it?

What I don't know is what we'd loose by removing this directory, iLBC for
sure, but that was a wanted effect anyway. But there were some dirs there
like sox, portmixer, ... that we don't have as a shared lib, so... what
where those for?

As for removing iLBC the source is not ready for that and still shows the
iLBC button and it is enabled, so if you choose it and make a call you get
in the console:

ERROR: Codec not supported: 1024
ERROR: Codec could not be created: 1024

I'll have to investigate this more, but this poses problems when loading a
config (iLBC should be changed to some other codec like gsm) and then in the
preferences window where we should either make iLBC not appear or at least
make it appear disabled.

Thoughts on all this?

 Welcome back :-)

Thanks!

 I perfer the kiax UI over twinkle, but I prefer SIP over IAX2.
 Go for it, kiax is needed...

:-) Twinkle is getting better, but the original UI is not good, so it is
only being patched :-( But as I don't care about UI's that's not a problem
for me, I like it better than kiax and I think it works better also.

Regards...
-- 
Manty/BestiaTester - http://manty.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]