On Sun, Apr 07, 2024 at 08:22:37PM +0100, Peter Michael Green wrote:
> The following lines in the build log look like a likely culprit.
>
> > # The module(s) are linked against libruby2.x but use none of its
> > # symbols, so there's no dependency generated. That's unhelpful for
> > # users and for transitions (https://bugs.debian.org/816775) so
> > # generate a suitable dependency.
> > #
> > # If RUBY_VERSIONS is 2.1 2.2 2.3, Depends: libruby2.3|libruby2.1
> > |libruby2.2
> > echo "ruby:Depends=libruby3.1" \
> > >> debian/ruby-xapian.substvars
Yes, thanks for identifying that.
We can't rely on the automated machinery (see ticket linked above
if you want the gory details) but the ruby team (quite reasonably)
wanted a dependency and suggested essentially what we do now.
We could just hardcode t64 here, but probably better to try to extract
the actual library from the matching ruby version's dependencies so we
don't have to do this for future suffix changes (the next librubyX.Y
to be packaged won't need it).
This works, but maybe there's a better way:
dpkg -s ruby3.1|sed -n 's/^Depends:.*\(libruby3.1[a-z0-9]*\).*/\1/p;d'
I'll try to get a fix uploaded in the next day or two.
Cheers,
Olly
