> Hi,
>
> Am Freitag, den 18.10.2013, 09:10 +0100 schrieb Iain Lane:
>> I stopped because Louis told me to.
>>
>> Should I upload?
>
> I believe there was a misunderstanding.
>
> @Louis, from what I understood Iain has cherry-picked patches for alex
> compatibility from upstream that are working, a
Hi,
Am Freitag, den 18.10.2013, 09:10 +0100 schrieb Iain Lane:
> I stopped because Louis told me to.
>
> Should I upload?
I believe there was a misunderstanding.
@Louis, from what I understood Iain has cherry-picked patches for alex
compatibility from upstream that are working, and is ready to
On Fri, Oct 18, 2013 at 09:30:31AM +0200, Joachim Breitner wrote:
> Hi,
>
> Am Dienstag, den 15.10.2013, 10:57 +0100 schrieb Iain Lane:
> > On Tue, Oct 15, 2013 at 11:15:59AM +0200, Joachim Breitner wrote:
> > > Hi Iain
> > >
> > > Am Dienstag, den 15.10.2013, 11:00 +0200 schrieb Joachim Breitner
Hi,
Am Dienstag, den 15.10.2013, 10:57 +0100 schrieb Iain Lane:
> On Tue, Oct 15, 2013 at 11:15:59AM +0200, Joachim Breitner wrote:
> > Hi Iain
> >
> > Am Dienstag, den 15.10.2013, 11:00 +0200 schrieb Joachim Breitner:
> > > I’m uploading yi right now. According to
> > > http://jenkins.debian.ne
Hi,
Seems like we did the same changes at the same time. Please upload your
master branch.
Le 15. 10. 13 12:16, Iain Lane a écrit :
>
> What do you want to do?
>
I think we can only make guesses.
darcs log --to-patch="Support for Alex 3.1" --from-tag=2.3.2.1
on Agda upstream is near a hundred
Also, it seems like dist/build/Agda/Syntax/Parser/{Lexer,Parser}.hs are
version-controlled, although they seem to be generated from
src/full/Agda/Syntax/{Lexer.x,Parser.y}. Any reason for that? Introduced
by fe6fa12e5cb63847e1d67f8eceaa40a8af806de8.
Louis
--
When I grow up,
I will run a Tor n
On Tue, Oct 15, 2013 at 12:14:34PM +0200, Louis Bettens wrote:
> Hi,
>
> Le 15. 10. 13 11:57, Iain Lane a écrit :
> >Doing. I only noticed that one, but it also needs a cherry-picked
> >upstream patch for Alex 3.1.
> >
> The patch called “Support for Alex 3.1” seems to do. It just bumps
> the depe
Hi,
Le 15. 10. 13 11:57, Iain Lane a écrit :
Doing. I only noticed that one, but it also needs a cherry-picked
upstream patch for Alex 3.1.
The patch called “Support for Alex 3.1” seems to do. It just bumps the
dependency. It passes pdebuild.
There's a lot of patches in the agda repo between
On Tue, Oct 15, 2013 at 11:15:59AM +0200, Joachim Breitner wrote:
> Hi Iain
>
> Am Dienstag, den 15.10.2013, 11:00 +0200 schrieb Joachim Breitner:
> > I’m uploading yi right now. According to
> > http://jenkins.debian.net/job/chroot-installation_sid_install_haskell/143/
> > only Agda remains to
Le 15. 10. 13 11:19, Louis Bettens a écrit :
Hi,
Yes. There was a discrepency between Agda.cabal and debian/control, the
former said hashable up to 1.3 and the latter to 1.2. It's fixed. I'm
trying with pbuilder.
Louis
Oh, I see. Agda is on a git repo. I had an old checkout in my
~/pkg/haskell
Le 15. 10. 13 11:00, Joachim Breitner a écrit :
Hi,
I’m uploading yi right now. According to
http://jenkins.debian.net/job/chroot-installation_sid_install_haskell/143/ only
Agda remains to be fixed. There is no new Agda version, so we need to patch it.
Louis, can you see if Agda builds if you
Hi Iain
Am Dienstag, den 15.10.2013, 11:00 +0200 schrieb Joachim Breitner:
> I’m uploading yi right now. According to
> http://jenkins.debian.net/job/chroot-installation_sid_install_haskell/143/
> only Agda remains to be fixed. There is no new Agda version, so we need to
> patch it. Louis, can
Hi,
I’m uploading yi right now. According to
http://jenkins.debian.net/job/chroot-installation_sid_install_haskell/143/ only
Agda remains to be fixed. There is no new Agda version, so we need to patch it.
Louis, can you see if Agda builds if you allow the newer hashable?
Thanks,
Joachim
--
J
13 matches
Mail list logo
