[Bug 576967] Re: new upstream version for Maverick

David Sugar david.sugar at canonical.com
Tue May 25 11:40:54 BST 2010


sippasswd needs to be a setuid binary.  I added $remote_fs to init as
suggested, as yes, it makes sense since /usr may be network mounted, and
I fixed sipwitch-cgi.  I do not think the abi is stable enough where it
can be trusted to match linkage between even different point releases,
and at the moment all linkage is internal to the package and there are
no externally built packages, so I was uncertain what to do with having
a symbol file at this point.  Symbol files is also the one area I am
unclear in packaging.

** Attachment added: "sipwitch_0.8.3-0ubuntu1.debian.tar.gz"
   http://launchpadlibrarian.net/49070251/sipwitch_0.8.3-0ubuntu1.debian.tar.gz

** Patch removed: "sipwitch_0.8.3-0ubuntu1.debian.tar.gz"
   http://launchpadlibrarian.net/48722359/sipwitch_0.8.3-0ubuntu1.debian.tar.gz

-- 
new upstream version for Maverick
https://bugs.launchpad.net/bugs/576967
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “sipwitch” package in Ubuntu: New

Bug description:
Binary package hint: sipwitch

There is a new upstream version built around ucommon 2.1.x and includes includes desktop notification support.  Maverick related work, per UDS/arm-mobile-telephony-stack blueprint will focus on the newer sipwitch 0.8.1 (and later) upstream releases, so it seemed a good time to update Maverick's archive.





More information about the Ubuntu-sponsors mailing list