From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 40410-done@debbugs.gnu.org
Subject: bug#40410: gnome-todo build failure
Date: Wed, 13 Jul 2022 10:02:19 -0400 [thread overview]
Message-ID: <8735f51578.fsf@gmail.com> (raw)
In-Reply-To: <20200403182456.015cb13e@scratchpost.org> (Danny Milosavljevic's message of "Fri, 3 Apr 2020 18:24:56 +0200")
Hi,
Danny Milosavljevic <dannym@scratchpost.org> writes:
> $ LC_ALL=C guix describe
> Generation 70 Apr 02 2020 13:27:19 (current)
> guix 451c38b
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 451c38b7d6017434a2a06646f1da6ef1e6ca4614
Our gnome-todo (version 41) builds fine on current master.
Closing.
Thanks for the report!
Maxim
prev parent reply other threads:[~2022-07-13 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 16:24 bug#40410: gnome-todo build failure Danny Milosavljevic
2022-07-13 14:02 ` Maxim Cournoyer [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=8735f51578.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=40410-done@debbugs.gnu.org \
--cc=dannym@scratchpost.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).