New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haskel: error build package insert-ordered-containers and uri-bytestring #53067

Open
Izorkin opened this Issue Dec 30, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@Izorkin
Copy link
Contributor

Izorkin commented Dec 30, 2018

Issue description

Error build package insert-ordered-containers

Steps to reproduce

nixpkgs rev 6b1a429
nix build -f ~/nixpkgs haskellPackages.insert-ordered-containers

builder for '/nix/store/c2vl0b6r6icrv2cnhzhsa9pzp2s1m7ry-insert-ordered-containers-0.2.1.0.drv' failed with exit code 1; last 10 log lines:
    die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:950:20 in Cabal-2.4.0.1:Distribution.Simple.Configure
    configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:460:12 in Cabal-2.4.0.1:Distribution.Simple.Configure
    configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:596:20 in Cabal-2.4.0.1:Distribution.Simple
    confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:67:5 in Cabal-2.4.0.1:Distribution.Simple.UserHooks
    configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:178:19 in Cabal-2.4.0.1:Distribution.Simple
    defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:115:27 in Cabal-2.4.0.1:Distribution.Simple
    defaultMain, called at Setup.hs:2:8 in main:Main
  Setup: Encountered missing dependencies:
  tasty >=0.10.1.2 && <1.2

nix build -f ~/nixpkgs haskellPackages.uri-bytestring

builder for '/nix/store/7awm3all33j3gxn3xhlm13ykb90l1nkf-uri-bytestring-0.3.2.1.drv' failed with exit code 1; last 10 log lines:
          at test/URI/ByteString/Arbitrary.hs:(39,1)-(41,27)
      • In the second argument of ‘($)’, namely ‘SOP.hcpure p arbitrary’
        In the second argument of ‘($)’, namely
          ‘SOP.apInjs_POP $ SOP.hcpure p arbitrary’
        In the first argument of ‘oneof’, namely
          ‘(map SOP.hsequence $ SOP.apInjs_POP $ SOP.hcpure p arbitrary)’
     |
  42 | sopArbitrary' = oneof (map SOP.hsequence $ SOP.apInjs_POP $ SOP.hcpure p arbitrary)
     |                                                             ^^^^^^^^^^^^^^^^^^^^^^
  [2 of 4] Compiling URI.ByteStringQQTests ( test/URI/ByteStringQQTests.hs, dist/build/test/test-tmp/URI/ByteStringQQTests.o )
[0 built (1 failed)]
error: build of '/nix/store/7awm3all33j3gxn3xhlm13ykb90l1nkf-uri-bytestring-0.3.2.1.drv' failed

Technical details

  • system: "x86_64-linux"
  • host os: Linux 4.19.12, NixOS, 19.03pre164359.60739e534d9 (Koi)
  • multi-user?: yes
  • sandbox: yes
  • version: nix-env (Nix) 2.2pre6526_9f99d624
  • channels(root): "nixos-19.03pre164359.60739e534d9"
  • nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

@Izorkin Izorkin changed the title haskel: error build package insert-ordered-containers haskel: error build package insert-ordered-containers and uri-bytestring Dec 30, 2018

@Izorkin

This comment has been minimized.

Copy link
Contributor

Izorkin commented Dec 31, 2018

In nixpkg rev de0de8 normal build, in rev cb5bc3 - error.

@bb010g

This comment has been minimized.

Copy link
Contributor

bb010g commented Jan 6, 2019

insert-ordered-containers is fixed in phadej/insert-ordered-containers@73fdf9c , but the new metadata revision hasn't been made on Hackage yet.

@wkral

This comment has been minimized.

Copy link

wkral commented Jan 14, 2019

I thought this would have been addressed with 2534ddd and I was waiting for a new build of master but it didn't seem to resolve the issue. Looking at the commit with more context it seems to only be for pandoc.

Currently this is still broken after a successful build of trunk-combined. Would this same approach work with insert-order-containers it doesn't seem like there is any movement to fix the package on hackage.

With a break before the end of the year and this issue I can't been able to update my machine for more than a month, is there a way I can fix it locally as well? With an overlay or something like that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment