public inbox for location@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: DB version number?
Date: Mon, 27 Sep 2021 09:08:04 +0000	[thread overview]
Message-ID: <d78266b4-f64e-808e-9b6f-b2f75bf66c91@ipfire.org> (raw)
In-Reply-To: <49d2b73a-c5e5-706c-7454-ff449cd5bf77@riseup.net>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Hi nusenu,

> For transparency and archive purposes I'd like to show the location database version
> that has been used for the AS number and name lookups on the website. 

that's a good idea. Actually, I am missing this information on https://metrics.torproject.org/rs.html
as well - it appears as they still use an outdated location database there, but I don't know which one.

> Is there a versioning scheme of the DB? if so: How do I retrieve the version of the db file?
> Or is this timestamp the best bet? 

Yes, there is a scheme for the database _format_ (currently set to "1"), in case we need to change that
somewhere in the future. The versioning scheme for the database _contents_ is a simple timestamp, and
the output of "location version" is based on the database on your filesystem (not the most recent one
on the servers):

> $ location version
> Mon, 27 Sep 2021 05:47:57 GMT


> I'm not looking for the version of the tool itself (which is shown via location --version ). 

Yes, that is unfortunately kinda confusing... :-)

Thanks, and best regards,
Peter Müller

  parent reply	other threads:[~2021-09-27  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26 20:27 nusenu
2021-09-27  9:02 ` Gisle Vanem
2021-09-27  9:11   ` Peter Müller
2021-09-27 16:37     ` nusenu
2021-09-27  9:08 ` Peter Müller [this message]
2021-09-27 16:37   ` nusenu
2021-09-27 18:17     ` Peter Müller

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=d78266b4-f64e-808e-9b6f-b2f75bf66c91@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