2017-09-29 13:38 GMT+02:00 Michael Biebl <bi...@debian.org>:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: binnmu
>
> nmu gtk-d_3.6.5-2 . amd64 . unstable . -m "Rebuild against libphobos2-ldc74"
>
> tilix was built with the latest version of ldc and as a result is linked
> against libphobos2-ldc74. It also links against libvted-3-0, which was
> not compiled with the newest ldc version yet, so still links against
> libphobos2-ldc72. Apparently mixing libraries this way is not supported
> and as a consequence tilix fails to start, see #876479:
>
> $ tilix
> Fatal Error while loading '/usr/lib/x86_64-linux-gnu/libdruntime-ldc.so.72':
> The module 'core.atomic' is already defined in
> '/usr/lib/x86_64-linux-gnu/libdruntime-ldc.so.74'.
>
> Rebuilding gtk-d (which provides libvted-3-0) against libphobos2-ldc74
> seems to fix the error.
>
> CCed the D developers. It would be nice if such situations could be
> avoided in the future. Maybe you have some ideas how to achieve that.
>
> The situation is a mess:
> https://packages.debian.org/sid/tilix
> https://packages.debian.org/sid/libvted-3-0
>
> There is no consistency wrt to which version of libphobos2-ldc the
> binaries are linked against.
Agreed. Ideally we'd need to coordinate binNMUs on new ABI versions
better, so thinks are rebuilt in order, and not randomly. Also, LDC
needs to migrate to testing faster (currently blocked on rewriting the
d/copyright file).
Maybe we can also add a breaks relationship to the newer libphobos
versions, so mixing runtimes in software is impossible.
Thank you for filing the binNMU request!
Cheers,
Matthias
--
I welcome VSRE emails. See http://vsre.info/
