Tags: fixed-upstream

Hi,
while looking at this FTFBS I've found that the new upstream version
4.2 [1] would fix this problem.
I found no clear documentation on how the dfsg was generated (some
vendored libs removed, some not), so I had the feeling "just trying"
might make things worse.
But I wanted to pass this FYI to the bug to avoid anyone to re-debug this.

The timeline/reason for all of this this is:
Dec 2019 - ndpi 3.0 / ntopng 3.8.1 uploaded by the maintainer
June 2020 - ntopng removed for blocking ndpi [2]
Winter 20/21 - various helpful people bumped ndpi for CVEs and some bug fixes

But the new ndpi makes ntopng an FTFBS.
And in turn the old ntopng would block ndpi.

Bonus: Also AFAICS ndpi (lib) only exists (from the Archives POV) for
ntopng, so there is almost no gain for it to stay around alone.

[1]: https://github.com/ntop/ntopng/releases/tag/4.2
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953181

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

Reply via email to