** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update micro version in shlibs file when sy
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update micro version in shlibs file when sym
** Branch linked: lp:~michihenning/unity-scopes-api/shlib-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update micro version in shlibs file when symbols are added
To mana
** Changed in: unity-scopes-api (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1548718
Title:
Need to update micro version in shlibs file when symbols are a
Looking at this, I think the easiest way would be to generate the final
digit in the dependency clause from a separate file, say,
LAST_ABI_ADDITION_MICRO.
So, if we release 1.0.6, but there were no ABI additions from 1.0.5 to
1.0.6, we would have VERSION containing "1.0.6", and
LAST_ABI_ADDITION_M
The version numbers in at the end of the shlibs lines refer to package
version numbers. Every binary package produced from the source package
will share the same version number.
Given that unity-scopes-api 0.2 seems to date from 2014, which is long
before the Qt library was written, it certainly
Ouch! :-(
Thank you for the detective work!
I'll fix the script to generate the the correct file names. To get the
correct micro version in there, we'll have to use a manual process, I'm
afraid, at least until it somehow becomes possible to have abigail help
with detecting symbol additions to the
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
I'm not seeing it in the final packages though:
$ apt-cache policy libunity-scopes1.0
libunity-scopes1.0:
Installed: 1.0.3+16.04.20160209-0ubuntu1
Candidate: 1.0.3+16.04.20160209-0ubuntu1
Version table:
*** 1.0.3+16.04.20160209-0ubuntu1 500
500 http://au.
The version assertion should be there. In the shlibs.in file, we have
libunity-scopes @UNITY_SCOPES_SOVERSION@ libunity-
scopes@UNITY_SCOPES_SOVERSION@ (>= @UNITY_SCOPES_MAJOR_MINOR@)
But the micro version is missing here.
--
You received this bug notification because you are a member of Ubuntu
The shlibs file should read something like:
libunity-scopes 1.0 libunity-scopes1.0 (>= 1.0.x)
Where 1.0.x is the last release where new ABI was introduced (currently
it omits the version assertion on the end).
For mediascanner2, I am not generating the shlibs file from anything,
but instead
11 matches
Mail list logo
