Hi.

I am curious if you're still maintaining "libnet" in Debian, and if you
saw the bug I reported last year:

  https://bugs.debian.org/949348


I am sending this message to your email directly in case there is some
technical difficulty relaying messages from the debian bug tracking
system...


Thanks!


live well,
  vagrant

On 2021-01-01, Vagrant Cascadian wrote:
> On 2020-01-19, Vagrant Cascadian wrote:
>> I'd suggest simply removing the Makefile, as it is not functional, or
>> alternately, sanitizing with the attached patch to debian/rules.
>
> Patch attached which removes the Makefile instead, which should fix both
> the usrmerge and build path bugs than the previous patches.
>
> I would like to see this land in bullseye if possible, would you
> consider uploading soon, or be amenable to an NMU?
>
>
> live well,
>   vagrant
> From d8e38005ce5c084e33212c399968410661fcb07f Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <[email protected]>
> Date: Fri, 1 Jan 2021 21:32:55 +0000
> Subject: [PATCH] Remove example Makefile. (Closes: #949348, #949346)
>
> The example Makefile embeds build paths that are not likely to be
> present on the end-user system, and possibly binary paths that may be
> different on a usrmerge system, thus requiring the end-user to
> regenerate the file from Makefile.in or Makefile.am anyway.
> ---
>  debian/rules | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/debian/rules b/debian/rules
> index 578a6af..b73692b 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -14,3 +14,6 @@ CFLAGS += -Wno-uninitialized -Wno-unused-but-set-variable
>  DEB_INSTALL_CHANGELOGS_libnet1 := doc/CHANGELOG
>  DEB_CONFIGURE_EXTRA_FLAGS += --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)
>  
> +binary-install/libnet1-doc::
> +     # Remove example Makefile which embeds build paths and binary paths
> +     rm -f 
> $(CURDIR)/debian/libnet1-doc/usr/share/doc/libnet1-doc/html/Makefile
> -- 
> 2.30.0

Attachment: signature.asc
Description: PGP signature

Reply via email to