Source: liblxi
Version: 1.20-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 liblxi to FTBFS
in sid with:

| Found pkg-config: /usr/bin/pkg-config (1.8.1)
| Run-time dependency avahi-client found: YES 0.8
| Run-time dependency libxml-2.0 found: YES 2.9.14
| Run-time dependency threads found: YES
| Has header "avahi-client/client.h" : YES
| Did not find CMake 'cmake'
| Found CMake: NO
| Run-time dependency libtirpc found: NO (tried pkgconfig)
|
| ../src/meson.build:30:14: ERROR: Dependency "libtirpc" not found, tried pkgconfig
|
| A full log can be found at /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
| cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt

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.

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 Fri, 01 Mar 2024 18:34:06 +0000
with message-id <E1rg7hu-0002HE-Ah@fasolo.debian.org>
and subject line Bug#1065181: fixed in liblxi 1.20-2
has caused the Debian Bug report #1065181,
regarding liblxi: missing build-dep on libtirpc-dev
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.)


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

Received: (at submit) by bugs.debian.org; 1 Mar 2024 15:41:59 +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=-109.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,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, 106; 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:311, 0.000-+--H*RT:108
Return-path: <aurel32@debian.org>
Received: from stravinsky.deb