#41779: hs-aeson @0.6.2.1_1 configure failure: command execution failed -----------------------+---------------------- Reporter: markus@… | Owner: cal@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: hs-aeson | -----------------------+---------------------- Changes (by cal@…): * owner: macports-tickets@… => cal@… * status: new => assigned Comment: I think `hs-attoparsec` and its dependencies might need a revbump. Can you attach the output of `ghc-pkg check` and `ghc-pkg list`, please? -- Ticket URL: <https://trac.macports.org/ticket/41779#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#41779: hs-aeson @0.6.2.1_1 configure failure: command execution failed -----------------------+-------------------- Reporter: markus@… | Owner: cal@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: fixed | Keywords: Port: hs-aeson | -----------------------+-------------------- Changes (by cal@…): * status: assigned => closed * resolution: => fixed Comment: For each package that you have twice in the output of `ghc-pkg list`, please run `sudo ghc-pkg unregister $name-$version` where `$name` is the package name and `$version` is the older version of the package. In your case that's - highlighting-kate-0.5.3.9 and - binary-0.5.1.1 These problems are caused by a bug in the haskell PortGroup which previously wouldn't successfully remove packages from the list while uninstalling them from MacPorts when there were still other (haskell) packages using them. This bug has since been fixed, but I cannot automatically fix that for packages that have been broken by it. I've revbumped hs-attoparsec and its dependencies in r114665. That might or might not have been necessary, but since I have done lots of incorrect updates for haskell ports some unneeded revbumps probably don't hurt anyone to come back to a consistent state (especially since the buildbots will produce packages for those). I think this problem should be fixed. Please re-open if you still encounter it. -- Ticket URL: <https://trac.macports.org/ticket/41779#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X