Bug#963933: glib2.0: autopkgtext: ld: cannot find -lcryptsetup

[Simon McVittie]

Control: reassign -1 src:glib2.0,src:util-linux
Control: found -1 glib2.0/2.64.3-1
Control: found -1 util-linux/2.35.2-5
Control: tags -1 + moreinfo bullseye sid

On Mon, 29 Jun 2020 at 00:16:49 +0100, Simon McVittie wrote:
> On Sun, 28 Jun 2020 at 22:00:58 +0200, Chris Hofstaedtler wrote:
> > I imagine this might be caused by libcryptsetup-dev not shipping an
> > .a library.
> 
> This means that GLib could previously be successfully statically linked
> (and we had a test to prove it), and now it cannot.
> 
> Do you consider this to be a deliberate change? Is statically linking
> a library that depends on libmount no longer supported?

This is either a regression in libmount (could be statically linked, now
can't) or a wrong assumption in GLib (assumed that statically linking was
supported, but (now?) it isn't). Which one?

Thanks,
    smcv