Bug#924188:

2019-03-17 Thread Matthias Urlichs
Yeah, a dependency is the best short term solution. Will upload shortly.

By the time the next release cycle becomes relevant, the library will be
removed anyway – KNXD is about to grow a more reasonable API, most
likely based on protobuf.

-- 
-- Matthias Urlichs




signature.asc
Description: OpenPGP digital signature


Bug#924188:

2019-03-17 Thread Sergei Golovan
Hi!

In the short run, while the new packages won't be able to enter
buster, I would just make knxd-dev depend on knxd-tools (=
${binary:Version}). But for the next release cycle slitting out the
library would be preferable.

Cheers!
-- 
Sergei Golovan



Bug#924188: knxd-dev: missing dependency on library package - and a separate library package in the first place

2019-03-10 Thread Andreas Beckmann
Package: knxd-dev
Version: 0.14.29-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m19.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libeibclient.so -> libeibclient.so.0.0.0 (knxd-dev)

libeibclient.so.0.0.0 is shipped in knxd-tools ...
this should rather be a separate library package libeibclient0
s.t. knxd-dev can depend on libeibclient0 (= ${binary:Version})


cheers,

Andreas


knxd-dev_0.14.29-3.log.gz
Description: application/gzip