Packages in PPA doesn't generate correct shlibs

Bug #689272 reported by Julien Lavergne
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg
Invalid
Undecided
Unassigned

Bug Description

When you upload a new library to the PPA, this new version number is not used when you build new package in this package.

Example :
In this PPA : https://edge.launchpad.net/~synapse-core/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=lucid
There is a new version of libzeitgeist (0.2.14, and the version in main Ubuntu repositories is 0.2.8.
When you rebuild a package, using ${shlibs:Depends} in debian/control, it should generate a depend libzeitgeist-1.0-0 (>= 0.2.14), but the depend generated is just libzeitgeist-1.0-0 (without the version).

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Hi Julien,

Requirements for newer versions of a library in shlibs will only be added if that library's SONAME has been changed or if it is using symbol versioning and your package uses a symbol that was only recently introduced. As far as I can tell this is correct behaviour.

Cheers,

Jelmer

affects: soyuz → dpkg
Changed in dpkg:
status: New → Invalid
Revision history for this message
Julien Lavergne (gilir) wrote :

Hi Jelmer

No, the behavior is correct in the main Ubuntu repository, only the behavior on the PPA is incorrect.

If you build package foo with libbar1 (0.2), foo will depends on libbar1 (= 0.2) using ${shlibs:Depends}
If you build the same package foo with libbar1 (0.4) in your PPA (0.2 still available in Ubuntu), foo will depends on libbar1 without any version.

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.