From: Christopher Baines <mail@cbaines.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 61477@debbugs.gnu.org,
Philippe SWARTVAGHER <swartvagher@par.tuwien.ac.at>
Subject: [bug#61477] [PATCH] gnu: python-pygraphviz: Update to 1.10
Date: Wed, 15 Feb 2023 16:24:35 +0000 [thread overview]
Message-ID: <874jrmopwm.fsf@cbaines.net> (raw)
In-Reply-To: <86y1ozcflj.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> On Mon, 13 Feb 2023 at 14:03, Philippe SWARTVAGHER <swartvagher@par.tuwien.ac.at> wrote:
>> * gnu/packages/graphviz.scm (python-pygraphviz): Update to 1.10
> --^
> Missing dot
>
> Missing two ending dot: one commit headline and one ChangeLog.
>
> Well, QA says red:
>
> https://qa.guix.gnu.org/issue/61477
>
> but it appears to me unrelated. Chris, an idea?
Appears grey (unknown) to me currently, but it could have been red
previously.
I see one odd and unrelated thing here, the derivation for
openmv-openscenegraph is flapping around as there's a #<gexp in the
builder script. I've fixed that in
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=12127395dc55d9ea389a6dc619207c406725237e
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-02-15 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 13:03 [bug#61477] [PATCH] gnu: python-pygraphviz: Update to 1.10 Philippe SWARTVAGHER
2023-02-15 11:50 ` zimoun
2023-02-15 16:24 ` Christopher Baines [this message]
2023-02-16 11:31 ` zimoun
2023-02-17 16:47 ` Christopher Baines
2023-02-17 17:05 ` Simon Tournier
2023-02-15 16:19 ` Philippe SWARTVAGHER
2023-02-15 16:19 ` Philippe SWARTVAGHER
2023-02-20 13:05 ` bug#61477: " Nicolas Goaziou
2023-02-16 9:49 ` [bug#61477] " Simon Tournier
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=874jrmopwm.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=61477@debbugs.gnu.org \
--cc=swartvagher@par.tuwien.ac.at \
--cc=zimon.toutoune@gmail.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.