From: Mark H Weaver <mhw@netris.org>
To: Julian Graham <joolean@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: gzochi: Update to 0.10.
Date: Tue, 23 Aug 2016 13:44:52 -0400 [thread overview]
Message-ID: <87mvk34bxn.fsf@netris.org> (raw)
In-Reply-To: <CANdC_RAp2_=XsDwd10e6qrMyuOMnWuYE1JS9a9=faQ=76AknoQ@mail.gmail.com> (Julian Graham's message of "Tue, 23 Aug 2016 11:11:00 -0400")
Julian Graham <joolean@gmail.com> writes:
> On Tue, Aug 23, 2016 at 1:20 AM, Mark H Weaver <mhw@netris.org> wrote:
>> If you have 'guix' installed, you can run:
>>
>> guix build --system=i686-linux --keep-failed gzochi
>>
>> to reproduce the same build on your machine, and to leave the failed
>> build directory in /tmp/guix-build-* for further investigation.
>
> Neat! I'll give that a shot.
>
>
>> If you can fix the problem on i686, please let me know and I'd be glad
>> to test the same fix on armhf.
>>
>> What do you think?
>
> Will do. From a Guix perspective, what's better: A new gzochi release
> or a patch for Guix to apply against the 0.10 release?
Either one would be fine for Guix users. However, for the sake of
non-Guix users and other distros, I would suggest making a new release.
I think it's important that upstream software releases should be
reasonably portable whenever feasible, especially to important
architectures like i686 and armhf. What do you think?
Mark
next prev parent reply other threads:[~2016-08-23 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 15:20 [PATCH] gnu: gzochi: Update to 0.10 Julian Graham
2016-08-21 16:13 ` David Craven
2016-08-21 16:15 ` David Craven
2016-08-21 16:21 ` Andreas Enge
2016-08-21 17:00 ` David Craven
2016-08-21 21:06 ` Julian Graham
2016-08-21 21:20 ` David Craven
2016-08-21 21:28 ` Julian Graham
2016-08-21 23:52 ` David Craven
2016-08-22 4:24 ` Mark H Weaver
2016-08-22 12:59 ` Julian Graham
2016-08-23 5:20 ` Mark H Weaver
2016-08-23 15:11 ` Julian Graham
2016-08-23 17:44 ` Mark H Weaver [this message]
2016-08-25 15:12 ` Julian Graham
2016-08-25 19:22 ` Mark H Weaver
2016-09-01 1:41 ` Julian Graham
2016-09-03 20:43 ` Julian Graham
2016-09-04 11:06 ` David Craven
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvk34bxn.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=joolean@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.