[pkg-crosswire-devel] transition didn't happen for 1.8.1

[Teus Benschop]

Thank you Daniel for the update on this matter.

A DD can upload to the NEW queue, but as a DM I was unable to do so.

To work around that, I had taken the following steps:

1. Update libsword to 1.8.1 while keeping the binary the same.
2. Rebuild BibleTime to link against that.

Then the plan was to wait till the updated Xiphos had entered testing, and
then to do a rebuild against libsword 1.8.1 also.

This night Xiphos had entered testing, so I was about to issue a rebuild,
so it would link to libsword 1.8.1.

I am unable to upload to the NEW queue yet, and any help to get the new
package libsword.1.8.1 uploaded is greatly appreciated!

Blessings,

Teus.

On Fri, 2 Nov 2018 at 07:02 Daniel Glassey <wdg at debian.org> wrote:

> Hi,
>
> It looks as though there was no transition for 1.8.1[1]. The library has
> changed from libsword.so.11v5 to libsword-1.8.1.so
>
> This means that currently no application using sword e.g. bibletime, xiphos
> will be able to run in unstable or testing until it is recompiled against
> the new libsword-dev.
>
> This is supposed to happen in a transition so that the new library and all
> it's dependencies go into unstable from experimental at the same time.
>
> The way it was before the lib so version would only change with an ABI
> incompatibility so if the new sword version didn't cause one then the
> version would stay the same. If something changes, the so version changes
> and the libsword<version> package name changes and the package is NEW.
>
> The lib name changed so there should be a new libsword1.8.1 package which
> will have to go through NEW. After that every new version of sword will
> require a package to go through NEW because the lib so version changes
> every time.
>
> See https://www.debian.org/doc/debian-policy/ch-sharedlibs.html esp 8.1
> Run-time shared libraries
>
> Basically the next upload needs to have a new library package renamed from
> libsword11v5 to libsword1.8.1 and it will have to go through NEW. That must
> go into experimental not unstable.
>
> Don't worry, we can fix this :)
>
> Regards,
> Daniel
>
> [1] it was probably needed with the first package version using autotools
> but I don't know which one that was.
> _______________________________________________
> pkg-crosswire-devel mailing list
> pkg-crosswire-devel at alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-crosswire-devel
>
-- 
Teus Benschop
teusjannette at gmail.com
0318 712046