We need a stable ekiga-3 ebuild to fix bug 290062.
*** Bug 302514 has been marked as a duplicate of this bug. ***
Hi, this is blocking progress on gcc-4.4, can arches be added soon? Keywords: ekiga-2.0.12: alpha amd64 hppa ia64 ppc ppc64 sparc x86 Keywords: ekiga-3.2.5-r2: Keywords: ekiga-3.2.6: ~alpha ~amd64 ~ia64 ~ppc ~sparc ~x86 Thanks.
Unfortunately, ekiga-3 needs ptlib and newest opal to be stabilized and ptlib stabilization needs pwlib removal which can't be done in quickly. I understand gcc-4.4 needs to be stabilized. What are the available options ?
(In reply to comment #3) > Unfortunately, ekiga-3 needs ptlib and newest opal to be stabilized and ptlib > stabilization needs pwlib removal which can't be done in quickly. > > I understand gcc-4.4 needs to be stabilized. What are the available options ? > The obvious ones Lastrite stable ekiga, and keep it ~arch only. Or test and try to fix compilation issues w/ gcc-4.4 for stable ekiga.
(In reply to comment #3) > Unfortunately, ekiga-3 needs ptlib and newest opal to be stabilized and ptlib > stabilization needs pwlib removal which can't be done in quickly. I don't understand the need to make it done atomically. If the deps are correct, what is the hold up? Anyway, progress on gcc-4.4 will not be held back for ekiga (it is not a critical package), so I suggest some action :)
(In reply to comment #5) > (In reply to comment #3) > > Unfortunately, ekiga-3 needs ptlib and newest opal to be stabilized and ptlib > > stabilization needs pwlib removal which can't be done in quickly. > > I don't understand the need to make it done atomically. If the deps are > correct, what is the hold up? > Some deps (pwlib and opal) are used by some stable packages and newest version (ptlib for pwlib) are now backward-compatible. So, moving ptlib and opal-3 to stable is not going to be easy and we need them to move ekiga-3 to stable. I will look about gcc-4.4 issues in ekiga-2 and see if I can fix them otherwise, ekiga-2 is going to be removed.
Can't you just make a stable bug for the whole thing all at once ? And lets get rid of ekiga 2.
Olivier, as I said, ptlib and pwlib can't live together and some packages depends on pwlib and will not work with ptlib. We need to fix that before stabilizing ekiga-3. I think fixing the compilation issues for ekiga-2 will be much more easier... or remove ekiga-2 from the tree.
(In reply to comment #8) Please do *not* remove ekiga-2.0.12! Until now - even with version 3.2.7 - there is *no* adequate substitute for ekiga version 2.0.12; ekiga-2* passes echo tests (sip:500@ekiga.net and sip:520@ekiga.net); ekiga-3* *only* passes first test: no response call to sip:520@ekiga.net (behind NAT router) and therefore no 'calling in' is possible! Stable ekiga-, pwlib- and opal-version were built without additional USE flags. Could someone provide a working USE flag configuration for last ekiga version with identical NAT behaviour as the ekiga-2.0.12/opal-2.2.11/pwlib-1.10.10-r2 package? > Olivier, as I said, ptlib and pwlib can't live together and some packages > depends on pwlib and will not work with ptlib. We need to fix that before > stabilizing ekiga-3. I think fixing the compilation issues for ekiga-2 will be > much more easier... or remove ekiga-2 from the tree.
(In reply to comment #9) > Until now - even with version 3.2.7 - there is *no* adequate substitute for > ekiga version 2.0.12; ekiga-2* passes echo tests (sip:500@ekiga.net and > sip:520@ekiga.net); ekiga-3* *only* passes first test: no response call to > sip:520@ekiga.net (behind NAT router) and therefore no 'calling in' is > possible! Plese open new bug report. Both tests work here with USE="dbus debug eds gconf gnome gstreamer ldap libnotify mmx nls shm xv -aqua -avahi -doc -h323 -kde -kdeenablefinal -kontact -static -v4l -xcap".
*** Bug 361395 has been marked as a duplicate of this bug. ***
Finally done in bug 397617 *** This bug has been marked as a duplicate of bug 397617 ***
