You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
opam upgrade recently started failing for me. The proximate cause of this seems to have been ccache moving its default cache
directory from $HOME/.ccache to $HOME/.cache/ccache in its latest version (version 4.0), coupled with the sandbox.sh file installed by opam being out of date. This caused the sandboxing issue referred to here to arise.
In the end I resolved this by copying src/state/shellscripts/bwrap.sh from the latest opam tarball to $HOME/.opam/opam-init/hooks/sandbox.sh by hand: moving sandbox.sh and running opam init again does not appear to cause it to be refreshed automatically.
I suggest opam init should have an option available to it to refresh sandbox.sh. Better error reporting where a sandboxing error like this occurs would also be helpful, so that the user can more easily diagnose the cause.
The text was updated successfully, but these errors were encountered:
opam upgraderecently started failing for me. The proximate cause of this seems to have been ccache moving its default cachedirectory from $HOME/.ccache to $HOME/.cache/ccache in its latest version (version 4.0), coupled with the sandbox.sh file installed by opam being out of date. This caused the sandboxing issue referred to here to arise.
In the end I resolved this by copying src/state/shellscripts/bwrap.sh from the latest opam tarball to $HOME/.opam/opam-init/hooks/sandbox.sh by hand: moving sandbox.sh and running
opam initagain does not appear to cause it to be refreshed automatically.I suggest
opam initshould have an option available to it to refresh sandbox.sh. Better error reporting where a sandboxing error like this occurs would also be helpful, so that the user can more easily diagnose the cause.The text was updated successfully, but these errors were encountered: