From: Cayetano Santos via Guix-patches via <guix-patches@gnu.org>
To: 67964-done@debbugs.gnu.org
Cc: 67964@debbugs.gnu.org
Subject: bug#67964: Done
Date: Wed, 03 Jan 2024 10:03:41 +0100 [thread overview]
Message-ID: <87frzevlbh.fsf@inventati.org> (raw)
Message-ID: <20240103090341.sWHun6PnGr_8T5SdVgw740vlR81k32eTmJpCbRFz8wo@z> (raw)
In-Reply-To: <87plyxtqcx.wl-hako@ultrarare.space>
>sam. 23 déc. 2023 at 13:55, Hilton Chain <hako@ultrarare.space> wrote:
> On Sat, 23 Dec 2023 05:15:03 +0800,
> Liliana Marie Prikler wrote:
>>
>> Am Freitag, dem 22.12.2023 um 13:31 +0800 schrieb Hilton Chain:
>> > Quoted from the package's readme.org:
>> > "Warning: As of 2021-01-06 this package is broken since mu4e has
>> > made changes to its protocol. New maintainer wanted!."
>> >
>> > See also:
>> > https://gitlab.com/ambrevar/mu4e-conversation/-/issues/18
>> > https://gitlab.com/ambrevar/mu4e-conversation/-/issues/19
>> >
>> > * gnu/packages/emacs-xyz.scm (emacs-mu4e-conversation): Delete
>> > variable.
>> >
>> > Reported-by: Cayetano Santos <csantosb@inventati.org>
>> > Change-Id: I1a0ade274f1e9aac180c68fe0223a6aea77ff80c
>> > ---
>> I assume this also affects Guix' version?
>
> I don't know... Could you explain more about this?
>
>> Where can I read more about this report?
>
> It's reported in bug#67944, the content is the same quote.
This may be closed now, as already merged in master.
next prev parent reply other threads:[~2024-01-03 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 5:31 [bug#67964] [PATCH] gnu: Remove emacs-mu4e-conversation Hilton Chain via Guix-patches via
2023-12-22 21:15 ` Liliana Marie Prikler
2023-12-23 5:55 ` Hilton Chain via Guix-patches via
2024-01-03 9:03 ` Cayetano Santos via Guix-patches via [this message]
2024-01-03 9:03 ` bug#67964: Done Cayetano Santos via Guix-patches via
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=87frzevlbh.fsf@inventati.org \
--to=guix-patches@gnu.org \
--cc=67964-done@debbugs.gnu.org \
--cc=67964@debbugs.gnu.org \
--cc=csantosb@inventati.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://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).