[Pkg-crosswire-devel] Bug#796711: Bug#796711: sword: library transition is needed with GCC 5 as default

[Simon McVittie]

On Mon, 24 Aug 2015 at 11:24:19 +0100, Daniel Glassey wrote:
> A new version of the library (1.7.5) is imminent and will require a
> transition anyway. So we'll start planning the transition to libsword12.

Please do the v5 transition anyway; the wider libstdc++ transition has
eaten a month so far, and we would really like it to be over. The
release team are more likely to kick packages out of testing than waiting
for a new SONAME. As I think I mentioned at the Debian-UK BBQ,
there are ~ 300 transitions involving ~ 3000 packages at the moment,
so the people dealing with them would really prefer to see conservative,
minimal-risk changes.

If you had 1.7.5 already staged in experimental, it had already built
on all architectures, and you had test-built its rdeps successfully,
then going directly to libsword12 might be OK; but that doesn't
appear to be the case. The libsword12 transition can still happen in the
usual way (with a transition slot and so on) after the libstdc++ horror
has finished; there aren't many packages involved, so it should be an
easy one under normal circumstances.

Vaguely related to this, a ftp team member noted that there are open
RM bugs for bibledit-gtk and xiphos, which seem to be in the same
general area (bible study), and might get processed soon. If these
are of interest to you, please reply to the removal bugs and either
say "yes, this should be removed from unstable", or say what the plan
is for fixing the issues that led to the bug.

    S