From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: libloc 0.9.16 released
Date: Sat, 29 Oct 2022 14:35:51 +0100 [thread overview]
Message-ID: <66FBD3A5-6729-4FC9-8092-5394B5EEBF82@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
Hello,
This is the release announcement for libloc 0.9.16. It comes with the following changes:
* The tarball now includes a recent default database which is going to be installed into the system. Having some data is better than having no data to start with. This will make packaging libloc easier for third-party vendors.
* An issue has been resolved which lead to only one signature being written, even when multiple keys were passed to the database writer. There have also been further improvements on handling any errors during signature validation.
* export: Exporting into the ipset format has been fixed
* An issue with random strings being shown for vendor and description has been fixed when those attributes were not set at all
* An incorrect default database path has been fixed
* Some sanity checks for importing data from Spamhaus have been implemented to prevent importing any corrupted data
* perl: Parallel builds were broken and the module is now installed into the correct path. Thanks to Petr Písař.
* The man page for the “location” command is now being installed in section 1 instead of 8. Thanks to Petr Písař.
Thank you to everyone who has contributed to this release.
You can find the source here:
https://git.ipfire.org/?p=location/libloc.git;a=shortlog;h=refs/tags/0.9.16
https://source.ipfire.org/releases/libloc/libloc-0.9.16.tar.gz
Best,
-Michael
reply other threads:[~2022-10-29 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=66FBD3A5-6729-4FC9-8092-5394B5EEBF82@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@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