new upstream version for Maverick

Bug #576967 reported by David Sugar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sipwitch (Ubuntu)
Fix Released
Undecided
Unassigned

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.

Related branches

Changed in sipwitch (Ubuntu):
assignee: nobody → David Sugar (dyfet)
Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

sipwitch diff for 0.8.1 package

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

debdiff from 0.7.4 (lucid) to 0.8.1 (for maverick)

Changed in sipwitch (Ubuntu):
assignee: David Sugar (dyfet) → nobody
Revision history for this message
Benjamin Drung (bdrung) wrote :

I propose these changes (patch attached).
 * Switch to dpkg-source 3.0 (quilt) format.
 * Wrap and sort Build-Depends and Depends.
 * debian/rules: Remove get-orig-source; uscan does the same job.
 * Some cosmetic changes.

A new upstream release is available. Please package that, include my proposed changes, and resubscribe once ucommon 2.1.3 passed the NEW queue.

Do you plan to bring this package to Debian?

Revision history for this message
Benjamin Drung (bdrung) wrote :

...and resubscribe ubuntu-sponsors...

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

I like this very much, and in fact I will have to look at how I am packaging other things now as well. I will take this in with maybe a few small tweaks, and propagate something similar to things like ucommon and ccscript packaging. Actually there will be a newer upstream release of sipwitch (0.8.3) later this week which has changes relevant to Ubuntu (0.8.2 did not have any change other than changing the dependency in the configure script itself to test for ucommon 2.1.3, and this of course was already addressed in packaging, so I felt it unnecessary to do an update for 0.8.2).

We have had no success getting these packages accepted in Debian in the past even when existing Debian package maintainers came forward offering to package it. If it could be done, it might simplify life of course.

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

Debdiff for new 0.8.3 release with proposed changes merged

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

Packaging for 0.8.3 by itself

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

Benjamin, I have merged your changes with upstream changes for the newer 0.8.3 release, which includes placing network config change scripts, and re-subscribing sponsors as you suggest.

Revision history for this message
Benjamin Drung (bdrung) wrote :

There are some lintian errors and warnings that should be addressed:

* description in package sipwitch-plugin-libnotify: dbus -> D-Bus
* sipwitch-cgi must depend on ${shlibs:Depends}
* I: sipwitch source: binary-control-field-duplicates-source field "section" in package sipwitch-cgi
* E: sipwitch: init.d-script-missing-dependency-on-remote_fs /etc/init.d/sipwitch: required-start
* E: sipwitch: init.d-script-missing-dependency-on-remote_fs /etc/init.d/sipwitch: required-stop
* W: sipwitch: setuid-binary usr/bin/sippasswd 4755 root/root

You probably want to add a symbols file (I: libsipwitch0: no-symbols-control-file usr/lib/libsipwitch.so.0.0.40)

This typo found by lintian should be forwarded upstream:
I: sipwitch: spelling-error-in-manpage usr/share/man/man1/sipwitch.1.gz deamon daemon

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

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.

Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

Revised debdiff

Revision history for this message
Benjamin Drung (bdrung) wrote :

uploaded

Changed in sipwitch (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sipwitch - 0.8.3-0ubuntu1

---------------
sipwitch (0.8.3-0ubuntu1) maverick; urgency=low

  * New upstream version (LP: #576967):
    - Requires ucommon 2.1.3 or later
    - Introduction of desktop notification plugin subpackage
    - Reloads configuration when ethernet interface state changes
    - Packaging cleanup
 -- David Sugar <email address hidden> Tue, 18 May 2010 15:00:23 -0400

Changed in sipwitch (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.