Ubuntu
libupnp package

Package version is strongly outdated

Bug #855339 reported by Ivan Frederiks
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libupnp (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Development of libupnp 1.6.6 finished on 2008-04-24 (according to http://pupnp.sourceforge.net/ChangeLog).
Right now version 1.6.13 is available (since 2011-03-15). There are also many intermediate versions.
Is there any reason to ship ubuntu with outdated version of libupnp?

Related branches

lp:debian/libupnp
Hans Joachim Desserud (hjd)
tags: added: upgrade-software-version
Revision history for this message
Nick Leverton (nick-leverton) wrote :

Be careful, upstream has poor ABI stability. If you upgrade the library you'll probably need to rebuild all dependent packages. This is why 1.6.6 is still in Debian, for instance. I intend to do something about this before Wheezy is released, but if you guys want to do something earlier please feel free to go ahead.

Ilya Barygin (randomaction)
Changed in libupnp (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libupnp (Ubuntu):
status: New → Confirmed
Revision history for this message
Nick Leverton (nick-leverton) wrote :

I can confirm that upgrading will involve a library transition from libupnp3 to libupnp6, due to upstream changing the SONAME. This will have a knock-on effect of requiring build-dependency changes from libupnp3-dev to libupnp-dev to the following packages:

amule
djmount
vlc

and rebuilds to the above and also to gmediaserver.

There is also an important API call been removed (UpnpSetVirtualDirCallbacks) which will require reinstating or else working around. I'm working with upstream on restoring this one.

Revision history for this message
StoatWblr (stoatwblr) wrote :

Amule (at least) doesn't play well with 1.6.6 anyway and has to be restarted every tiume the upnp gateway is rebooted.

It's a lot better behaved when locally compiled against 1.6.14

Similar problems exist with upnp-router-control

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libupnp - 1:1.6.17-1.1

---------------
libupnp (1:1.6.17-1.1) unstable; urgency=high

  * Non-maintainer upload.
  * libupnp6-doc Replaces libupnp3-dev (closes: #670894)

 -- Julien Cristau <email address hidden> Tue, 08 May 2012 16:59:14 +0200

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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