From: Bruno Victal <mirai@makinata.eu>
To: bdju <bdju@tilde.team>
Cc: 61261-done@debbugs.gnu.org
Subject: bug#61261: obs-wlrobs build failure
Date: Mon, 13 Feb 2023 12:31:55 +0000 [thread overview]
Message-ID: <3135c8f3-5313-0048-4946-ffd960ccfdbf@makinata.eu> (raw)
In-Reply-To: <CQ9HKA6BPRQI.37KS3QHPFHOFS@masaki>
On 2023-02-04 04:15, bdju via Bug reports for GNU Guix wrote:
> guix (GNU Guix) c3e50c731d8c175133cae1869e445cbb7a3b4d6f
> log attached
This has been fixed with obs-wlrobs 1.1 update. (guix c3e50c731d8c175133cae1869e445cbb7a3b4d6f)
Cheers
Bruno
prev parent reply other threads:[~2023-02-13 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 4:15 bug#61261: obs-wlrobs build failure bdju via Bug reports for GNU Guix
2023-02-13 12:31 ` Bruno Victal [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=3135c8f3-5313-0048-4946-ffd960ccfdbf@makinata.eu \
--to=mirai@makinata.eu \
--cc=61261-done@debbugs.gnu.org \
--cc=bdju@tilde.team \
/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).