Hi,
sorry for the late reply!
On Fri, 2020-03-06 at 18:11 -0700, Antonio Russo wrote:
>
> Because that is not the case, the pkg-config calls to get the path to
> libip4tc{.h,.so} libip6tc{.h,.so} and libiptc.h fail. You can get around
> that with the trivial patch I've attached.
Unfortunately
On 3/6/20 4:50 PM, Bernd Zeimetz wrote:
>
> I fail to understand the reason behind this: libiptc-dev still exists
> and collectd needs it to build successfully. Please convince me why
> there is a reason for this change.
>
My apologies: I for some reason thought I saw "pkg-config --exists libip4
On 3/1/20 6:46 PM, Antonio Russo wrote:
> Sorry for the noise here. I understand that these are two separate issues,
> and I believe
> that upstream has addressed the libiptc -> libip4tc name change in their
> 5.10.0 release.
>
> My MR has been updated to only pull in libip4tc-dev and libip6t
Sorry for the noise here. I understand that these are two separate issues, and
I believe
that upstream has addressed the libiptc -> libip4tc name change in their 5.10.0
release.
My MR has been updated to only pull in libip4tc-dev and libip6tc-dev, and not
libiptc-dev
in a third patch, so there
I'm trying to address the changes in the iptables package for collectd.
I can avoid the dependency on the transitional iptables-dev package (see [1]),
but I'm confused by the
statement:
> The src:iptables debian package (v1.8.4-1) dropped the libiptc-dev and
> libiptc0 binary packages.
I see t
5 matches
Mail list logo
