unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
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 12:21:28 +0000	[thread overview]
Message-ID: <87r37jp1dj.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <idjzim7w3i3.fsf@bimsb-sys02.mdc-berlin.net>

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:

> ng0 <ng0@we.make.ritual.n0.is> writes:
>
>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>>
>>> ng0 <ng0@we.make.ritual.n0.is> writes:
>>>
>>>> Without adding all of the off-ticket/list email I got: the failure is
>>>> very likely caused by /gnu/store being on a separate partition.
>>>
>>> What makes you say this is “very likely” the cause?
>>
>> I summarized the email I got offlist, I should've written this before I
>> started summarizing it.
>> 'Very likely' was not my own finding. This is a case of Gentoo/Guix I
>> can not debug.
>
> That’s okay, but I’d like to know what makes this the likely cause.  Has
> this behaviour been reproduced on another machine?
>
> As Guix has no problems with a store on a different partition I don’t
> know if it makes sense to keep this bug report open.  I cannot reproduce
> this on my machines.
>
> ~~ Ricardo
>

I'd like to keep it open. Right now I don't have the time to create a VM
to ~roughly~ reproduce this, I am busy with some upcoming personal
events. The bug ended up here, I offered bugs.gentoo.org (as far as I
know gentoo-overlays can use this shared infrastructure), my personal
email and our debbugs, so it makes sense to treat it as unsolved as long
as I wasn't able to reproduce it. However in addition to the "emerge
--info" I already got, I might need further info. Which guix ebuild was
used? "guix-bin" or "guix"?

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 will assume (the unlikely case) that there are no package specific
use-flags set and just copy more or less what the emerge --info spit
out.. but this will take time (going from stage3 to that particular
stage4...). Otherwise I would accept a stage4 of the system, but I don't
know how much developing on Gentoo experience dian_cecht has. Creating
your own stage4 is documented but it still requires uploading this
stage4 somewhere.
Furthermore, dian_cecht could you give me the exact chain of commands
you made up to the point of failure (or where you are right now)
starting from emerge guix? This would really help to reproduce the
problem. If you are not able to reconstruct this, please try to recall
what you did and describe it. All I've got so far is feedback on what's
broken not how it got to be broken.

Thanks,
ng0

  reply	other threads:[~2016-10-14 12:22 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 [this message]
2016-10-14 13:17                   ` Ricardo Wurmus
2016-10-14 14:21                     ` ng0
2016-10-14 14:33                     ` ng0
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=87r37jp1dj.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).