
Hi everyone, I was getting ready to prepare the final 8.6.1 release tarballs when Herbert pointed out that the testsuite of his cryptohash-sha256 package currently segfaults. This appears to be a rather serious, non-deterministic regression. I've opened #15544 to track this and will delay the final 8.6.1 release until this is resolved. Cheers, - Ben

I think the release should include this fix to haddock. Will that happen?
https://github.com/haskell/haddock/pull/905
Matt
On Mon, Aug 20, 2018 at 10:33 PM Ben Gamari
Hi everyone,
I was getting ready to prepare the final 8.6.1 release tarballs when Herbert pointed out that the testsuite of his cryptohash-sha256 package currently segfaults. This appears to be a rather serious, non-deterministic regression. I've opened #15544 to track this and will delay the final 8.6.1 release until this is resolved.
Cheers,
- Ben _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Matthew Pickering
I think the release should include this fix to haddock. Will that happen?
Yes, we can make that happen.

Am Mo., 20. Aug. 2018 um 23:40 Uhr schrieb Matthew Pickering < matthewtpickering@gmail.com>:
I think the release should include this fix to haddock. Will that happen?
Will the release contain the fix https://github.com/haskell/haddock/pull/893 for the issue https://github.com/haskell/haddock/issues/462 too? Without that fix, Haddock is basically unusable for lots of packages under the memory restrictions of Travis CI. Cheers, S.

Sven Panne
Am Mo., 20. Aug. 2018 um 23:40 Uhr schrieb Matthew Pickering < matthewtpickering@gmail.com>:
I think the release should include this fix to haddock. Will that happen?
Will the release contain the fix
https://github.com/haskell/haddock/pull/893
for the issue
https://github.com/haskell/haddock/issues/462
too? Without that fix, Haddock is basically unusable for lots of packages under the memory restrictions of Travis CI.
Alex, do you have any objection to merging these? Cheers, - Ben

Hi Ben,
I talked to Alex about these today:
* PR #905 has been merged.
* PR #893 requires the merge of https://phabricator.haskell.org/D5003.
Apart from that there were no objections.
Cheers,
Simon
Am Di., 21. Aug. 2018 um 17:09 Uhr schrieb Ben Gamari : Sven Panne Am Mo., 20. Aug. 2018 um 23:40 Uhr schrieb Matthew Pickering <
matthewtpickering@gmail.com>: I think the release should include this fix to haddock. Will that
happen? Will the release contain the fix https://github.com/haskell/haddock/pull/893 for the issue https://github.com/haskell/haddock/issues/462 too? Without that fix, Haddock is basically unusable for lots of packages
under the memory restrictions of Travis CI. Alex, do you have any objection to merging these? Cheers, - Ben
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Am Di., 21. Aug. 2018 um 17:14 Uhr schrieb Simon Jakobi via ghc-devs < ghc-devs@haskell.org>:
I talked to Alex about these today:
* PR #905 has been merged. * PR #893 requires the merge of https://phabricator.haskell.org/D5003. Apart from that there were no objections.
Just another Haddock-related question: Is the fix in https://github.com/haskell/haddock/issues/837 included in 8.6.1, too? Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1...

Is the fix in https://github.com/haskell/haddock/issues/837 included in 8.6.1, too?
The fix is both on ghc's ghc-8.6 branch and on haddock's ghc-8.6 branch. Currently I'm a bit confused about exactly which Haddock release/snapshot
will be shipped with 8.6.1...
I'm not sure either. CC'ing Herbert.
Am Do., 23. Aug. 2018 um 11:07 Uhr schrieb Sven Panne
Am Di., 21. Aug. 2018 um 17:14 Uhr schrieb Simon Jakobi via ghc-devs < ghc-devs@haskell.org>:
I talked to Alex about these today:
* PR #905 has been merged. * PR #893 requires the merge of https://phabricator.haskell.org/D5003. Apart from that there were no objections.
Just another Haddock-related question: Is the fix in https://github.com/haskell/haddock/issues/837 included in 8.6.1, too? Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1...

As far as I can tell, these changes aren’t yet in GHC 8.6: * https://github.com/haskell/haddock/pull/905 https://github.com/haskell/haddock/pull/905 is on Haddock’s 8.6 branch, but GHC 8.6 hasn’t yet bumped the submodule. * https://github.com/haskell/haddock/pull/893 https://github.com/haskell/haddock/pull/893 is not even yet on Haddock’s 8.6 branch. Note that this one requires matching GHC-side changes to be cherry-picked too. I think the idea is loosely for GHC 8.6 to ship whatever is in the Haddock `ghc-8.6` branch.
On Aug 23, 2018, at 6:46 AM, Simon Jakobi via ghc-devs
wrote: Is the fix in https://github.com/haskell/haddock/issues/837 https://github.com/haskell/haddock/issues/837 included in 8.6.1, too?
The fix is both on ghc's ghc-8.6 branch and on haddock's ghc-8.6 branch.
Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1...
I'm not sure either. CC'ing Herbert.
Am Do., 23. Aug. 2018 um 11:07 Uhr schrieb Sven Panne
mailto:svenpanne@gmail.com>: Am Di., 21. Aug. 2018 um 17:14 Uhr schrieb Simon Jakobi via ghc-devs mailto:ghc-devs@haskell.org>: I talked to Alex about these today: * PR #905 has been merged. * PR #893 requires the merge of https://phabricator.haskell.org/D5003 https://phabricator.haskell.org/D5003. Apart from that there were no objections.
Just another Haddock-related question: Is the fix in https://github.com/haskell/haddock/issues/837 https://github.com/haskell/haddock/issues/837 included in 8.6.1, too? Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1... _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

