From: ng0 <ng0@we.make.ritual.n0.is>
To: Harry Prevor <habs@sdf.org>, 24220@debbugs.gnu.org
Subject: bug#24220: "failed to unpack source code" on guix pull
Date: Sun, 14 Aug 2016 14:27:27 +0000 [thread overview]
Message-ID: <87popbfmsw.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <567c8b751b63d6851aeab6afa91ca878@sdf.org>
Harry Prevor <habs@sdf.org> writes:
> Hi ng0,
>
> On 2016-08-14 04:59, ng0 wrote:
>> This was caused by a patch I sent which was applied on master.
>> Guix error messages could be more natural, as for me the error output I
>> got seemed just verbose and I decided it was okay to send this in. The
>> commit has since then be reverted and I will send in an updated patch.
>>
>> Simpler explanation: a license I added was already inherited by another
>> loaded module, this caused some "hick up" and make broke (while it did
>> not break locally on my side).
>>
>>>> P.S. I'm not subscribed to bug-guix, so please CC me in any
>>>> responses to this thread!
>>
>> Can you please close this bug (see the message you got from
>> debbugs.gnu.org with instructions) when it is done.
>> For me master builds again, so I assume this bug is done?
>
> I can do that once I get a message (I haven't yet), but for me I'm still
> having the guix pull issue. Are there any steps that need to be done by
> me to ensure I'm getting the latest master branch with the fix? If not,
> when would the fix be applied?
>
> Thanks,
>
> ---
> Harry Prevor
>
>
>
Curious, I thought the normal behavior of debbugs was to send
instructions with how bugs are closed etc. Sometimes there's a very long
delay (I noticed 1-2 days delay with bugs being opened).
Can you describe your problem more in detail and how to reproduce? I've
just run a `guix pull` and the build succeeded for amd64.
--
♥Ⓐ ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-08-14 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 22:05 bug#24220: "failed to unpack source code" on guix pull Harry Prevor
2016-08-14 5:27 ` Pjotr Prins
2016-08-14 8:59 ` ng0
2016-08-14 13:02 ` Harry Prevor
2016-08-14 14:27 ` ng0 [this message]
2016-08-14 16:21 ` Leo Famulari
2016-08-22 15:49 ` Harry Prevor
2019-02-13 0:29 ` 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=87popbfmsw.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=24220@debbugs.gnu.org \
--cc=habs@sdf.org \
/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).