[wpkg-users] [Bug 257] XML error when using templates
http://bugzilla.wpkg.org/show_bug.cgi?id=257 --- Comment #6 from Rainer Meier r.me...@wpkg.org --- I have added some more changes and fixes in order to restore query functionality (host information was lost when reading wpkg.xml due to XML transform apply). @Stefan: Would you mind performing some more extensive tests and let me know whether it's better or worse than before? ;) Also I ask Falko to perform some tests on his use-case. Actually I did test the XSLT listed here already and it worked fine for me. But this is just one single test case... Changes in 1.2.1-RC48: FIX: Fixed invalid regular expression in host matching (within hosts.xml) would exit WPKG. Now a warning about invalid expression is printed. FIX: Fixed lost host information in settings (wpkg.xml) due to applied XML transforms. Bug was introduced in transforms processing added due to request in bug 257. Thanks to Stefan Pendl for reporting. NEW: Using correct name space in settings (wpkg.xml) written locally. NEW: Added proper processing information to settings (wpkg.xml). br, Rainer -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 257] XML error when using templates
http://bugzilla.wpkg.org/show_bug.cgi?id=257 Rainer Meier r.me...@wpkg.org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Comment #7 from Rainer Meier r.me...@wpkg.org --- I have added some more changes and fixes in order to restore query functionality (host information was lost when reading wpkg.xml due to XML transform apply). @Stefan: Would you mind performing some more extensive tests and let me know whether it's better or worse than before? ;) Also I ask Falko to perform some tests on his use-case. Actually I did test the XSLT listed here already and it worked fine for me. But this is just one single test case... Changes in 1.2.1-RC48: FIX: Fixed invalid regular expression in host matching (within hosts.xml) would exit WPKG. Now a warning about invalid expression is printed. FIX: Fixed lost host information in settings (wpkg.xml) due to applied XML transforms. Bug was introduced in transforms processing added due to request in bug 257. Thanks to Stefan Pendl for reporting. NEW: Using correct name space in settings (wpkg.xml) written locally. NEW: Added proper processing information to settings (wpkg.xml). br, Rainer -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 257] XML error when using templates
http://bugzilla.wpkg.org/show_bug.cgi?id=257 --- Comment #9 from Rainer Meier r.me...@wpkg.org --- So if I understand you properly the errors you discovered were referring to broken packages and not related to any WPKG bug. So it helped you to fix your packages. Please let me know if you discover any further issues. But I am sure you will :) Thank you! -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 257] XML error when using templates
http://bugzilla.wpkg.org/show_bug.cgi?id=257 --- Comment #10 from Rainer Meier r.me...@wpkg.org --- Just noticed. The error message contains a typo. Fixed in 1.2.1-RC49. No functional changes. FIX: Fixed minor typo in error message about invalid XML structure loaded. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] Order of package removals and install/upgrades
Hello all, I'm currently deploying Flash 10.x via WPKG but I now want to deploy Flash 11 (this is to Win7 Pro machines). My question is, if I make a new xml package file with a new name of flash11 but give it the same priority number as my flash10 xml file and then comment out the flash10 name from my profiles.xml (forcing flash 10 to be removed), will flash10 be removed _before_ flash11 is installed, does WPKG remove a package first _then_ look for new installations/upgrades of packages with the same priority? Hope this makes sense :) Thanks Chris - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Order of package removals and install/upgrades
Am Mittwoch, 23. November 2011, 21:04:07 schrieb C. Mortimer: Hello all, I'm currently deploying Flash 10.x via WPKG but I now want to deploy Flash 11 (this is to Win7 Pro machines). My question is, if I make a new xml package file with a new name of flash11 but give it the same priority number as my flash10 xml file and then comment out the flash10 name from my profiles.xml (forcing flash 10 to be removed), will flash10 be removed _before_ flash11 is installed, does WPKG remove a package first _then_ look for new installations/upgrades of packages with the same priority? Removals happen first, before anything new is installed. The exception being upgrades to packages scheduled for removal and then maybe (?) upgrades to their dependencies. If you change the package's name and remove flash10 from the profile, flash11 will stay out of the way until flash10 is gone. Apart from that, the flash installer is fine with just installing over an older version. So instead you could just bumb the package's revision and adapt the commands to version 11 instead of adding an unrelated (from WPKG's perspective) new package. Priority is not involved here and in general, I'd recommend using dependencies instead. Priorities (absolute package order) are basically a kludge to work around missing explicit dependency specifications (relative package order). Hope this makes sense :) Guess so :) Cheers, Malte - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Order of package removals and install/upgrades
Hello Malte, Thanks for your reply. All makes sense apart from 'The exception being upgrades to packages scheduled for removal and then maybe (?) upgrades to their dependencies.' sorry, not sure I follow this bit. Do you mean that if a package has been removed from profiles.xml and that package has also been edited to upgrade it, the upgrade will happen first, then it will be removed? Many thanks Chris --Original Message-- From: Malte Starostik To: wpkg-users@lists.wpkg.org Cc: Chris Mortimer Subject: Re: [wpkg-users] Order of package removals and install/upgrades Sent: 23 Nov 2011 8:17 PM Am Mittwoch, 23. November 2011, 21:04:07 schrieb C. Mortimer: Hello all, I'm currently deploying Flash 10.x via WPKG but I now want to deploy Flash 11 (this is to Win7 Pro machines). My question is, if I make a new xml package file with a new name of flash11 but give it the same priority number as my flash10 xml file and then comment out the flash10 name from my profiles.xml (forcing flash 10 to be removed), will flash10 be removed _before_ flash11 is installed, does WPKG remove a package first _then_ look for new installations/upgrades of packages with the same priority? Removals happen first, before anything new is installed. The exception being upgrades to packages scheduled for removal and then maybe (?) upgrades to their dependencies. If you change the package's name and remove flash10 from the profile, flash11 will stay out of the way until flash10 is gone. Apart from that, the flash installer is fine with just installing over an older version. So instead you could just bumb the package's revision and adapt the commands to version 11 instead of adding an unrelated (from WPKG's perspective) new package. Priority is not involved here and in general, I'd recommend using dependencies instead. Priorities (absolute package order) are basically a kludge to work around missing explicit dependency specifications (relative package order). Hope this makes sense :) Guess so :) Cheers, Malte - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Order of package removals and install/upgrades
Hi Chris, On 23.11.2011 22:09, Chris Mortimer wrote: Thanks for your reply. All makes sense apart from 'The exception being upgrades to packages scheduled for removal and then maybe (?) upgrades to their dependencies.' sorry, not sure I follow this bit. Do you mean that if a package has been removed from profiles.xml and that package has also been edited to upgrade it, the upgrade will happen first, then it will be removed? Yes, exactly this is the case. WPKG has a feature I call upgrade-before-remove. It was introduced to help package admins to fix broken packages easily. So if you made a mistake, let's say your flash10 package installed to clients does not correctly uninstall (maybe you just forgot to specify correct remove commands) then you don't have to worry. Just fix up your flash10 package on server side, bump the revision number and remove it from the profile. WPKG will then first upgrade flash10 to the latest available revision to assure that the latest/fixed package is applied to the system. Then WPKG performs the remove. WPKG will still first perform all removes before performing any installation. But as you see in some exceptional cases (client runs outdated version of a package to be removed) an upgrade will take place right before the remove. Hope this makes any sense to you ;) br, Rainer - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Order of package removals and install/upgrades
Hello Chris, Am Mittwoch, 23. November 2011, 22:09:42 schrieb Chris Mortimer: Hello Malte, Thanks for your reply. All makes sense apart from 'The exception being upgrades to packages scheduled for removal and then maybe (?) upgrades to their dependencies.' sorry, not sure I follow this bit. Do you mean that if a package has been removed from profiles.xml and that package has also been edited to upgrade it, the upgrade will happen first, then it will be removed? Exactly. There has been quite some discussion about this feature in the past and it can be disabled with /noUpgradeBeforeRemove. The rationale behind this feature is that this way the admin gets a chance to fix e.g. broken remove commands by bumping the revision which ensures the package is up to date locally before running its remove commands. In fact, to only fix removal, you could publish an upgraded revision with no upgrade commands at all, so the upgrade will merely feed the updated removal instructions into the client's local database. HTH, Malte - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Delayed sevice start
In message 2023083018.gc3...@sv.lnf.it Marco Gaiarin g...@sv.lnf.it wrote: Mandi! John Danks In chel di` si favelave... WPKG Client has a few settings you might try. I haven't experimented with logon delay, but it's there under Logon Settings / Execution mode. Consider also: http://support.microsoft.com/default.aspx?scid=kb;en-us;305293 I am only too aware of that, and in the domain always ensure it is set in Group policy to wait for the network. However XP Home edition can't join a domain, and I haven't found an equivalent registry setting to make it start the wireless before logging in. The problem is not that the wireless is slow to start - you can leave the computer at the login window for an hour, and the wireless still hasn't started. It waits for someone to login before it tries to connect. -- Alan Adams, from Northamptonshire a...@adamshome.org.uk http://www.nckc.org.uk/ - wpkg-users mailing list archives http://lists.wpkg.org/pipermail/wpkg-users/ ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