Hello!
I'm having some problem related to plugin recompilation:
https://ghc.haskell.org/trac/ghc/ticket/15564
This prevents inline-java from building with ghc-6.8.1. Perhaps it is
worth checking before the release.
Best,
Facundo
On Thu, Aug 23, 2018 at 11:29 AM Alec Theriault
As far as I can tell, these changes aren’t yet in GHC 8.6:
* https://github.com/haskell/haddock/pull/905 is on Haddock’s 8.6 branch, but GHC 8.6 hasn’t yet bumped the submodule. * https://github.com/haskell/haddock/pull/893 is not even yet on Haddock’s 8.6 branch. Note that this one requires matching GHC-side changes to be cherry-picked too.
I think the idea is loosely for GHC 8.6 to ship whatever is in the Haddock `ghc-8.6` branch.
On Aug 23, 2018, at 6:46 AM, Simon Jakobi via ghc-devs
wrote: Is the fix in https://github.com/haskell/haddock/issues/837 included in 8.6.1, too?
The fix is both on ghc's ghc-8.6 branch and on haddock's ghc-8.6 branch.
Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1...
I'm not sure either. CC'ing Herbert.
Am Do., 23. Aug. 2018 um 11:07 Uhr schrieb Sven Panne
: Am Di., 21. Aug. 2018 um 17:14 Uhr schrieb Simon Jakobi via ghc-devs
: I talked to Alex about these today:
* PR #905 has been merged. * PR #893 requires the merge of https://phabricator.haskell.org/D5003. Apart from that there were no objections.
Just another Haddock-related question: Is the fix in https://github.com/haskell/haddock/issues/837 included in 8.6.1, too? Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1...
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

I just replied on the ticket. I think the issue is fixed by D5048.
Matt
On Fri, Aug 24, 2018 at 9:05 PM Facundo Domínguez
Hello!
I'm having some problem related to plugin recompilation: https://ghc.haskell.org/trac/ghc/ticket/15564
This prevents inline-java from building with ghc-6.8.1. Perhaps it is worth checking before the release.
Best, Facundo
On Thu, Aug 23, 2018 at 11:29 AM Alec Theriault
wrote: As far as I can tell, these changes aren’t yet in GHC 8.6:
* https://github.com/haskell/haddock/pull/905 is on Haddock’s 8.6 branch, but GHC 8.6 hasn’t yet bumped the submodule. * https://github.com/haskell/haddock/pull/893 is not even yet on Haddock’s 8.6 branch. Note that this one requires matching GHC-side changes to be cherry-picked too.
I think the idea is loosely for GHC 8.6 to ship whatever is in the Haddock `ghc-8.6` branch.
On Aug 23, 2018, at 6:46 AM, Simon Jakobi via ghc-devs
wrote: Is the fix in https://github.com/haskell/haddock/issues/837 included in 8.6.1, too?
The fix is both on ghc's ghc-8.6 branch and on haddock's ghc-8.6 branch.
Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1...
I'm not sure either. CC'ing Herbert.
Am Do., 23. Aug. 2018 um 11:07 Uhr schrieb Sven Panne
: Am Di., 21. Aug. 2018 um 17:14 Uhr schrieb Simon Jakobi via ghc-devs
: I talked to Alex about these today:
* PR #905 has been merged. * PR #893 requires the merge of https://phabricator.haskell.org/D5003. Apart from that there were no objections.
Just another Haddock-related question: Is the fix in https://github.com/haskell/haddock/issues/837 included in 8.6.1, too? Currently I'm a bit confused about exactly which Haddock release/snapshot will be shipped with 8.6.1...
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs

greetings, this topic was discussed on mailing list before[1], but I don't think anything came of it. It was also recently discussed on the cabal issue tracker [2] but alas the cabal maintainers have so far not shown interest in resolving the issue. And while cabal-install caused this problem to surface for many users, the fact that package environment files unnecessarily add state to ghc behaviour holds regardless of cabal behaviour, and must be addressed on ghc's end. I expand on this reasoning in a blog post [3]. Thanks for considering. -- lennart [1] https://mail.haskell.org/pipermail/haskell-cafe/2018-May/129076.html [2] https://github.com/haskell/cabal/issues/4542 [3] https://hexagoxel.de/postsforpublish/posts/2018-08-25-ghc-pkg-env-misfeature...
participants (8)
-
Alec Theriault
-
Ben Gamari
-
Ben Gamari
-
Facundo Domínguez
-
lennart spitzner
-
Matthew Pickering
-
Simon Jakobi
-
Sven Panne