From: Leo Famulari <leo@famulari.name>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Our git just broke
Date: Sat, 13 Aug 2016 09:07:29 -0400 [thread overview]
Message-ID: <20160813130729.GA13976@jasmine> (raw)
In-Reply-To: <e04d6242-e40c-f5a4-4e71-df637145f11c@uq.edu.au>
On Sat, Aug 13, 2016 at 10:41:59PM +1000, Ben Woodcroft wrote:
> Hi,
>
> I cannot currently build git on the master branch. I bisected and got to
> this commit. I had a quick look but couldn't see what the problem was. The
> new package builds fine. Can someone take a look please?
>
>
> b3885778e8e438e8526a8ee9e96072fd00f5cae5 is the first bad commit
> commit b3885778e8e438e8526a8ee9e96072fd00f5cae5
> Author: ng0 <ng0@we.make.ritual.n0.is>
> Date: Wed Aug 10 10:04:29 2016 +0000
>
> gnu: Add stagit.
>
> * gnu/packages/version-control.scm (stagit): New variable.
>
> Signed-off-by: Leo Famulari <leo@famulari.name>
Oops! I've reverted the commit.
The variable expat is defined twice. We need to change
version-control.scm to use a license prefix rather than selecting
licenses.
ng0, will you update version-control.scm to use a license prefix and
re-send an updated stagit patch?
next prev parent reply other threads:[~2016-08-13 13:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 12:41 Our git just broke Ben Woodcroft
2016-08-13 13:07 ` Leo Famulari [this message]
2016-08-13 13:23 ` Vincent Legoll
2016-08-13 13:32 ` Ben Woodcroft
2016-08-13 15:33 ` ng0
2016-08-13 23:11 ` Leo Famulari
2016-08-13 15:36 ` ng0
2016-08-13 23:11 ` Leo Famulari
2016-08-14 2:46 ` Eric Bavier
2016-08-14 18:24 ` Our git just broke [PATCH]: gnu: Add stagit, adjust version-control.scm ng0
2016-08-17 11:38 ` ng0
2016-08-13 17:28 ` Our git just broke Pjotr Prins
2016-08-14 4:28 ` Ben Woodcroft
2016-08-14 16:13 ` Leo Famulari
2016-08-15 1:08 ` Mark H Weaver
2016-08-15 11:23 ` Ben Woodcroft
2016-08-15 17:11 ` Leo Famulari
2016-08-15 18:04 ` Pjotr Prins
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=20160813130729.GA13976@jasmine \
--to=leo@famulari.name \
--cc=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.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).