Am Sa., 10. Nov. 2018 um 15:25 Uhr schrieb Julien Cristau <jcris...@debian.org>:
>
> On Wed, Oct 24, 2018 at 12:50:28 +0200, Matthias Klumpp wrote:
>
> > Am Mi., 24. Okt. 2018 um 12:45 Uhr schrieb Andrey Rahmatullin 
> > <w...@debian.org>:
> > >
> > > Package: appstream-generator
> > > Version: 0.7.4-1
> > > Severity: grave
> > >
> > > I've just installed appstream-generator and ran it:
> > >
> > > $ appstream-generator
> > > appstream-generator: symbol lookup error: appstream-generator: undefined
> > > symbol: _D7gobject7ObjectGQi5dorefMFZCQBcQxQz
> > >
> > > So it's either underlinked or some dependency dropped that symbol without
> > > bumping the soname, in which case please reassign the bug accordingly.
> >
> > This is because the package wasn't properly rebuilt with the latest
> > LDC release in the last LDC transition.
> > A simple package rebuild should fix this issue.
> >
> > There is another LDC transition pending, which starts when LDC clears
> > NEW, I'll merge this issue with the transition bug then.
> >
> Package dependencies should prevent silent breakage like this, though?

If a dependency gets rebuilt, but the reverse dependency didn't (like
with libglibd and appstream-generator here), this issue can happen.
Because of that, the new LDC releases have their newer standard
library package conflict with the previous version now, so people
won't install an uninstallable configuration.
Since the first rebuild here failed though due to an unrelated bug in
Meson, LDC got more releases in the meantime, dropping this Conflicts
safeguard, which caused this issue.

Not great, but dealing with unstable ABIs unfortunately leads to these
issues (unless you go the Go route and recompile everything, or go the
Haskell route and make a more complicated system of dependencies).
The good news is that this issue shouldn't happen again (or would be
rather rare, as it requires a package to FTBFS due to a dependency
that is unrelated to the LDC ABI transition).

Cheers,
Matthias
-- 
I welcome VSRE emails. See http://vsre.info/

Reply via email to