Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Stack docker does not work with GHC HEAD (`ghc-pkg dump` format change) #1509
I've made a docker image of the optimised release build of GHC HEAD (which I intend to trigger/push nightly builds of) but it sadly doesn't work with stack. It seems that
Steps to reproduce:
The version of stack I'm running:
I'm on OS X running with docker-machine and docker 1.9.1. The command fails with this output:
From what I can tell, the command
In HEAD they now look like this:
It seems weird to me that this change has happened, especially since the hashes have also disappeared from the package ids. Is this a GHC bug or expected behaviour? Either way it would be good to fix this so people can play with nightlies (really to try the new kind equality stuff) - this is the last part preventing me making an automated build for GHC HEAD nightlies that's easy to use. It will also present itself as a problem when GHC 8.0 is released in the coming month or so.
referenced this issue
Dec 13, 2015
@CRogers Yes, that would be my guess. Stack should assume whitespace separated.
The hash removal was intentional (hashes in general haven't gone away from IPIDs, but I removed them from GHC's boot libraries, on the basis that they are the "one and only" libraries of this type for any GHC install), but maybe I can add it back.
added a commit
Dec 14, 2015
In 9ee38c8 I've made stack accept space separated build dependencies, and it now passes the test added in @CRogers PR. Leaving this ticket open for the discussion of the other change to the
I lean towards preferring consistency as well. However, if we can be reasonably sure that anything that expects an IPID will also accept these boot library versions, then I suppose it's not necessary. For example, here's how
GHC 8.0 definitely will accept
I looked at the code in GHC, though, and it seems like the reason we don't make some sort of random hash is partially because GHC's build system may still have some (latent) bugs in it. I'll try to take a closer look.