On 27.02.2010 19:43, Vasaris wrote: >> On 27.02.2010 14:14, Tomasz Chmielewski wrote: >>> No, one folder is enough. >>> If WPKG Client is already installed, wpkg.js will just skip its >>> installation. >> >> Just as an additional clarification: Make sure WPKG client is assigned to each >> profile - else WPKG will try to remove the WPKG client installation which was >> run manually before. >> >> The reason is that during manual /install:wpkg operation WPKG writes the "wpkg" >> package to the local wpkg.xml file. If it's not part of the profile later on, >> then WPKG will try to remove this package and execute its uninstall commands. >> However if you do it right and just include "wpkg" in your profiles, then WPKG >> will simply know that this package is already installed and will not re-install >> it on first run via WPKG client. > > Heh, now I have a joke. After unsuccessfull first deployment of 1.3.9 client, I have tried 1.3.14 beta (I finaly was able to download it via 3rd provider). It did not worked. Everything was failed here: http://bugzilla.wpkg.org/show_bug.cgi?id=182. > > And now, back to the 1.3.9 client, suddenly it works OK. From my POV, I have changed nothing in config. I am happy, but at a loss. I do not know, if other clients will follow this good habit, I will have to check this out. Could you do one more test? If you upgrade to 1.3.14, does it suddenly stop working? -- Tomasz Chmielewski http://wpkg.org |