all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: Hendursaga <hendursaga@aol.com>
Cc: 66037@debbugs.gnu.org
Subject: [bug#66037] [PATCH 1/3] gnu: libosmium: Update to 2.19.0.
Date: Sat, 16 Sep 2023 22:34:50 +0100	[thread overview]
Message-ID: <fff24d06-34d1-485d-b0dd-80b048a83da5@makinata.eu> (raw)
In-Reply-To: <f85dedc376e37da64d4cdfd9ead82001d257b30b.1694898378.git.hendursaga@aol.com>

Hi Hendursaga,

On 2023-09-16 22:21, Hendursaga via Guix-patches via wrote:
> +    (native-inputs (list doxygen graphviz))

Perhaps you could use graphviz-minimal instead?


-- 
Furthermore, I consider that nonfree software must be eradicated.

Cheers,
Bruno.





  reply	other threads:[~2023-09-16 21:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1694898378.git.hendursaga.ref@aol.com>
2023-09-16 21:18 ` [bug#66037] [PATCH 0/3] Update libosmium and dependents Hendursaga via Guix-patches via
2023-09-16 21:21   ` [bug#66037] [PATCH 1/3] gnu: libosmium: Update to 2.19.0 Hendursaga via Guix-patches via
2023-09-16 21:34     ` Bruno Victal [this message]
2023-09-17 19:38       ` [bug#66037] [PATCH v2 0/3] Update libosmium and dependents Hendursaga via Guix-patches via
2023-09-17 19:39         ` [bug#66037] [PATCH v2 1/3] gnu: libosmium: Update to 2.19.0 Hendursaga via Guix-patches via
2023-09-17 19:39         ` [bug#66037] [PATCH v2 2/3] gnu: osm2pgsql: Update to 1.9.2 Hendursaga via Guix-patches via
2023-09-17 19:39         ` [bug#66037] [PATCH v2 3/3] gnu: osmium-tool: Update to 1.15.0 Hendursaga via Guix-patches via
2023-09-21 15:39         ` bug#66037: [PATCH v2 0/3] Update libosmium and dependents Guillaume Le Vaillant
2023-09-16 21:21   ` [bug#66037] [PATCH 2/3] gnu: osm2pgsql: Update to 1.9.2 Hendursaga via Guix-patches via
2023-09-16 21:21   ` [bug#66037] [PATCH 3/3] gnu: osmium-tool: Update to 1.15.0 Hendursaga via Guix-patches via

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fff24d06-34d1-485d-b0dd-80b048a83da5@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=66037@debbugs.gnu.org \
    --cc=hendursaga@aol.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.