A bit more info: I ran the gen-debian-files.sh script, and it produced
the following files:
libunity-scopes-1.0.2.shlibs
libunity-scopes-qt0.2.0.shlibs
Neither of these match the binary package names (libunity-scopes1.0 and
libunity-scopes-qt0.2 respectively), which is probably why they are
being ignored.
This still leaves open the issue of how to manage the minimum version
requirement. At the moment these files produce:
libunity-scopes 1.0 libunity-scopes1.0 (>= 1.0)
libunity-scopes-qt 0.2 libunity-scopes-qt0.2 (>= 0.2)
The first is wrong because there have been ABI additions since version
1.0. The second looks weird because it doesn't look like it refers to
any released version -- that binary package has the same version
numbering as the rest of them, so I'd expect a 1.0.x version as minimum.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update micro version in shlibs file when symbols are added
Status in unity-scopes-api package in Ubuntu:
New
Bug description:
Currently, we are writing only major.minor into the shlibs file. But,
if we add a new symbol to the public API and only increment the micro
version, we really need to write the micro version as well.
Unfortunately, that's a manual process, so we need to remember. With
the next version of abigail, it might be possible to spit out some
big-time warning or some such when new symbols are added to the public
API. At least that would help to remind us.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1548718/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
