From: Juliana Sims <juli@incana.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 62635@debbugs.gnu.org, ludo <ludo@gnu.org>
Subject: [bug#62635] Ping
Date: Tue, 16 May 2023 01:10:30 -0400 [thread overview]
Message-ID: <IPJQUR.XBL6DDIT12572@incana.org> (raw)
In-Reply-To: <52a8debc25fc85c96e2268f500e716e1f4a9f469.camel@gmail.com>
Hi,
Le mar, mai 16 2023 at 06:19:13 +0200, Liliana Marie Prikler
<liliana.prikler@gmail.com> a écrit :
>> It is true that Geary, like Evolution, needs a running Evolution Data
> Server to function correctly. However, this dependency is most often
> met by adding evolution-data-server to the operating-system packages,
> as not doing so causes other evolution-data-server-related issues
> IIRC.
It's probably beyond the scope of this current patch set, but is this
something that should be communicated to users somehow? I would never
have figured out about evolution-data-server if my friend hadn't
recognized the error message. (There are similar situations where other
packages require some non-dependency package to work/use all
functionality, so the solution to this would ideally be bigger than
just Geary and thus out of scope.)
>> It makes a difference for cross-builds, so you would have to check
> those.
Apparently librsvg is in the dependency graph for Geary, which is a
Rust library, meaning cross builds are not currently an option. So in
addition to removing the commit adding evolution-data-server as an
input, I've added another commit removing the redundant native-input
packages; feel free to simply drop the patch if the patch set looks
good otherwise and this is deemed a frivolous or unnecessary change. I
know dropping these native-inputs doesn't cause any issues because I'm
sending this email using the very Geary package I am about to submit
patches for :D
Anyway, patches incoming!
Thanks,
Juli
next prev parent reply other threads:[~2023-05-16 5:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 1:58 [bug#62635] [PATCH 0/2] gnu: geary: Add missing dependency, use g-expressions J. Sims via Guix-patches via
2023-04-03 2:00 ` [bug#62635] [PATCH 1/2] gnu: geary: Add missing input to fix launch bug J. Sims via Guix-patches via
2023-04-03 2:01 ` [bug#62635] [PATCH 2/2] gnu: geary: Use g-expressions J. Sims via Guix-patches via
2023-05-06 16:20 ` [bug#62635] [PATCH 0/2] gnu: geary: Add missing dependency, use g-expressions Ludovic Courtès
2023-05-07 19:06 ` [bug#62635] [PATCH v1 1/3] gnu: geary: Fix failing build Juliana Sims
2023-05-07 19:06 ` [bug#62635] [PATCH v1 2/3] gnu: geary: Add evolution-data-server as input Juliana Sims
2023-05-07 19:06 ` [bug#62635] [PATCH v1 3/3] gnu: geary: Use g-expressions Juliana Sims
2023-05-07 19:21 ` [bug#62635] [PATCH v2 1/3] gnu: geary: Fix failing build Juliana Sims
2023-05-07 19:21 ` [bug#62635] [PATCH v2 2/3] gnu: geary: Add evolution-data-server as input Juliana Sims
2023-05-07 19:44 ` Liliana Marie Prikler
2023-05-07 21:10 ` Juliana Sims
2023-05-07 19:21 ` [bug#62635] [PATCH v2 3/3] gnu: geary: Use g-expressions Juliana Sims
2023-05-15 13:55 ` [bug#62635] Ping Juliana Sims
2023-05-15 18:20 ` Liliana Marie Prikler
2023-05-16 1:36 ` Juliana Sims
2023-05-16 4:19 ` Liliana Marie Prikler
2023-05-16 5:10 ` Juliana Sims [this message]
2023-05-16 15:25 ` Liliana Marie Prikler
2023-05-16 5:12 ` [bug#62635] [PATCH v4 1/4] gnu: geary: Fix build failure Juliana Sims
2023-05-16 5:12 ` [bug#62635] [PATCH v4 2/4] gnu: geary: Use G-Expressions Juliana Sims
2023-05-16 5:13 ` [bug#62635] [PATCH v4 3/4] gnu: geary: Remove redundant native-inputs Juliana Sims
2023-05-16 16:24 ` [bug#62635] [PATCH v4 4/4] gnu: geary: Update to 43.0 Liliana Marie Prikler
2023-05-17 12:49 ` Juliana Sims
2023-05-21 20:35 ` bug#62635: " Liliana Marie Prikler
2023-05-16 5:12 ` [bug#62635] [PATCH v3 1/3] gnu: geary: Fix failing build Juliana Sims
2023-05-16 5:12 ` [bug#62635] [PATCH v3 2/3] gnu: geary: Use g-expressions Juliana Sims
2023-05-16 5:13 ` [bug#62635] [PATCH v3 3/3] gnu: geary: Remove redundant native-inputs Juliana Sims
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=IPJQUR.XBL6DDIT12572@incana.org \
--to=juli@incana.org \
--cc=62635@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.org \
/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).