all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: 61557@debbugs.gnu.org
Cc: elb@kb8ojh.net
Subject: bug#61557: bug database indexing problem for bug #61557
Date: Sat, 25 Feb 2023 09:58:57 +0100	[thread overview]
Message-ID: <87r0uew27i.fsf@gmx.de> (raw)
In-Reply-To: <Y/ly3+gvZbQuM7Wc@colt.lan> (Ethan Blanton via's message of "Fri,  24 Feb 2023 21:30:55 -0500")

Ethan Blanton via "General discussion for the tracker at
debbugs.gnu.org" <help-debbugs@gnu.org> writes:

Hi Ethan,

> Bug #61557, filed against the vdirsyncer package in Guix and having
> the title "vdirsyncer fails to verify certificates", does not show up
> in the Guix bug database at issues.guix.gnu.org when searching by
> keywords such as "vdirsyncer" or "certificates", although it does
> appear when searching for "61557".

When I search for vdirsyncer, bug#61557 appears in the hit list.

Searching for certificates does not show such a hit. However, in the bug
messages this word appears only as certificates" or "certificates". This
seems to prevent the word to be indexed. The HyperEstraier search engine
counts only words, and a leading or trailing apostrophe seems to
suppress a string to be regarded as word. Just a guess, but it is the
most plausible explanation.

Best regards, Michael.




  parent reply	other threads:[~2023-02-26 15:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Y+6SIw5S64Rodiyi@colt.lan>
2023-02-25  2:44 ` bug#61557: vdirsyncer fails to verify certificates Tobias Geerinckx-Rice via Bug reports for GNU Guix
     [not found] ` <Y/ly3+gvZbQuM7Wc@colt.lan>
2023-02-25  8:58   ` Michael Albinus [this message]
2023-02-25 21:52 ` Leo Famulari
2023-03-26 22:05 ` Ethan Blanton via Bug reports for GNU Guix
2023-03-27 12:50   ` Giovanni Biscuolo

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=87r0uew27i.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=61557@debbugs.gnu.org \
    --cc=elb@kb8ojh.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.