Monday, December 02, 2019

Re: ghc-pkg failure during bulk builds

On Mon, Dec 02, 2019 at 09:11:39PM +0100, Matthias Kilian wrote:
> Hi,
>
> today, naddy@ ran into this error (for devel/shellcheck, but this doesn't
> matter here):
>
> /usr/local/bin/ghc-pkg recache '--package-db=dist/package.conf.inplace'
> ===> Exiting devel/shellcheck,-lib with an error
> ghc-pkg: /usr/local/lib/ghc/package.conf.d/network-2.6.2.1.conf: openBinaryFile: does not exist (No such file or directory)
>
> I'm quite sure that this happened while dpb(1) was junking, removing
> unused packages, including hs-network, and that it's a double bug
> in ghc-pkg (it shouldn't look at the system-wide package db when
> run with --package-db=dist/package.conf.inplace, and it should do
> some kind of locking in case another ghc-pkg is running at the same
> time).
>
> So if you're doing bulk builds with dpb(1) and have a ports failing
> with an error message from ghc-pkg similar to the above one, please
> consider restarting the build of the failed port (by removing the
> corresponding dpb lock file) for now, unless it really starts to
> happen often.

If you're not going to fix this really soon, set DPB_PROPERTIES += nojunk
in ghc.port.mk

I don't give a damn whether it happens often or not.
It's going to require manual tinkering, and that's exactly the kind of
work-around nojunk is intended for.

No comments:

Post a Comment