unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Guix-devel <guix-devel@gnu.org>, 29072@debbugs.gnu.org
Subject: bug#29072: The usability of Guix configurations
Date: Mon, 06 Nov 2017 18:26:26 -0500	[thread overview]
Message-ID: <86wp330z19.fsf__46522.7416404106$1510010838$gmane$org@gmail.com> (raw)
In-Reply-To: <20171106221621.GA2534@jasmine.lan>

Please note: these replies separated by topics in an effort to make the
threads more topical ...

On 11/06/2017 at 22:16 Leo Famulari writes:

> On Mon, Nov 06, 2017 at 03:12:11PM -0500, myglc2 wrote:
>> My system recently broke when I did an upgrade. I reported what I
>> thought was a bug (bug#29072) but it turned out that, because qemu
>> package code had been moved, my system configuration had become broken
>> ;-(
>>
>> Confronted with my situation, helpful developers said "The package code
>> was moved in commit xxx" (Leo) and "maybe you have a mistake in your
>> config (Efraim)."
>
> I'm sorry that my comment was not enough on its own!

Hey Leo,

Please understand that don't mean this as a complaint your reply, which
was helpful and I was very happy to receive.

I am just trying to step back and think about the bigger picture.

  parent reply	other threads:[~2017-11-06 23:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <868tfjw4is.fsf@gmail.com>
2017-11-06 22:16 ` bug#29072: The usability of Guix configurations Leo Famulari
     [not found] ` <20171106221621.GA2534@jasmine.lan>
2017-11-06 23:26   ` myglc2 [this message]
2017-11-07  1:56   ` myglc2
2017-11-07  2:30   ` myglc2
2017-11-07 10:23 ` Ludovic Courtès
2017-10-30 20:34 bug#29072: guix system: error: qemu-CVE-2017-7493.patch: patch not found myglc2
2017-11-06 20:12 ` bug#29072: The usability of Guix configurations myglc2

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='86wp330z19.fsf__46522.7416404106$1510010838$gmane$org@gmail.com' \
    --to=myglc2@gmail.com \
    --cc=29072@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).