On Thu, Mar 24, 2016 at 07:52:56PM +0100, Christian Hofstaedtler wrote:
> * Christian Hofstaedtler <z...@debian.org> [160324 19:08]:
> > your package implicitly depends ob libruby2.2, by means of shipping
> > an .so which uses symbols from libruby2.2. libruby2.2 is about to go
> > away from testing.
>
> This might not be completely true; but even if the .so doesn't use
> any of libruby's symbols, it's still built against libruby2.2 and
> ends up in the extension directory of libruby2.2.
>
> As such it really should have a Depends: libruby2.2.
>
> Easiest way of getting that dep right (now and for future versions)
> may be to actually link with libruby.
>
> BTW, there's a pkg-config file if you don't want to go via
> RbConfig::CONFIG; if you do, it appears the relevant snippet is:
> print RbConfig::CONFIG['DLDFLAGS'] + ' ' +
> RbConfig::CONFIG['LIBRUBYARG_SHARED'] + ' ' + RbConfig::CONFIG['LIBS']
Thanks very much for this additional detail - I had had a brief look and
failed to grasp what was going awry with the automatic dependency. I
think I now actually understand what's going on.
I'll sort out a fix soon, but if this is/becomes the final blocker for
the transition feel free to NMU something appropriate to get us past
that (I think just a binNMU would do the trick as it should get rebuilt
against ruby2.3).
Cheers,
Olly
