unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: 51956-done@debbugs.gnu.org
Subject: bug#51956: [PATCH] On core-updates-frozen, geary is criminally outdated
Date: Fri, 19 Nov 2021 14:20:32 +0100	[thread overview]
Message-ID: <87r1bcl1sv.fsf@gnu.org> (raw)
In-Reply-To: <87h7c99sft.fsf@planete-kraus.eu> (Vivien Kraus's message of "Thu, 18 Nov 2021 20:25:58 +0100")

Hi!

Vivien Kraus <vivien@planete-kraus.eu> skribis:

> I finally managed to upgrade geary. The latest release lacks the GMime
> 3.0 vapi, and that’s not something we can generate easily (there’s
> custom metadata and custom code), so I had to install it with gmime.
>
> What do you think?

No strong opinion, LGTM.

> From 65c6544aca89c3a8797de22861f06a3f7bb831bf Mon Sep 17 00:00:00 2001
> From: Vivien Kraus <vivien@planete-kraus.eu>
> Date: Thu, 18 Nov 2021 19:44:03 +0100
> Subject: [PATCH 1/2] gnu: gmime: Install the vapi file.
>
> * gnu/packages/mail.scm (gmime)[configure flags]: Build the vapi file.
> [native-inputs]: Add vala.

[...]

> From cf80e70f47532fa5057755b6e08cc6ea1a346a1f Mon Sep 17 00:00:00 2001
> From: Vivien Kraus <vivien@planete-kraus.eu>
> Date: Wed, 10 Nov 2021 20:18:46 +0000
> Subject: [PATCH 2/2] gnu: geary: Upgrade to 40.0
>
> * gnu/packages/gnome.scm (geary): Upgrade to 40.0.

Applied!

Let’s discuss the possibility of getting rid of gmime 2.6 separately.

Thanks,
Ludo’.




      parent reply	other threads:[~2021-11-19 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 19:25 [bug#51956] [PATCH] On core-updates-frozen, geary is criminally outdated Vivien Kraus via Guix-patches via
     [not found] ` <handler.51956.B.163726359315148.ack@debbugs.gnu.org>
2021-11-18 20:28   ` [bug#51956] Acknowledgement ([PATCH] On core-updates-frozen, geary is criminally outdated) Vivien Kraus via Guix-patches via
2021-11-19 13:20 ` Ludovic Courtès [this message]

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=87r1bcl1sv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=51956-done@debbugs.gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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).