Created attachment 254051 [details] patch Latest release 1.12.6 of mu has significant improvement upon 1.8.13 currently supported. The patch provide an update and merge the mail/mu4e front-end. This report cancel and replace bug #280678.
Error status
^Triage: remove now-redundant 'patch' Keyword.
mu 1.12.7 is out: https://github.com/djcb/mu/releases/tag/v1.12.7
mu 1.12.8 is out: https://github.com/djcb/mu/releases/tag/v1.12.8 Is there something wrong with RWN's patch? Does it make any sense to update the patch?
Created attachment 256225 [details] New patch 1.12.8 version The patch is updated to consider last version 1.12.8. It removes the separate mail/mu4e ports which is the front-end of mail/mu. Also, I proposed to become maintainer of this port.
Review is available at review D46961
Works fine with new release 1.12.8 https://github.com/emacsmirror/mu4e/releases/tag/v1.12.8
Meanwhile mu 1.12.9 is out. The version in ports is more than two years old. maintainer timeout/reset? Is the current maintainer still using the port and can he comment what's wrong with the patch or why we should keep an outdated/unsupported(?) version?
Created attachment 258163 [details] mu 1.12.9 Patch on top of 1.12.8
What is the process to update mu ?
This does need merging; the current version of mu4e in ports (1.8.13) seems broken with the current version of Emacs (30.1). Trying to send mail returns the following error: [mu4e] Message sent error in process sentinel: async-when-done: Invalid read syntax: "#<" error in process sentinel: Invalid read syntax: "#<"
Hmmm. Although once patched and installed, the same problem persists. I'll file a bug upstream for this one.
No feedback for six months. :-( Maintainer timeout? Can this port be returned to the pool? Maybe someone else want to take it.
I've been an mu / mu4e user for years, and *many* years ago used to work on mail server software for a living (Netwin's DPOP and DLIST). I'd be willing to take over port maintenance.
Hello, In fact I proposed myself to be the maintainer (see maintainer item in the patch) and my question on 2025-04-10 was about becoming maintainer in some sense... However, I have no experience in maintaining a port. But, I use my up-to-date version of mu on my network, build with poudriere, since almost 1 year and works fine with the patches I proposed. If you think you have more experience go ahead. Note, the maintainer is not responding since this first bug #280678 I reported on mu. Best, E.
My apologies! I hadn't noticed. I'm quite content not to become the maintainer, I just hope *someone* will :)
(In reply to Duncan Bayne from comment #12) Did you install successively the 2 patches to build the port ?
Maintainer timeout? Please return mail/mu to the pool so that someone else can take and update it. Latest version is now: 1.12.11 (May 10th, 2025).