Hi Andres,<br><br>Thanks for the reply! Note that I get this message even running 'cabal install' a second time after changing nothing. Is that scenario an example of what you mean by a "potentially dangerous cabal invocation"? I've been unable to avoid this error message by any other means that (a) 'ghc-pkg unregister <package>' or (b) '--force-reinstall'. So far, '--solver=modular' hasn't helped. So I'm hoping for something less aggressive. In particular, in case nothing has changed, I want 'cabal install' to succeed (exit code 0) so that my automated build & install & release processes will continue rather than get stopped.<br>
<br>Regards, - Conal<br><br>On Sat, Feb 4, 2012 at 9:51 PM, Andres Löh <span dir="ltr"><<a href="mailto:andres.loeh@googlemail.com">andres.loeh@googlemail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Conal.<br>
<div class="im"><br>
On Sun, Feb 5, 2012 at 12:36 AM, Conal Elliott <<a href="mailto:conal@conal.net">conal@conal.net</a>> wrote:<br>
> Since upgrading to 7.4.1, if I 'cabal install' successfully and then 'cabal<br>
> install' a second time without first doing a 'ghc-pkg unregister<br>
> <package-name>', I get the following complaint:<br>
><br>
</div>> [...]<br>
<br>
The warning is intended to prevent you from breaking your system<br>
without knowing that you know that you're running a potentially<br>
dangerous cabal invocation.<br>
<br>
The --force-reinstalls flag should always make it build. If it<br>
doesn't, it's a bug.<br>
<br>
In addition, I'm planning to make the warning a little bit less<br>
aggressive before the release.<br>
<div class="im"><br>
> The only path I've found so far that's willing to rebuild or even say<br>
> nothing needs rebuilding (when nothing does) is to 'ghc-pkg unregister' and<br>
> then 'cabal install' again. I'm getting the same behavior on Red Hat 5 and<br>
> Mac OS 10.6.8, both compiled from sources.<br>
<br>
</div>I'd be surprised if the OS matters. But as I said, I've not yet<br>
encountered a situation where it wouldn't build given<br>
--force-reinstalls.<br>
<br>
Cheers,<br>
Andres<br>
</blockquote></div><br>