Bug#772551: Suricata: missing library libhtp-0.5.12.so.1

2015-02-10 Thread Pierre Chifflier
On Mon, Feb 09, 2015 at 10:42:26PM +0100, Arturo Borrero Gonzalez wrote: On 9 February 2015 at 15:05, Pierre Chifflier pol...@debian.org wrote: This bug is solved by the next (pending) uploading, to be validated by the release team. I have a some questions: * How this could happen?

Bug#772551: Suricata: missing library libhtp-0.5.12.so.1

2015-02-10 Thread Ralph J.Mayer
s has nothing to do with the override - it is caused by the fact that a newer libhtp was uploader *after* suricata. I think a triggered rebuild of suricata could be enough, but since we are going to upload suricata to close the other bugs, this will also resolve the problem. I don't think it

Bug#772551: Suricata: missing library libhtp-0.5.12.so.1

2015-02-09 Thread Pierre Chifflier
tags 772551 + pending block 772551 by 777042 thanks Hi, This bug is solved by the next (pending) uploading, to be validated by the release team. The two bug reports for the unblock requests are: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777040 (libhtp)

Processed: Re: Bug#772551: Suricata: missing library libhtp-0.5.12.so.1

2015-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tags 772551 + pending Bug #772551 [suricata] Suricata: missing library libhtp-0.5.12.so.1 Added tag(s) pending. block 772551 by 777042 Bug #772551 [suricata] Suricata: missing library libhtp-0.5.12.so.1 772551 was not blocked by any bugs. 772551

Bug#772551: Suricata: missing library libhtp-0.5.12.so.1

2015-02-09 Thread Ralph J.Mayer
* 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

Bug#772551: Suricata: missing library libhtp-0.5.12.so.1

2015-02-09 Thread Arturo Borrero Gonzalez
On 9 February 2015 at 15:05, Pierre Chifflier pol...@debian.org wrote: This bug is solved by the next (pending) uploading, to be validated by the release team. I have a some questions: * How this could happen? Aren't these errors supposed to show up on build logs? * Why this doesn't seem to