haskell-distributed/cloud-haskell

Failing to build cloud-haskell

DebarghaG opened this issue · 4 comments

DebarghaG commented

Forgive me if I sound completely wonky; I'm new to this.

I'm trying to build with stack, and I get a plan construction failed error due to the build requiring an unattainable base version.
Can you please help? Is this, at all, due to [this]? (https://travis-ci.org/github/haskell-distributed/cloud-haskell)

Error: While constructing the build plan, the following exceptions were encountered:

In the dependencies for cloud-haskell-0.3.0.0:
    distributed-process-0.7.0 from stack configuration does not match ==0.6.*  (latest matching version is 0.6.6)
    network-transport-0.5.2 from stack configuration does not match ==0.4.*  (latest matching version is 0.4.4.0)
needed since cloud-haskell is a build target.

In the dependencies for distributed-process-async-0.2.3:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3.0 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.3 && <0.7  (latest matching version is 0.6.6)
    time-1.6.0.1 from stack configuration does not match >1.4 && <1.6  (latest matching version is 1.5.0.1)
needed since distributed-process-async is a build target.

In the dependencies for distributed-process-client-server-0.1.3.2:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3.0 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.2 && <0.7  (latest matching version is 0.6.6)
    time-1.6.0.1 from stack configuration does not match >1.4 && <1.6  (latest matching version is 1.5.0.1)
needed since distributed-process-client-server is a build target.

In the dependencies for distributed-process-demos-0.1.0.0(-use-azure):
    binary-0.8.3.0 from stack configuration does not match >=0.5 && <0.8  (latest matching version is 0.7.6.1)
needed since distributed-process-demos is a build target.

In the dependencies for distributed-process-execution-0.1.2.2:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3.0 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.3 && <0.7  (latest matching version is 0.6.6)
    time-1.6.0.1 from stack configuration does not match >1.4 && <1.6  (latest matching version is 1.5.0.1)
needed since distributed-process-execution is a build target.

In the dependencies for distributed-process-extras-0.2.1.2:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3.0 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.3 && <0.7  (latest matching version is 0.6.6)
    time-1.6.0.1 from stack configuration does not match >1.4 && <1.6  (latest matching version is 1.5.0.1)
needed since distributed-process-extras is a build target.

In the dependencies for distributed-process-registry-0.1.0.2:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3.0 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.3 && <0.7  (latest matching version is 0.6.6)
    time-1.6.0.1 from stack configuration does not match >1.4 && <1.6  (latest matching version is 1.5.0.1)
needed since distributed-process-registry is a build target.

In the dependencies for distributed-process-simplelocalnet-0.2.3.2:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.0 && <0.7  (latest matching version is 0.6.6)
    network-multicast-0.2.0 from stack configuration does not match >=0.0 && <0.2  (latest matching version is 0.1.2)
    network-transport-0.5.2 from stack configuration does not match >=0.4.1.0 && <0.5  (latest matching version is 0.4.4.0)
    network-transport-tcp-0.6.0 from stack configuration does not match >=0.4 && <0.6  (latest matching version is 0.5.1)
    transformers-0.5.2.0 from stack configuration does not match >=0.2 && <0.5  (latest matching version is 0.4.3.0)
needed since distributed-process-simplelocalnet is a build target.

In the dependencies for distributed-process-supervisor-0.1.3.2:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3.0 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.3 && <0.7  (latest matching version is 0.6.6)
    time-1.6.0.1 from stack configuration does not match >1.4 && <1.6  (latest matching version is 1.5.0.1)
needed since distributed-process-supervisor is a build target.

In the dependencies for distributed-process-task-0.1.2.2:
    binary-0.8.3.0 from stack configuration does not match >=0.6.3.0 && <0.8  (latest matching version is 0.7.6.1)
    distributed-process-0.7.0 from stack configuration does not match >=0.5.3 && <0.7  (latest matching version is 0.6.6)
    time-1.6.0.1 from stack configuration does not match >1.4 && <1.6  (latest matching version is 1.5.0.1)
needed since distributed-process-task is a build target.

In the dependencies for network-transport-benchmarks-0.0.0.1:
    base-4.9.1.0 from stack configuration does not match >=4.8 && <4.9  (latest matching version is 4.8.2.0)
needed since network-transport-benchmarks is a build target.

In the dependencies for network-transport-composed-0.2.0.1:
    network-transport-0.5.2 from stack configuration does not match >=0.4.0.0 && <0.5  (latest matching version is 0.4.4.0)
needed since network-transport-composed is a build target.

Some different approaches to resolving this:

  * Set 'allow-newer: true' in /home/d/.stack/config.yaml to ignore all version constraints and build anyway.

  * Build requires unattainable version of base. Since base is a part of GHC, you most likely need to use a different GHC version
    with the matching base.

Plan construction failed.
facundominguez commented

Hello! It may be necessary to update the package bounds in cloud-haskell.cabal. Note though, that this package is deprecated and it isn't being maintained.

  • 👍1
DebarghaG commented

Hi @facundominguez!

Thank you for taking time out to reply.

I understand that the package isn't being maintained, and I am somewhat new to the Haskell world.

I'm trying to code some distributed consensus protocols, and multiple web sources seemed to suggest this package was the best one to use to abstracting away networking functionality. Would you suggest any other package instead?

facundominguez commented

In that case, it is probably better to start with distributed-process and consider other packages as needed. Good luck!

  • ❤️1
DebarghaG commented

Great, thanks!