Source: libguestfs
Version: 1:1.52.0-2.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past) User: debian-glibc@lists.debian.org
Usertags: libtirpc-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes libguestfs to
FTBFS in sid with:

| checking for CFLocaleCopyPreferredLanguages... no
| checking for GNU gettext in libc... yes
| checking whether to use NLS... yes
| checking where the gettext function comes from... libc
| checking if the user specified a default backend... direct
| checking for dlopen in -ldl... yes
| checking for dlfcn.h... (cached) yes
| checking for libtirpc... no
| checking for rpc/xdr.h... no
| configure: error: XDR header files are required
| cd debian/build-1 && tail -v -n \+0 config.log

This could be fixed by adding an explicit Build-Depends on libtirpc-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

I also noticed that libguestfs, uses rpcgen, provided by the
rpcsvc-proto during the build process. It is currently a dependency of
the libc6-dev package for the same reason as libnsl-dev, and will be
removed at some point. Therefore please also add an explicit
Build-Depends on rpcsvc-proto.

Regards
Aurelien

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Tue, 12 Mar 2024 00:30:54 +0000
with message-id <E1rjq2g-00GwkX-9D@fasolo.debian.org>
and subject line Bug#1065189: fixed in libguestfs 1:1.52.0-3
has caused the Debian Bug report #1065189,
regarding libguestfs: missing build-dep on libtirpc-dev (and also rpcsvc-proto) to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


--
1065189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065189
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 1 Mar 2024 16:06:12 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-108.3 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY,
USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,WORD_WITHOUT_VOWELS,
XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 150; neutral, 113; spammy,
0. spammytokens:
hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
0.000-+--H*RT:108, 0.000-+--H*RT:311
Return-path: <aurel32@debian.org>
Received