unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Christopher Howard <christopher@librehacker.com>
Cc: 40542@debbugs.gnu.org
Subject: bug#40542: wip-hurm-vm build failure
Date: Thu, 25 Mar 2021 20:25:32 -0400	[thread overview]
Message-ID: <YF0p/Os9iFah5g6F@jasmine.lan> (raw)
In-Reply-To: <817c3ac2ee3b4b55b0eb7697e8eee00d5948d089.camel@librehacker.com>

On Thu, Mar 25, 2021 at 04:16:20PM -0800, Christopher Howard wrote:
> I think it would be fine to close this old bug-report now that the hurd
> image configuration is part of master. I just built a qcow2 today from
> gnu/systems/images/hurd and didn't have any trouble.

Great!

Anyone can close it by sending a message to
<40542-done@debbugs.gnu.org>.

And, there is no harm in closing a bug and then having to re-open it
later, so feel free :)




  reply	other threads:[~2021-03-26  0:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 15:53 bug#40542: wip-hurm-vm build failure Christopher Howard
2020-04-11 15:46 ` Jan Nieuwenhuizen
2020-04-13 16:59   ` Christopher Howard
2020-04-13 20:40     ` Ludovic Courtès
2020-04-13 21:02       ` Christopher Howard
2020-04-13 21:23         ` Ludovic Courtès
2020-04-13 21:46           ` Jan Nieuwenhuizen
2020-04-13 22:58           ` Christopher Howard
2020-04-14  5:46             ` Jan Nieuwenhuizen
2020-04-14 15:55               ` Christopher Howard
2020-04-14 17:12                 ` Jan Nieuwenhuizen
2020-04-14 16:57               ` Bengt Richter
2020-04-14 17:29                 ` Christopher Howard
2020-04-14 19:30                   ` Jan Nieuwenhuizen
2020-04-14 23:27                     ` Christopher Howard
2021-03-26  0:16 ` Christopher Howard
2021-03-26  0:25   ` Leo Famulari [this message]
2021-03-29 16:49     ` Leo Famulari

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=YF0p/Os9iFah5g6F@jasmine.lan \
    --to=leo@famulari.name \
    --cc=40542@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).