user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 0/4] test fixes for latest CPAN modules
Date: Wed, 30 May 2018 11:28:43 -0400	[thread overview]
Message-ID: <20180530152843.abfkgu7sf5spjoxa@chatter> (raw)
In-Reply-To: <20180530115719.GA17038@dcvr>

On Wed, May 30, 2018 at 11:57:19AM +0000, Eric Wong wrote:
>> Is this easier solved by upgrading to the version of xapian > 1.2.22? I
>> can probably nag the Epel packager to do that if it's a legitimate bug
>> in Xapian.
>
>Maybe... I wonder if there's other patches in the Epel package
>or other system-level differences causing this.

I'm fine with that -- in fact, I already requested that the package in
EPEL is updated to the latest 2.2.

We can just leave things as-is, as I definitely don't see the same issue
with 2.2.25.

-K

      reply	other threads:[~2018-05-30 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 19:20 [PATCH 0/4] test fixes for latest CPAN modules Eric Wong
2018-05-11 19:20 ` [PATCH 1/4] content_id: workaround quote handling change in Email::* modules Eric Wong
2018-05-11 19:20 ` [PATCH 2/4] convert+compact: fix when running without ~/.public-inbox/config Eric Wong
2018-05-11 19:20 ` [PATCH 3/4] t/v2mda: setup emergency Maildir for test Eric Wong
2018-05-11 19:20 ` [PATCH 4/4] t/search: quiet warning from Encode.pm Eric Wong
2018-05-11 19:27 ` [PATCH 0/4] test fixes for latest CPAN modules Konstantin Ryabitsev
2018-05-11 19:38   ` Eric Wong
2018-05-11 19:50     ` Konstantin Ryabitsev
2018-05-16  5:12       ` Eric Wong
2018-05-23 21:51         ` Konstantin Ryabitsev
2018-05-24  8:41           ` Eric Wong
2018-05-24 15:15             ` Konstantin Ryabitsev
2018-05-30 11:57               ` Eric Wong
2018-05-30 15:28                 ` Konstantin Ryabitsev [this message]

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20180530152843.abfkgu7sf5spjoxa@chatter \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.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).