Thank you.

On Wed, 26 Jun 2024, 16:50 Aurelien Jarno, <aure...@debian.org> wrote:

> Dear maintainer,
>
> On 2024-03-01 16:55, Aurelien Jarno wrote:
> > Source: caml-crush
> > Version: 1.0.12-1.1
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the
> past)
> >
> > 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 caml-crush to
> > FTBFS in sid with:
> >
> > | checking for gawk... no
> > | checking for mawk... mawk
> > | checking for camlidl... yes
> > | checking for spatch... yes
> > | Detected coccinelle version 1.1.1
> > | configure: Using default C based client and RPC
> > | checking for getnetname in -ltirpc... no
> > | configure: Using the glibc RPC implementation
> > | checking for rpc/rpc.h... no
> > | configure: error: Could not find C RPC headers.
> > |         cd build-SERVER && 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 caml-crush, 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.
>
> I have just done a NMU to fix this issue. Please find the debdiff
> attached.
>
> Regards
> Aurelien
>
> --
> Aurelien Jarno                          GPG: 4096R/1DDD8C9B
> aurel...@aurel32.net                     http://aurel32.net
>

Reply via email to