Dear Maintainer,

The development package for pango (libpango1.0-dev) does not include static
libraries so it is not possible to link these libraries statically.

Control: forcemerge 994752 994751
Control: severity 994752 wishlist
Control: tags 994752 + wontfix

libpango-1.0.so.0 depends on libgio-2.0.so.0, which depends on
libmount.so.1, which is only available as a shared library, so it
doesn't seem like it is going to be possible to link these libraries
statically regardless of whether we build a .a file or not. It doesn't
seem desirable to make the build take longer to build something that
won't actually work as desired.

More generally, configurations that aren't actively tested typically
don't work, so if I enable static linking in a particular package,
I would want to have at least superficial autopkgtest coverage for it
(see debian/tests/build-static and debian/tests/build in src:glib2.0 for
an example). However, for this particular package, it doesn't seem like
that is going to be possible.

    smcv

I do not see a dependency on libgio when I run ldd on
libpango-1.0.so.0, although it does depend on libglib-2.0.so.0 and
libgobject-2.0.so.0.

Besides, it is possible to compile statically against libpango and
still compile dynamically against some of its dependencies. I am doing
that for my use case and it works just fine.

I will be happy to provide such a test if that is the blocker for landing this.

Right, I double checked and indeed the latest in unstable has that dependency.

Please see the new attached patch.

Thanks,
Alfonso