From: zimoun <zimon.toutoune@gmail.com>
To: Christopher Howard <christopher@librehacker.com>
Cc: 46158-done@debbugs.gnu.org, 46132-done@debbugs.gnu.org
Subject: bug#46132: bug#46158: qucs-s build failure: cairocffi python2 issue
Date: Thu, 11 Mar 2021 02:03:10 +0100 [thread overview]
Message-ID: <86sg52a4dt.fsf@gmail.com> (raw)
In-Reply-To: <9924570c0c4a91edd97e58f7d499671504b6d1c0.camel@librehacker.com>
On Wed, 10 Mar 2021 at 15:48, Christopher Howard <christopher@librehacker.com> wrote:
> I was able to build qucs a week or two ago, but didn't report it. I
> think you can close this bug report. Thank you.
Thanks, so closing.
prev parent reply other threads:[~2021-03-11 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 18:17 bug#46158: qucs-s build failure: cairocffi python2 issue Christopher Howard
2021-01-28 22:05 ` Leo Famulari
2021-03-11 0:27 ` zimoun
2021-03-11 0:48 ` bug#46132: " Christopher Howard
2021-03-11 1:03 ` zimoun [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=86sg52a4dt.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=46132-done@debbugs.gnu.org \
--cc=46158-done@debbugs.gnu.org \
--cc=christopher@librehacker.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 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).