On one hand: Yes it is the same underlying problem, various packages are already fixed - but some are not. Usually if the upstream code is ready all you need is to add libtirpc-dev to the build deps, if the upstream code isn't ready then some changes are needed.
But the bug here was meant to just track glusterfs to adopt this. And for this https://launchpad.net/ubuntu/+source/glusterfs/9.0-1 is actually fixed by now, so we can mark this bug fix-released. The problem is that in the past often xdr_* got resolved through glibc even if libtirpc was around (yes it is bad, but I'm just stating what I've found back then). Glibc now dropping these symbols (in groovy already) now exposes those cases. Eventually all those packages in the following list will have adopted one or the other way: $ reverse-depends --release hirsute --build-depends libtirpc-dev Reverse-Build-Depends * alberta * autofs * ganglia * ganglia-modules-linux * glusterfs * gnudatalanguage * kio-extras * libace-perl * libassa * libdap * libnsl * libnss-nis * libvirt * netatalk * nfs-utils * nfswatch * openbsd-inetd * quota * rpcbind * slapi-nis * xymon * yp-tools * ypbind-mt * ypserv --- On the other hand: Your example indeed fails, and TBH I don't see the problem why it would fail :-/ But This bug wasn't meant for the general issue (that is just a decision by glibc to move to that, and delayed by ubuntu carrying the comat symbols up until 2.32). This was just meant to track the glusterfs case of it. Never the less you made me wondering ... ** Changed in: glusterfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905360 Title: FTBFS in Hirsute due to glibc2.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1905360/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
