Nope.
Fixed.
Thanks!
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
If a service has a requirement on 'networking
(either from accepting a shepherd-requirements field from its configuration
record-type or
from the service-type definition) and networking is provided by NetworkManager,
it will not
work as intended. This is because networking is prematurely flagged
This is now fixed in mumi commit
4361d69de393a55ad27574d10d7c6ad62477a13e.
--
Ricardo
Hello Julius.
Julius Schwartzenberg writes:
> I didn't imagine
> I would need to do a 'guix pull' after running it. It seems I ran it
> at a bad moment, just as 1.4.0 was about to be released.
Indeed, but upgrading without compiling will be easier with bordeaux.
(Probably it would also have been
This is now fixed with mumi commit
ca4d83865943f2851b07deaf34b026705c46dd41.
The problem here was that the attachment did not come with a
content-disposition header reporting the size of the attachment. As a
fall back mumi now also looks at the actual size of the message when
determining whether
Commit 0a90eeda9b5e12a2f83e3917c46fa539f308d0c8 fixes this. Debbugs
apparently stores the raw email with the first two lines swapped. I
just swap the two lines back. The output from mumi’s /raw endpoint now
only differs in trailing white space.
--
Ricardo
I cannot reproduce this with the current version of mumi.
https://issues.guix.gnu.org/47513#3 points to the restinio email, and
the download links fetch the corresponding email / message parts.
--
Ricardo
> See http://issues.guix.gnu.org/49114, which Mumi currently
> titles
>
> ‘guix_ lint’ should catch certificate validation exceptions
>
> There's no underscore in the original subject.
The debbugs “.log” file for issue 49114 contains this line:
Subject: bug#49114: =?UTF-8?Q?=E2=80=98guix_?=
