* How this could happen? Aren't these errors supposed to show up on build logs?

suricata (2.0.4-1) was released 10.10.14, libhtp (0.5.15-1) six days later.

I think the problem is libhtp for setting the wrong SONAME.
Theres even a override in lintian, "upstream soname version is not correct"

I opened 777540 for this on libhtp after some discussion on #debian.de


rm


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to