weird mumi message dupe/drop?

weird mumi message dupe/drop?

[Lilah Tascheter]

so, I just tried to apply v3 of issue #73202, but it failed, first
trying to apply a regular email, then completely dropping the last
patch (in email order, so actually patch 12/14). looking into it, it
seems like the raw messages aren't indexed properly? when downloading
the raw mbox for either @17 or @18, the message for @17 is returned.
all subsequent messages are then shifted one earlier than they should
be. so, mumi am just doesn't work at all.

any clues wtf happened? honestly I'm not even sure where to report this
(if to report this?) and if anyone can, like, fixup the patch series
message files?

thanks!
lilah

Re: weird mumi message dupe/drop?

[Andreas Enge]

Hello Lilah,

Am Thu, Sep 26, 2024 at 11:59:03AM -0500 schrieb Lilah Tascheter:
> so, I just tried to apply v3 of issue #73202, but it failed, first
> trying to apply a regular email, then completely dropping the last
> patch (in email order, so actually patch 12/14). looking into it, it
> seems like the raw messages aren't indexed properly? when downloading
> the raw mbox for either @17 or @18, the message for @17 is returned.
> all subsequent messages are then shifted one earlier than they should
> be. so, mumi am just doesn't work at all.
> any clues wtf happened? honestly I'm not even sure where to report this
> (if to report this?) and if anyone can, like, fixup the patch series
> message files?

I suspect this is not a problem with Mumi, since
   https://qa.guix.gnu.org/issue/73202
shows that the commits do not apply.

The QA page
   https://qa.guix.gnu.org/patches
shows a number of patches that cannot be applied; the core-updates merge
probably has not made things easier.

It would be nice if submitters whose patches stopped applying could send
a new version of their commits.

Andreas