Timothy Sample writes:
> Hi Marius,
>
> Marius Bakke writes:
>
>> I appreciate the heads-up. Thanks again for taking on this task. The
>> branch LGTM.
>>
>> I've restarted the builds that you mentioned in another message. How is
>> the weather looking, do you think it's ready to merge? :-)
>
I can confirm that git-annex built locally so no complaints there.
Great job!
--
Efraim Flashner אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
Thanks Tim, Marius!
Good work! I am really happy about xmobar, it’s so much more stable now. I’ll
take a look at idris next time I get the chance.
- John
Hi Marius,
Marius Bakke writes:
> I appreciate the heads-up. Thanks again for taking on this task. The
> branch LGTM.
>
> I've restarted the builds that you mentioned in another message. How is
> the weather looking, do you think it's ready to merge? :-)
There are a few remaining issues, bu
Timothy Sample writes:
> Hi,
>
> Marius Bakke writes:
>
>> I've read some of the changes and they LGTM. If Cuirass is happy, I
>> think you can go ahead and merge the branch. \o/
>
> I just put everything together and rebased it all on master, fixing
> several typos as I did so. :) It seems
Hi again,
Timothy Sample writes:
> Marius Bakke writes:
>
>> I've read some of the changes and they LGTM. If Cuirass is happy, I
>> think you can go ahead and merge the branch. \o/
>
> I just put everything together and rebased it all on master, fixing
> several typos as I did so. :) It see
Hi,
Marius Bakke writes:
> I've read some of the changes and they LGTM. If Cuirass is happy, I
> think you can go ahead and merge the branch. \o/
I just put everything together and rebased it all on master, fixing
several typos as I did so. :) It seems that “ghc@8.6.5” has changed a
few day
Ah, ok makes sense!
Hi John,
John Soo writes:
> When we bump to Stackage 14 can issue 36653 be closed?
I think these changes should still be merged (with review and fixes).
Eventually Stackage LTS 15 will come out while we’re still on LTS 14.
At that point, we will have the same issue with the importer and linter
Hey everyone,
When we bump to Stackage 14 can issue 36653 be closed?
- John
Timothy Sample writes:
> Hi John,
>
> John Soo writes:
>
>> Xmobar builds properly with all the extensions but I haven't really given it
>> a spin. I did have to
>> add a few more packages, but I think they are reasonable.
>
> This is fantastic! Thanks so much for your help.
>
>> I think the
Hi John,
John Soo writes:
> Xmobar builds properly with all the extensions but I haven't really given it
> a spin. I did have to
> add a few more packages, but I think they are reasonable.
This is fantastic! Thanks so much for your help.
> I think the update to ghc after 8.4 will fix a segf
Hi Tim,
Xmobar builds properly with all the extensions but I haven't really given
it a spin. I did have to add a few more packages, but I think they are
reasonable.
I think the update to ghc after 8.4 will fix a segfault that i have been
experiencing :).
Here are my patches, is this the place t
Hi John,
John Soo writes:
> Thanks for putting in the work. I use xmobar with a few extra options:
> dbus, alsa and maybe one more. I can’t remember. I can try submitting
> a patch for it this week.
Hooray! If I fix “ngless” this will be pretty much ready to merge.
Then (pause while a short fa
Hi Tim,
Thanks for putting in the work. I use xmobar with a few extra options: dbus,
alsa and maybe one more. I can’t remember. I can try submitting a patch for it
this week.
My only question is how many options should we enable? We can try all.
Hi again,
Timothy Sample writes:
> However, I have a really weird problem. When I build “git-annex”, I
> build
>
> /gnu/store/5i2x293qn45dwg2rv6vy45s0r9jbnv8l-git-annex-7.20191024.drv
>
> and it succeeds. On the build farm, it’s
>
> /gnu/store/fj5kyjkblxzcxbs6di1kd29j6fpsjvgk-git-annex
Hello,
Timothy Sample writes:
> I have “xmonad”, “darcs”, “ghc-pandoc”, and “git-annex” all building
> (locally) on top of GHC 8.6, which means that we’re nearly there.
> Unfortunately, the mess is getting to be too much, so I plan to clean it
> up tomorrow and then push a new, cleaner version o
Hi all,
Timothy Sample writes:
>> Ricardo Wurmus writes:
>>
>>> Yes, you can take over wip-haskell-updates.
>
> Great! I’ve pushed a new branch with updated Haskell packages. It’s a
> little messy yet, but I want the build farm to help me find build
> problems before cleaning up too much. I
Hello,
Marius Bakke writes:
> Ricardo Wurmus writes:
>
>>> Ricardo, what do you think? Are we okay to take over
>>> wip-haskell-updates? Does a mega commit make sense or do you think
>>> that’s a bad idea?
>>
>> Yes, you can take over wip-haskell-updates.
Great! I’ve pushed a new branch wit
hat upgrading one package at a time. Hence, my rough plan is to
>> start by setting GHC 8.6 as the compiler for the build system, and then
>> run the refresh script with Stackage LTS 14. After that, I will push
>> the results to wip-haskell-updates and see how it goes.
>>
&g
ough plan is to
> start by setting GHC 8.6 as the compiler for the build system, and then
> run the refresh script with Stackage LTS 14. After that, I will push
> the results to wip-haskell-updates and see how it goes.
>
> Ricardo, what do you think? Are we okay to take over
> wip
is not ideal. I’m not sure how to
avoid that upgrading one package at a time. Hence, my rough plan is to
start by setting GHC 8.6 as the compiler for the build system, and then
run the refresh script with Stackage LTS 14. After that, I will push
the results to wip-haskell-updates and see how it go
22 matches
Mail list logo
