From: ng0 <ng0@we.make.ritual.n0.is>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 24670@debbugs.gnu.org, dian_cecht@zoho.com
Subject: bug#24670: Unexpected EOF reading a line (from guix pull) [forward]
Date: Fri, 14 Oct 2016 14:33:30 +0000 [thread overview]
Message-ID: <87y41rvw3p.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <idjwphbvzmd.fsf@bimsb-sys02.mdc-berlin.net>
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> ng0 <ng0@we.make.ritual.n0.is> writes:
>
>> It is impossible to reproduce exactly the system which caused the bug,
>> but I will try to reproduce it as good as you can with Gentoo.
>
> I chuckled a little. It’s ironic because with Guix we actually can
> reproduce systems with relative ease :)
Food for thought: right now, yes. But what happens when more people
start to use Guix, with modified versions of packages or even versions
of packages which are no longer in master? Do we simply ignore the
request for support with "sorry, this is not in master we can not
reproduce it"?
The systems following master go towards being reproducible, but custom
systems (and that's what Gentoo is) will appear and they will make this
harder, a new challenge to face maybe.
next prev parent reply other threads:[~2016-10-14 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 22:34 bug#24670: Unexpected EOF reading a line (from guix pull) dian_cecht
2016-10-11 23:07 ` ng0
[not found] ` <20161012070258.GA12645@khaalida>
2016-10-13 8:09 ` bug#24670: Unexpected EOF reading a line (from guix pull) [forward] ng0
2016-10-13 11:25 ` Ricardo Wurmus
2016-10-13 12:44 ` ng0
2016-10-14 0:10 ` ng0
2016-10-14 10:08 ` Ricardo Wurmus
2016-10-14 11:22 ` ng0
2016-10-14 11:53 ` Ricardo Wurmus
2016-10-14 12:21 ` ng0
2016-10-14 13:17 ` Ricardo Wurmus
2016-10-14 14:21 ` ng0
2016-10-14 14:33 ` ng0 [this message]
2016-10-14 14:37 ` Ricardo Wurmus
2016-10-14 0:21 ` bug#24670: bug #24670: Unexpected EOF reading a line (from guix pull) dian_cecht
2016-10-14 10:06 ` Ricardo Wurmus
2016-10-16 4:57 ` dian_cecht
2016-10-16 10:23 ` Ricardo Wurmus
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=87y41rvw3p.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=24670@debbugs.gnu.org \
--cc=dian_cecht@zoho.com \
--cc=ricardo.wurmus@mdc-berlin.de \
/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).