http://bugzilla.wpkg.org/show_bug.cgi?id=114 Summary: new parameter /force2 ? Product: WPKG Version: 1.0.1 Platform: PC OS/Version: Windows Server 2003 Status: NEW Severity: enhancement Priority: P2 Component: wpkg.js AssignedTo: mangoo at wpkg.org ReportedBy: jens.geile at mzbs.de QAContact: wpkg-users at lists.wpkg.org Hi, today I've run into some serious trouble when I upgraded some script on a couple of servers. I'm using wpkg.js 1.0.2 with the /force option always enabled. I've updated VLC 0.8.6e to 0.8.6f by increasing the revision from 0.8.6.5 to 0.8.6.6. The problem here is that /force DOES NOT honour the lokal wpkg.xml and instead of executing the upgrade command specified in vlc.xml it actually executed the install command which fails because of the broken VLC installer. :/ This could potentially happen with a lot of other scripts to and basically kills the whole installation as WPKG Service hangs there waiting for input but nothing happens. What I'd like to have is a /force2 (obviously it needs a more specific name) that does the same as /force but DOES honour the local wpkg.xml There are various reasons why I'm using the /force parameter in the first place and I'd really like to keep using it. But updating software is kinda impossible that way as you never know what will happen. :/ - jens -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |