From: Olly Betts <olly@survex.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Xapian Discussion <xapian-discuss@lists.xapian.org>,
"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: How to recover from this permanent fatal error?
Date: Sun, 6 Jun 2021 02:45:17 +0100 [thread overview]
Message-ID: <20210606014517.GD9932@survex.com> (raw)
In-Reply-To: <CAMP44s3cRiJ3dXrjf+QBwWZc2HyXrqNqSd13n6jxy2FtAcVM3A@mail.gmail.com>
On Sat, Jun 05, 2021 at 09:39:28AM -0500, Felipe Contreras wrote:
> On Fri, Jun 4, 2021 at 9:43 PM Olly Betts <olly@survex.com> wrote:
> > I'd suggest trying this simple tool I wrote that can probably rescue the
> > tags from a broken notmuch database (the tags are the part notmuch can't
> > just recreate by reindexing):
> >
> > https://git.xapian.org/?p=xapian;a=blob;f=README.notmuch;hb=refs/heads/notmuch-tag-rescue-hack
>
> I can't seem to build it:
[...]
> ./backends/documentinternal.h:339:29: error: ‘numeric_limits’ was not
> declared in this scope
> 339 | wdf_delta = numeric_limits<Xapian::termcount>::max();
> | ^~~~~~~~~~~~~~
Oh, that's a missing header include which older compilers seemed to
not complain about - it was fixed on master a few months ago, and I've
just merged master to the branch to pick up the fix so it should build
now.
Cheers,
Olly
next prev parent reply other threads:[~2021-06-06 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 0:44 How to recover from this permanent fatal error? Felipe Contreras
2021-06-05 1:37 ` David Bremner
2021-06-05 1:40 ` Felipe Contreras
2021-06-05 2:43 ` Olly Betts
2021-06-05 14:39 ` Felipe Contreras
2021-06-06 1:45 ` Olly Betts [this message]
2021-06-06 4:40 ` Felipe Contreras
2021-06-06 10:08 ` Olly Betts
2021-06-06 12:48 ` Felipe Contreras
2021-06-07 3:45 ` Olly Betts
2021-06-07 7:07 ` Felipe Contreras
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210606014517.GD9932@survex.com \
--to=olly@survex.com \
--cc=felipe.contreras@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=xapian-discuss@lists.xapian.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://yhetil.org/notmuch.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).