Build #3 for hopenpgp-tools-0.21.3
Package | hopenpgp-tools-0.21.3 |
---|
Install | DependencyFailed hopenpgp-tools-0.21.3 |
---|---|
Docs | NotTried |
Tests | NotTried |
Time submitted | 2019-01-19 15:41:26.530760641 UTC |
---|---|
Compiler | ghc-8.6.3 |
OS | linux |
Arch | x86_64 |
Dependencies | aeson-1.4.2.0, array-0.5.3.0, attoparsec-0.13.2.2, base-4.12.0.0, binary-0.8.6.0, binary-conduit-1.3.1, bytestring-0.10.8.2, conduit-1.3.1, conduit-extra-1.3.0, containers-0.6.0.1, crypto-pubkey-0.2.8, directory-1.3.3.0, errors-2.3.0, fgl-5.7.0.1, graphviz-2999.20.0.3, hOpenPGP-2.7.4.1, ixset-typed-0.4.0.1, lens-4.17, monad-loops-0.4.3, optparse-applicative-0.14.3.0, prettyprinter-1.2.1, prettyprinter-convert-ansi-wl-pprint-1.1, resourcet-1.2.2, text-1.2.3.1, time-1.8.0.2, transformers-0.5.5.0, unordered-containers-0.2.10.0, yaml-0.11.0.0, aeson-1.4.2.0, base-4.12.0.0, base16-bytestring-0.1.1.6, binary-0.8.6.0, binary-conduit-1.3.1, bytestring-0.10.8.2, conduit-1.3.1, conduit-extra-1.3.0, containers-0.6.0.1, crypto-pubkey-0.2.8, cryptohash-0.11.9, directory-1.3.3.0, errors-2.3.0, hOpenPGP-2.7.4.1, http-client-0.6.1, http-client-tls-0.3.5.3, http-types-0.12.2, ixset-typed-0.4.0.1, lens-4.17, monad-loops-0.4.3, openpgp-asciiarmor-0.1.1, optparse-applicative-0.14.3.0, prettyprinter-1.2.1, prettyprinter-ansi-terminal-1.1.1.2, prettyprinter-convert-ansi-wl-pprint-1.1, text-1.2.3.1, time-1.8.0.2, time-locale-compat-0.1.1.5, transformers-0.5.5.0, yaml-0.11.0.0, aeson-1.4.2.0, array-0.5.3.0, base-4.12.0.0, binary-0.8.6.0, binary-conduit-1.3.1, bytestring-0.10.8.2, conduit-1.3.1, conduit-extra-1.3.0, errors-2.3.0, hOpenPGP-2.7.4.1, lens-4.17, monad-loops-0.4.3, openpgp-asciiarmor-0.1.1, optparse-applicative-0.14.3.0, prettyprinter-1.2.1, prettyprinter-convert-ansi-wl-pprint-1.1, text-1.2.3.1, transformers-0.5.5.0, yaml-0.11.0.0 |
Flags | none |
Code Coverage
No Code Coverage was submitted for this report.
Build log
[view raw]
Warning: The install command is a part of the legacy v1 style of cabal usage. Please switch to using either the new project style and the new-install command or the legacy v1-install alias as new-style projects will become the default in the next version of cabal-install. Please file a bug if you cannot replicate a working v1- use case with the new-style commands. For more information, see: https://wiki.haskell.org/Cabal/NewBuild Resolving dependencies... Starting StateVar-1.1.1.1 Starting base16-bytestring-0.1.1.6 Starting base-orphans-0.8 Starting base-compat-0.10.5 Building StateVar-1.1.1.1 Building base16-bytestring-0.1.1.6 Building base-orphans-0.8 Building base-compat-0.10.5 Completed base-orphans-0.8 Starting base64-bytestring-1.0.0.2 Completed base16-bytestring-0.1.1.6 Starting basement-0.0.8 Completed StateVar-1.1.1.1 Starting blaze-builder-0.4.1.0 Building base64-bytestring-1.0.0.2 Building basement-0.0.8 Building blaze-builder-0.4.1.0 Completed base64-bytestring-1.0.0.2 Starting byteable-0.1.1 Building byteable-0.1.1 Completed blaze-builder-0.4.1.0 Starting bzlib-0.5.0.5 Completed base-compat-0.10.5 Starting cabal-doctest-1.0.6 Completed byteable-0.1.1 Starting call-stack-0.1.0 Failed to install bzlib-0.5.0.5 Build log ( /home/builder/.cabal/logs/ghc-8.6.3/bzlib-0.5.0.5-8TMEZNLRAIMKxXCedq0SW1.log ): cabal: Entering directory '/tmp/cabal-tmp-26669/bzlib-0.5.0.5' Configuring bzlib-0.5.0.5... cabal: Missing dependency on a foreign library: * Missing (or bad) header file: bzlib.h * Missing (or bad) C library: bz2 This problem can usually be solved by installing the system package that provides this library (you may need the "-dev" version). If the library is already installed but in a non-standard location then you can use the flags --extra-include-dirs= and --extra-lib-dirs= to specify where it is.If the library file does exist, it may contain errors that are caught by the C compiler at the preprocessing stage. In this case you can re-run configure with the verbosity flag -v3 to see the error messages. If the header file does exist, it may contain errors that are caught by the C compiler at the preprocessing stage. In this case you can re-run configure with the verbosity flag -v3 to see the error messages. cabal: Leaving directory '/tmp/cabal-tmp-26669/bzlib-0.5.0.5' Starting cereal-0.5.8.0 Building cabal-doctest-1.0.6 Building call-stack-0.1.0 Building cereal-0.5.8.0 Completed call-stack-0.1.0 Completed cabal-doctest-1.0.6 Completed cereal-0.5.8.0 Completed basement-0.0.8 cabal: Error: some packages failed to install: bzlib-0.5.0.5-8TMEZNLRAIMKxXCedq0SW1 failed during the configure step. The exception was: ExitFailure 1 hOpenPGP-2.7.4.1-FEmSfJotMmCDNGCU2ATVf5 depends on hOpenPGP-2.7.4.1 which failed to install. hopenpgp-tools-0.21.3-Lv3s5KVyfoV9KND567m42i depends on hopenpgp-tools-0.21.3 which failed to install.
Test log
No test log was submitted for this report.