Comment 30 for bug 274085

Hi,

It would be a pity if ekiga 3.0 will not be in intrepid, as it has a nearly 3 years of development. Also, there has been no important bug since the release, one week ago. For my part, I try to push ekiga/ptlib/opal to debian (my bulds are at http://snapshots.debian.net/snapshots/debian). They will appear in experimental as soon as ptlib source package exists the new queue (http://ftp-master.debian.org/new.html). I plan to maintain them in debian, I would like to help for ubuntu too, but I do not work on ubuntu. Now, for this bug:

The soname are 2.4.1, resp. 3.4.1 (no compatilibty between minor versions, i.e. 2.4.2 will not be compatible to 2.4.1), so the packages have to be renamed libpt2.4.1 and libopal3.4.1.

I don't know about the md5 mismatches, but this will be solved of course upon building.

"cp * build-gtkonly" should have a - before it in the Makefile, in order not to take into account the known error "Cannot copy a directory into itself". There's no harm here. Anyway, gtkonly build is not very tested, upstream proposed not to ship it yet in official packages.

./configure: not found This problem comes from: if you use the SVN sources, you must use autogen.sh, because they do not have a configure file. If you use the release versions, i.e. the tar.gz from ftp.gnome, as given in the previous link, then you must use ./configure (it does not have autogen.sh).

For your dist-upgrade error: I do not understand why ekiga is not correctly installed, is it because the name of the packages?

The last versions of ptlib (2.4.1) and opal (3.4.1) are mandatory for ekiga 3.0.

Greetings,
Eugen