From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Re: Pending package updates
Date: Mon, 07 Sep 2020 15:16:07 +0200 [thread overview]
Message-ID: <8f93ca4b-4cee-5047-1612-cab40db3faab@gmail.com> (raw)
In-Reply-To: <b6ca1b6b-5c84-b7cf-a03c-57ef84bd48ed@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2856 bytes --]
Hi Michael,
Ignore my earlier question about logging in to the IPFire Bugzilla. I was using the wrong email address for logging in. I have successfully logged in now.
Regards,
Adolf.
On 07/09/2020 13:33, Adolf Belka wrote:
> Hi Michael,
>
> I was going to raise a ticket for fixing collectd in bugzilla but I need an account to do that and I couldn't find any registration option to create an account. Can you help me with getting an account on Bugzilla for IPFire.
>
> I need this anyway as I want to have a look at some of the bugs listed in there to see if there is anything that I can help with.
>
>
> For the iptables patch, I will send that shortly and also the patches for libnetfilter-queue, libnetfilter-conntrack and conntrack-tools. Then you have them all available and can then decide which ones you will merge and when.
>
> Regards,
>
> Adolf.
>
> On 04/09/2020 17:46, Michael Tremer wrote:
>> Hello,
>>
>>> On 3 Sep 2020, at 09:23, Adolf Belka <ahb.ipfire(a)gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> Just had a look through the netfilter mailing list archive and found the announcement for iptables-1.8.4 and it mentions the following:-
>>>
>>> "libiptc: - Generic libiptc.so shared object is no longer built, likely all users link to libip4tc.so or libip6tc.so directly"
>>>
>>> So that explains the problem we are having. So it looks like collectd needs to be rewritten to use libip4tc.so or libip6tc.so shared libraries. Until then I presume we have to stay on iptables-1.8.3
>> For the time being, yes. There are some other packages to work on first.
>>
>> However, this would be an easy fix we can simply patch into our version of collectd and therefore we should be fine.
>>
>> Could someone please submit a patch for iptables which we are not going to merge, yet, and create a ticket for fixing collectd and assigning that to me?
>>
>> Best,
>> -Michael
>>
>>> Regards,
>>>
>>> Adolf
>>>
>>>
>>> On 03/09/2020 10:14, Adolf Belka wrote:
>>>> Hi all,
>>>>
>>>> I ran the build of iptables 1.8.3 and 1.8.5 and compared the logs for the two of them. The problem seems to be that 1.8.5 never creates the libiptc.so libraries. It only creates the libip4tc.so and libip6tc.so libraries.
>>>>
>>>> iptables-1.8.3 creates libip4tc.so, libip6tc.so and libiptc.so libraries.
>>>>
>>>>
>>>> I have checked the changelogs for the 1.8.4 and 1.8.5 releases of iptables and it doesn't mention anything about this, as far as I can see.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Adolf
>>>>
>>>> On 02/09/2020 20:27, Matthias Fischer wrote:
>>>>> Hi,
>>>>>
>>>>> On 02.09.2020 17:36, Michael Tremer wrote:
>>>>>> Did the iptables build by any chance remove libiptc?
>>>>> Yes. Confirmed with a clean build.
>>>>>
>>>>> No idea how to fix this, yet.
>>>>>
>>>>> Best,
>>>>> Matthias
next prev parent reply other threads:[~2020-09-07 13:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 18:22 Peter Müller
2020-09-01 21:01 ` Adolf Belka
2020-09-02 13:26 ` Michael Tremer
2020-09-02 13:42 ` Adolf Belka
2020-09-02 14:24 ` Adolf Belka
2020-09-02 15:36 ` Michael Tremer
2020-09-02 16:02 ` Matthias Fischer
2020-09-02 18:27 ` Matthias Fischer
2020-09-03 8:14 ` Adolf Belka
2020-09-03 8:23 ` Adolf Belka
2020-09-04 15:46 ` Michael Tremer
2020-09-05 14:09 ` Adolf Belka
2020-09-07 11:33 ` Adolf Belka
2020-09-07 13:16 ` Adolf Belka [this message]
2020-09-02 13:25 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f93ca4b-4cee-5047-1612-cab40db3faab@gmail.com \
--to=ahb.ipfire@gmail.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox