Your message dated Fri, 08 Mar 2019 00:34:31 +0000
with message-id <e1h23t5-0003ht...@fasolo.debian.org>
and subject line Bug#923970: fixed in knot-resolver 3.2.1-2
has caused the Debian Bug report #923970,
regarding libkres-dev: cannot build anything meaningful against libkres-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 ow...@bugs.debian.org
immediately.)


-- 
923970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkres-dev
Version: 3.2.1-1
Severity: grave
Justification: renders package unusable

A little over half of the header files shipped in libkres-dev contain
an #include line that refers to other files in "lib/…", for example:

#include "lib/defines.h"

You can see these with:

    grep -n 'include "lib' /usr/include/libkres/*.h

This breaks anything that tries to #include these files directly, with
errors like this:

    gcc -o kres-test kres-test.c -lkres
    In file included from kres-test.c:1:
    /usr/include/libkres/module.h:23:10: fatal error: lib/defines.h: No such 
file or directory
     #include "lib/defines.h"
              ^~~~~~~~~~~~~~~
    compilation terminated.
    make: *** [Makefile:4: kres-test] Error 1


Of the files that don't include such a broken #include, they are
either not particularly useful on their own
(e.g. /usr/include/libkres/defines.h) or they refer to functions not
actually exported by libkres.so
(e.g. /usr/include/libkres/signature.h, which exposes a C header for
kr_authenticate_referral, which is not in libkres.so).

So libkres-dev doesn't really work at all right now, and the
distributed shared object libkres.so.* itself doesn't seem to be
useful for anything other than knot-resolver.

Upstream is planning to eventually produce some sort of functional
library, but they're not clear on what it looks like:

https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/770

So i think my earlier attempt at splitting out libkres was overly
optimistic, and will probably roll it back so that we're not shipping
a useless package.  When libkres matures, i'm sure we'll be able to
split it out again!

      --dkg



-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 
'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libkres-dev depends on:
ii  libkres9  3.2.1-1

libkres-dev recommends no packages.

libkres-dev suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: knot-resolver
Source-Version: 3.2.1-2

We believe that the bug you reported is fixed in the latest version of
knot-resolver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 923...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor <d...@fifthhorseman.net> (supplier of updated knot-resolver 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 07 Mar 2019 16:23:16 -0500
Source: knot-resolver
Architecture: source
Version: 3.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: knot-resolver packagers <knot-resol...@packages.debian.org>
Changed-By: Daniel Kahn Gillmor <d...@fifthhorseman.net>
Closes: 923970
Changes:
 knot-resolver (3.2.1-2) unstable; urgency=medium
 .
   * Standards-Version: move to 4.3.0 (no changes needed)
   * move to debhelper 12
   * Avoid breakage when built against knot-dns 2.8.0
   * d/tests/control: wrap-and-sort
   * Drop libkres9 and libkres-dev packages (Closes: #923970)
   * avoid clobbering CXXFLAGS when compiling lua-aho-corasick
   * missing-sources: updated dygraph-combined.js to match minified version
   * avoid shipping pre-built glyphicons-halflings-regular.woff2
Checksums-Sha1:
 eaea88d95bbe9c9d435c4e3b1ec227d612156207 2297 knot-resolver_3.2.1-2.dsc
 1ea6725b36cd052acddf3dda020c1603fcccec02 833 
knot-resolver_3.2.1.orig.tar.xz.asc
 720eccd47d86110cf755bbf9effb384497e79853 403484 
knot-resolver_3.2.1-2.debian.tar.xz
 df918b43fcdb107600af22fc6b8c06b210768386 9349 
knot-resolver_3.2.1-2_amd64.buildinfo
Checksums-Sha256:
 186a377178663c0202d851dac4c3923579781f5af1362cf920480de8a58f7bca 2297 
knot-resolver_3.2.1-2.dsc
 cc11c3e652e88a286bdfb95bf34f68f8cd2ac79dc23f2643430e344aee22c66a 833 
knot-resolver_3.2.1.orig.tar.xz.asc
 ed28437b0e943f957a8b5ca8a6ba64c58bee2145b87dc7111ad921ac99167682 403484 
knot-resolver_3.2.1-2.debian.tar.xz
 b0a1cfb27807f1d280aac98c188172f6a515b00113185feccc2697a1e7d427ca 9349 
knot-resolver_3.2.1-2_amd64.buildinfo
Files:
 eac5892d4681e2bd1280e9c68b6ef6e3 2297 net optional knot-resolver_3.2.1-2.dsc
 05e0acc0b22ffaa9605309f4343f8198 833 net optional 
knot-resolver_3.2.1.orig.tar.xz.asc
 2bcd21e9adcbbae31c4de2fc5d4eb917 403484 net optional 
knot-resolver_3.2.1-2.debian.tar.xz
 0efb0e513481534fe3966283870b4110 9349 net optional 
knot-resolver_3.2.1-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTJDm02IAobkioVCed2GBllKa5f+AUCXIG2cwAKCRB2GBllKa5f
+MTqAP0XGmCst7Lg5gcnIJxI+JUft7IErsXngAH1Nrfu/euohQD/a76pWOfE3fz4
V6hXguwXqBFJvz77tWxSrwPaN7R82Qw=
=LbyR
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to