Hello Marc, > Hi guys, > > Then I > ran WPKG again expecting that the checks will be met and the upgrade > commands wouldn't be run. But the debug output states that the checks > were not executed and the upgrade commands were run immediately leading > to the same error again. > > Is this the intended behaviour? Shouldn't the checks be run every time > to avoid situations like these? This is correct and documented (but i admit a little unexpected) behaviour. I wrote a patch some time ago that makes this configurable - but since there was no reaction, I assumed everybody was okay with the original behaviour. anyways, here's the bug: http://bugzilla.wpkg.org/show_bug.cgi?id=180 once you applied the patch to wpkg.js you can use "checkpolicy=always" in the package definition to force checks on update. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20100422/c4b782c6/attachment.html> |