Re: Our git just broke

[ng0]

Hi,

Leo Famulari <address@hidden> writes:

> 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 <address@hidden>
>> 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 <address@hidden>
>
> 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?

It is reverted and has no immediate priority as I read.
I can do so tomorrow or later today. Sorry that my commit broke it, I
thought the message about twice defined license was just verbose. Now I
know this can break the make.
-- 
♥Ⓐ  ng0
For non-prism friendly talk find me on http://www.psyced.org