From: Pierre Langlois <pierre.langlois@gmx.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Pierre Langlois <pierre.langlois@gmx.com>, 49751-done@debbugs.gnu.org
Subject: bug#49751: [PATCH] gnu: mu: Update to 1.6.0.
Date: Tue, 10 Aug 2021 14:56:16 +0100 [thread overview]
Message-ID: <87fsvho0y5.fsf@gmx.com> (raw)
In-Reply-To: <87v94dquxt.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hi Ludo,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Pierre,
>
> Looks like this fell through the cracks!
>
> Pierre Langlois <pierre.langlois@gmx.com> skribis:
>
> [...]
>
>>> Turns out we need to remove the xapian database (deleting .cache/mu and
>>> regenerating it) https://github.com/djcb/mu/issues/2058
>>>
>>> That worked for me, although it's a shame that there are no warnings,
>>> the issue also mentions another potential problem, so we might want to
>>> wait a little bit before updating in case upstream releases a point
>>> release with a smoother transition.
>>
>> 1.6.1 was just released, users should get a warning that they need to
>> run `mu init' https://github.com/djcb/mu/releases/tag/1.6.1
>>
>> Ok to apply?
>
> In general, if it works according to your testing and nobody has
> anything to say, you can feel free to go ahead, as per:
>
> https://guix.gnu.org/manual/devel/en/html_node/Commit-Access.html#Commit-Policy
Sounds good! Pushed as b0a6b1f13ce17ec37600f5e8404e0c8c43302fe5, with
version 1.6.2 actually.
Thanks,
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
prev parent reply other threads:[~2021-08-10 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 21:12 [bug#49751] [PATCH] gnu: mu: Update to 1.6.0 Pierre Langlois
2021-07-27 23:13 ` Pierre Langlois
2021-07-28 14:38 ` Pierre Langlois
2021-07-31 11:02 ` [bug#49751] [PATCH] gnu: mu: Update to 1.6.1 Pierre Langlois
2021-08-10 13:40 ` [bug#49751] [PATCH] gnu: mu: Update to 1.6.0 Ludovic Courtès
2021-08-10 13:56 ` Pierre Langlois [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsvho0y5.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=49751-done@debbugs.gnu.org \
--cc=ludo@gnu.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 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.