unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: yasu@yasuaki.com, 43528@debbugs.gnu.org
Subject: bug#43528: Download all issues so I can search?
Date: Sun, 20 Sep 2020 21:32:33 +0200	[thread overview]
Message-ID: <878sd4tfam.fsf@elephly.net> (raw)
In-Reply-To: <9c8d46eecb649c5bce585926d4aaf322@tobias.gr>


Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

> Hi!
>
> On 2020-09-20 9:30, Yasuaki Kudo wrote:
>> Hi,
>> If possible, I would like to download all guix issues in the tracker
>> (in other words, database dump?) so I can just use full text search
>> locally.   Is it possible?
>
> Probably!  This is basically what Mumi, the software behind
> issues.guix.gnu.org, does: pull all bug-guix and guix-patches mail
> from debbugs.gnu.org and index it locally using Mu.
>
> I don't *think* it uses any secret API/authentication/whitelisted IPs
> etc. but am not very familiar with its innards.

Actually it does exactly that (whitelisted IP doing rsync), ever since
The Indicident.  I used to just fetch all mbox files for all Guix bugs,
but this put the Debbugs servers under excessive load.  After the
server’s IP was blocked from accessing Debbugs we negotiated rsync
access.

We do have full text search on issues.guix.gnu.org.  It was brought to
my attention that it’s not yielding expected results since a while,
though, so this would have to be investigated.

-- 
Ricardo




  reply	other threads:[~2020-09-20 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-20  7:30 bug#43528: Download all issues so I can search? Yasuaki Kudo
2020-09-20 17:33 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-09-20 19:32   ` Ricardo Wurmus [this message]
2020-09-21 22:27 ` Michael Rohleder
2020-10-09  1:41   ` Maxim Cournoyer
2020-10-09  3:37     ` Bengt Richter
2020-09-21 22:54 ` zimoun

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878sd4tfam.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=43528@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=yasu@yasuaki.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).