unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Catonano <catonano@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: 25884@debbugs.gnu.org
Subject: bug#25884: build fails
Date: Mon, 27 Feb 2017 15:02:21 +0100	[thread overview]
Message-ID: <CAJ98PDyoqEWn6UEgYFEb3VU=fXmYq2OegRDQC5F+vaSN46B7tQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ98PDwU9PwP18unq6ZzsQrmCP4SyP8PfXVwLj4_qn55Rngqaw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

Ok,

I'm ashamed to admit that I was just confused, master builds perfectly

This bug can be closed.

Sorry for the fuss

Alex, I apologize for abusing your time :-/


2017-02-27 11:08 GMT+01:00 Catonano <catonano@gmail.com>:

> Alex,
>
> thanks for taking time for this
>
> 2017-02-27 10:31 GMT+01:00 Alex Kost <alezost@gmail.com>:
>
>> Catonano (2017-02-27 00:04 +0100) wrote:
>>
>> > Guix master won't build
>> >
>> > I just pulled master and I'm at
>> > 5d79b1bf575139dba9b3f919c7cc7b7f0853a67c
>>
>> I have just built it successfully.
>
>
> It happens randomly. Sometimes it happens, sometimes it doesn't
>
>
>> Could you try "make clean-go"; if it
>> reports about unhandled .go files, remove them; then try "make" again.
>>
>
> I gave "make clean-go" and the result is attached.
>
> It doesn't seem to me there are unhandled .go files
>

[-- Attachment #2: Type: text/html, Size: 1847 bytes --]

  reply	other threads:[~2017-02-27 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 23:04 bug#25884: build fails Catonano
2017-02-27  9:31 ` Alex Kost
2017-02-27 10:08   ` Catonano
2017-02-27 14:02     ` Catonano [this message]
2017-02-27 20:17       ` Leo Famulari
2017-02-28 13:53       ` Alex Kost
2017-02-28 14:36         ` 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='CAJ98PDyoqEWn6UEgYFEb3VU=fXmYq2OegRDQC5F+vaSN46B7tQ@mail.gmail.com' \
    --to=catonano@gmail.com \
    --cc=25884@debbugs.gnu.org \
    --cc=alezost@gmail.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).