在 2026/1/29 15:04, Syed Shahrukh 写道:
Hi,
Thank you for taking time to have a look.
I took an empty symbol file, something similar to version 4.11 which replaced
all the existing symbols with a new version.
Since there is already an existing symbols file, you need not initialize it
by yourself. Instead you should add new symbols that appeared in the new
library version
into it.
Alternatively, I could have put only the new symbols that were introduced in
version 4.13 using the diff in build log.
This procedure was exactly described in
https://www.debian.org/doc/manuals/maint-guide/advanced.en.html .
Please suggest the way forward, obviously i don't have a firm understanding on
how debian generates or uses symbols file.
You can read more into the symbols system using my given URL, but the basic
idea is just to
use the file to track which (public) symbols are exposed to the library
invoker, and of which
packaged shared library version did these symbols appear. As such, the file
shall exist and be
updated across different packaged library versions, and *get reset* when SONAME
is bumped
(since broken API/ABI would reset the symbol's minimum compatible library
version).
We are not bumping SONAME now, so there is not resetting, just adding new
symbols.
Please do so and let me know when you are ready. Please ensure that the package
buildlog
does not have warning outputs when dh_shlibdeps gets invoked.
Thanks,
Boyuan
On Fri, Jan 30, 2026 at 12:47 AM Boyuan Yang <[email protected]
<mailto:[email protected]>> wrote:
Hi,
在 2026/1/29 13:04, Syed Shahrukh Hussain 写道:
> Package uploaded on mentors.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126618
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126618>
Can you explain what have you done with the debian/libsqlcipher2.symbols
file?
In case you don't know clearly, please refer to Section A.2 in
https://www.debian.org/doc/manuals/maint-guide/advanced.en.html
<https://www.debian.org/doc/manuals/maint-guide/advanced.en.html> on the
*.symbols file usage.
Thanks,
Boyuan
