From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Andrew Tropin <andrew@trop.in>,
Cayetano Santos <csantosb@inventati.org>,
67964@debbugs.gnu.org
Subject: [bug#67964] [PATCH] gnu: Remove emacs-mu4e-conversation.
Date: Sat, 23 Dec 2023 13:55:26 +0800 [thread overview]
Message-ID: <87plyxtqcx.wl-hako@ultrarare.space> (raw)
In-Reply-To: <d5a16dd0aa02e8fbcbba8839cd865a79df73c28b.camel@gmail.com>
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.
next prev parent reply other threads:[~2023-12-23 5:56 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 [this message]
2024-01-03 9:03 ` [bug#67964] Done Cayetano Santos via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plyxtqcx.wl-hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=67964@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=cox.katherine.e+guix@gmail.com \
--cc=csantosb@inventati.org \
--cc=hako@ultrarare.space \
--cc=liliana.prikler@gmail.com \
/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.