Re: Our git just broke [PATCH]: gnu: Add stagit, adjust version-control.scm.

2016-08-17 Thread ng0
Hi, can someone comment on this patch if there are changes I need to make? ng0 writes: > Leo Famulari 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 q

Re: Our git just broke

2016-08-15 Thread Pjotr Prins
On Mon, Aug 15, 2016 at 01:11:50PM -0400, Leo Famulari wrote: > On Mon, Aug 15, 2016 at 09:23:44PM +1000, Ben Woodcroft wrote: > > > Leo Famulari writes: > > > > Regarding GnuTLS, I assume Pjotr is describing the failure of the > > > > "name-constraints" test [0]. > > > I'm a little confused. AIU

Re: Our git just broke

2016-08-15 Thread Leo Famulari
On Mon, Aug 15, 2016 at 09:23:44PM +1000, Ben Woodcroft wrote: > > Leo Famulari writes: > > > Regarding GnuTLS, I assume Pjotr is describing the failure of the > > > "name-constraints" test [0]. > I'm a little confused. AIUI, this was fixed in 3.5.2 which is a part of > current master and 0.11.0.

Re: Our git just broke

2016-08-15 Thread Ben Woodcroft
On 15/08/16 11:08, Mark H Weaver wrote: Leo Famulari writes: On Sun, Aug 14, 2016 at 02:28:43PM +1000, Ben Woodcroft wrote: On 14/08/16 03:28, Pjotr Prins wrote: Also gnutls does not pass it's tests on my system, nor does subversion. Both gnutls and subversion are substituted for me on cu

Re: Our git just broke

2016-08-14 Thread Mark H Weaver
Leo Famulari writes: > On Sun, Aug 14, 2016 at 02:28:43PM +1000, Ben Woodcroft wrote: >> On 14/08/16 03:28, Pjotr Prins wrote: >> > Also gnutls does not pass it's tests on my system, nor does >> > subversion. >> Both gnutls and subversion are substituted for me on current master >> (891284), indi

Re: Our git just broke [PATCH]: gnu: Add stagit, adjust version-control.scm.

2016-08-14 Thread ng0
Leo Famulari 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

Re: Our git just broke

2016-08-14 Thread Leo Famulari
On Sun, Aug 14, 2016 at 02:28:43PM +1000, Ben Woodcroft wrote: > On 14/08/16 03:28, Pjotr Prins wrote: > > Also gnutls does not pass it's tests on my system, nor does > > subversion. > Both gnutls and subversion are substituted for me on current master > (891284), indicating they built without issu

Re: Our git just broke

2016-08-13 Thread Ben Woodcroft
Hi Pjotr, On 14/08/16 03:28, Pjotr Prins wrote: [..] Also gnutls does not pass it's tests on my system, nor does subversion. Both gnutls and subversion are substituted for me on current master (891284), indicating they built without issue OK on hydra. Does it still not work for you? Thanks,

Re: Our git just broke

2016-08-13 Thread Eric Bavier
On Sat, 13 Aug 2016 19:11:35 -0400 Leo Famulari wrote: > On Sat, Aug 13, 2016 at 03:36:06PM +, ng0 wrote: > > On the subject of stagit, this is a software written by the cloud of > > people named "2f30", associated with the ideas of suckless. Should this > > go into suckless.scm and not versi

Re: Our git just broke

2016-08-13 Thread Leo Famulari
On Sat, Aug 13, 2016 at 03:36:06PM +, ng0 wrote: > On the subject of stagit, this is a software written by the cloud of > people named "2f30", associated with the ideas of suckless. Should this > go into suckless.scm and not version-control? The logical place for me > is version-control, the se

Re: Our git just broke

2016-08-13 Thread Leo Famulari
On Sat, Aug 13, 2016 at 03:33:29PM +, ng0 wrote: > 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. Correct,

Re: Our git just broke

2016-08-13 Thread Pjotr Prins
Thanks Ben, I thought it was just me banging my head against the wall. Also gnutls does not pass it's tests on my system, nor does subversion. I went back in time to July 22nd. Building fine there. Pj. On Sat, Aug 13, 2016 at 10:41:59PM +1000, Ben Woodcroft wrote: > Hi, > > I cannot currently

Re: Our git just broke

2016-08-13 Thread ng0
Leo Famulari 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

Re: Our git just broke

2016-08-13 Thread ng0
Hi, Leo Famulari 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 t

Re: Our git just broke

2016-08-13 Thread Ben Woodcroft
On 13/08/16 23:07, Leo Famulari wrote: 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 ta

Re: Our git just broke

2016-08-13 Thread Vincent Legoll
> The variable expat is defined twice. Would it be possible to get more meaningful error messages ? -- Vincent Legoll

Re: Our git just broke

2016-08-13 Thread Leo Famulari
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? > > > b3885778