From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Plain text libloc database dumps are currently missing any IP network information
Date: Fri, 04 Mar 2022 16:38:22 +0000 [thread overview]
Message-ID: <438aa8fa-e9eb-322a-825d-be2be229decb@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
Hello libloc users,
apparently, libloc 0.9.11 (https://lists.ipfire.org/pipermail/location/2022-March/000536.html) introduced
a regression in the "dump" command, which dumps any given location database into one big, plain text file.
After upgrading to 0.9.11, this file does not contain any IP network information, only information related
to Autonomous Systems.
Anybody using the _actual_ binary location database (for example, via "location lookup") is not affected.
This issue only affects users relying on plain text database dumps.
While this bug is currently under investigation (https://bugzilla.ipfire.org/show_bug.cgi?id=12790),
affected users can temporarily go back to libloc 0.9.10, where "location dump" works fine, including dumping
databases generated by libloc 0.9.11.
Apologies for any inconvenience caused.
Thanks, and best regards,
Peter Müller
reply other threads:[~2022-03-04 16:38 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=438aa8fa-e9eb-322a-825d-be2be229decb@ipfire.org \
--to=peter.mueller@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