From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Re: Pending package updates
Date: Thu, 03 Sep 2020 10:14:21 +0200 [thread overview]
Message-ID: <4f2ec2a1-7de1-ca0f-2b13-d3971fc134f4@gmail.com> (raw)
In-Reply-To: <7f292f48-f619-c320-8617-04a14aa98564@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
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-03 8:14 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 [this message]
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
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=4f2ec2a1-7de1-ca0f-2b13-d3971fc134f4@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