Fwd: Re: Bug#672656: libucommon-dev: /usr/lib/pkgconfig/ucommon.pc and commoncpp.pc missing from dev pkg

Tue May 15 22:00:08 UTC 2012

We do not normally build commoncpp presently, as we have migrated to
using commoncpp support in ucommon exclusively now for our tree.  There
are some users of commoncpp2 though, so I think it could be worth
resolving this.  It is also something we can continue to maintain and
will be happy to take patches upstream for and test.  Offhand it sounds
like it is just missing an include for <sys/stat.h>, unistd.h,  or
something similar in applog.cpp.  Some of these headers used to be
sloppily included indirectly by other ones, and a lot of that got fixed
in libc awhile ago.

Twinkle has not had a new release in several years, so I am not sure
what you wish to do in regard to future potential bug fixes, etc.  At
least upstream is certainly dead there.  Yes, we have a patch for it so
that it builds against the current ucommon/ccrtp2/zrtp2 tree.  I am not
sure if it is good to continue twinkle, but there are some high profile
users of it to this day, and organizations who do use it actively.  If
you do want to continue it in the archive for Wheezy, this is the patch
we have from Werner Dittermann, at least for the source tree.

I did not know there was an active bug for this already.  I am glad
there is :).

On 05/15/2012 05:10 PM, Mark Purcell wrote:
> David,
>
> We are in the process of transition to the newer versions
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663284
>
> I suspect that in the process we will drop twinkle as obsolete and update 
> sflohone. We have already dropped kde3.x support for twinkle, but would 
> continue if a ccrtp patch could be provided.
>
> I am having some issues with the current libcommoncpp2-dev (1.8.1) failing to 
> build as some defines have been dropped:
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../inc -D_FORTIFY_SOURCE=2 -
> I../src -DCCXX_EXPORT_LIBRARY -D_GNU_SOURCE -I../inc -g -O2 -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -c applog.cpp  
> -fPIC -DPIC -o .libs/applog.o
> applog.cpp: In constructor ‘ost::logger::logger(const char*, bool)’:
> applog.cpp:300:43: error: ‘S_IREAD’ was not declared in this scope
> applog.cpp:300:53: error: ‘S_IWRITE’ was not declared in this scope
> applog.cpp:300:61: error: ‘mkfifo’ was not declared in this scope
> applog.cpp: In member function ‘void ost::logger::logFileName(const char*, 
> bool)’:
> applog.cpp:345:43: error: ‘S_IREAD’ was not declared in this scope
> applog.cpp:345:53: error: ‘S_IWRITE’ was not declared in this scope
> applog.cpp:345:61: error: ‘mkfifo’ was not declared in this scope
> applog.cpp: In constructor ‘ost::AppLog::AppLog(const char*, bool, bool)’:
> applog.cpp:459:46: error: ‘S_IREAD’ was not declared in this scope
> applog.cpp:459:56: error: ‘S_IWRITE’ was not declared in this scope
> applog.cpp:459:64: error: ‘mkfifo’ was not declared in this scope
> applog.cpp: In member function ‘void ost::AppLog::logFileName(const char*, 
> bool, bool)’:
> applog.cpp:565:46: error: ‘S_IREAD’ was not declared in this scope
> applog.cpp:565:56: error: ‘S_IWRITE’ was not declared in this scope
> applog.cpp:565:64: error: ‘mkfifo’ was not declared in this scope
> make[3]: *** [applog.lo] Error 1
>
> Mark
>
>
> On Tue, 15 May 2012 18:37:15 David Sugar wrote:
>> This discussion involves several issues that need to be discussed more
>> broadly with different Debian maintainers, particularly voip.  The
>> original thread is under bug 672656...
>>
>> First, some time ago we migrated to GNU ccrtp 2.x and libzrtpcpp 2.x,
>> and in the process effectively have depreciated GNU Common C++ in favor
>> of GNU uCommon.  While Debian has the lastest ucommon library, and this
>> is now fixed to build the current ccrtp and zrtp releases, Debian is
>> maintaining much older and depreciated releases of ccrtp and zrtp
>> (1.3.x) which are not likely to see active maintenance.
>>
>> Also, Twinkle has not been maintained by their upstream for some years
>> now, but is still in Debian.  Nor did Twinkle ever migrate from qt3.
>> Should this really be carried in Wheezy?  I am simply suggesting that
>> sflphone may be a fine replacement for Twinkle for Wheezy, and is
>> currently actively maintained.
>>
>> We can produce patches for Twinkle (1.4.2...the last release of it) to
>> build against the current ccrtp and zrtp releases if so desired.  We are
>> working on a patch for sflphone which we are in contact with the
>> upstream about as well.  I would like to see if we can get Debian up to
>> date with releases that we do currently maintain and use for all our
>> libraries, and ideally before freeze.
>>
>> -------- Original Message --------
>> Subject: 	Re: Bug#672656: libucommon-dev: /usr/lib/pkgconfig/ucommon.pc
>> and commoncpp.pc missing from dev pkg
>> Date: 	Mon, 14 May 2012 20:12:44 +0200
>> From: 	Werner Dittmann <Werner.Dittmann at t-online.de>
>> To: 	David Sugar <dyfet at gnutelephony.org>
>> CC: 	672656 at bugs.debian.org, Tristan Matthews
>> <tristan.matthews at savoirfairelinux.com>, Jonas Smedegaard <dr at jones.dk>,
>> Simon L'nu <simon.lnu at gmail.com>, Haakon Meland Eriksen
>> <haakon.eriksen at far.no>
>>
>> Am 14.05.2012 18:27, schrieb David Sugar:
>>> This actually touches upon several packages and issues that I think we
>>> should at least try to resolve in debian before wheezy...
>>>
>>> First, ccrtp and zrtp 2.0 or later require ucommon's commoncpp.
>>>
>>> These are easy to build in Debian with ucommon commoncpp.  However,
>>> there are several packages that no doubt use zrtp and ccrtp.  The one I
>>> looked at was sflphone.  I included the debian control file and a patch
>>> I started on for supporting ucommon 5.2/ccrtp 2.x/zrtp 2.x.  It doesn't
>>> yet build correctly though, but is enough for Tristan to look at and see
>>> how this would effect building sflphone...
>>>
>>> I am pretty sure Werner Dittmann has been using twinkle with ccrtp 2.x
>>> for awhile, and I hope could provide a patch for that as needed.
>> Please be aware the twinkle is not longer maintained, Michel de Boer
>> stopped development and maintanance some years ago (2yrs?) . Because of
>> some modifications in ucommon / commoncpp I patched a local copy on my
>> system to compile and run with ucommon/commoncpp, ccrtp 2.x and zrtp 2.x .
>>
>> Thus I would recommend to phase out twinkle because no further development
>> and maintenance, AFAIK it uses older versions of Qt (3.x?), KDE 3.5 etc.
>> Was never enhanced to latest versions of Qt (4.x) and KDE 4.x
>>
>> Regards,
>>
>> Werner
>>
>>> On 05/12/2012 06:03 PM, Jonas Smedegaard wrote:
>>>> On 12-05-12 at 11:03pm, Jonas Smedegaard wrote:
>>>>> On 12-05-12 at 04:06pm, David Sugar wrote:
>> <SNIP --- SNAP>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20120515/8cc39403/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: twinkle-ucommon.diff
Type: text/x-patch
Size: 17810 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20120515/8cc39403/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dyfet.vcf
Type: text/x-vcard
Size: 232 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20120515/8cc39403/attachment-0001.vcf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20120515/8cc39403/attachment-0001.pgp>