From: Jan Engelhardt <jengelh@inai.de>
To: Jozsef Kadlecsik <kadlec@netfilter.org>
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 7.8 released
Date: Thu, 19 Nov 2020 23:07:45 +0100 (CET) [thread overview]
Message-ID: <83oq5412-o0sq-5q31-s7o5-s0q28s12844@vanv.qr> (raw)
In-Reply-To: <alpine.DEB.2.23.453.2011192237290.19567@blackhole.kfki.hu>
On Thursday 2020-11-19 22:46, Jozsef Kadlecsik wrote:
>Hi Jan,
>
>On Thu, 19 Nov 2020, Jan Engelhardt wrote:
>
>> LIBVERSION changed from 14:0:1 (ipset 7.6) to 14:1:2,
>> producing libipset.so.13 (7.6) and now libipset.so.12
>>
>> That seems incorrect! It should have been
>> - 14:0:1 (no changes)
>> - 15:0:2 (compatible changes)
>> - 15:0:0 (incompatible changes)
>
>Oh, my. It should be 15:0:2 (compatible changes). I dunno how many times I
>can mix it up, this numbering scheme is simply alien to my brain wiring.
If in doubt, always use :0:0 --- and make a mental note of exactly the
:0:0 requirement in Make_global.am. :-)
Distros can always rebuild transitively. They have to do that anyway for
things like /usr/lib64/libbfd-2.35.0.20200915-1.so (with a date, it
could change daily anyway). But recovering from a backjumping lib...
next prev parent reply other threads:[~2020-11-19 22:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 20:48 [ANNOUNCE] ipset 7.8 released Jozsef Kadlecsik
2020-11-19 21:10 ` Jan Engelhardt
2020-11-19 21:46 ` Jozsef Kadlecsik
2020-11-19 22:07 ` Jan Engelhardt [this message]
2020-11-20 3:01 ` Neutron Soutmun
2020-11-20 8:07 ` Jozsef Kadlecsik
2020-11-20 13:18 ` Neutron Soutmun
2020-12-04 12:47 ` Ed W
2020-12-07 14:54 ` Jozsef Kadlecsik
[not found] ` <701adbbb-202a-4ee4-ce2e-ecaaed6dc3b5@wildgooses.com>
2020-12-10 22:19 ` ipset 7.9 compilation fix on kernel 4.14 Jozsef Kadlecsik
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=83oq5412-o0sq-5q31-s7o5-s0q28s12844@vanv.qr \
--to=jengelh@inai.de \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).