Hello Kent,
Kent Tong wrote:
However, I'd like to deploy it to pilot group first. To avoid deploying to
all users,
I can't modify the existing package. It means I have to create a new
package.
If they have the same package id, then it will confuse wpkg, right? If they
have
different
Falko Trojahn-2 wrote:
- increase the revision number, so nothing on the existing clients is
changed, only the text file will be created/removed
- create a new, at least identical package, say mypackage2; assign it
to the test group, remove mypackage from the same group
Hi Falko,
Why not just create a new profile (called pilot or something) that
contains the package to test, and then in your hosts.xml add this new
profile to selected hosts that are to pilot the new package. You would still
have to create a separate package entry with a unique id of course, but
that's the
Hi,
first: please don't top post / full quote, thank you.
mscdex wrote:
Why not just create a new profile (called pilot or something) that
contains the package to test, and then in your hosts.xml add this new
profile to selected hosts that are to pilot the new package. You would
still have
Mandi! Kent Tong
In chel di` si favelave...
Is there any way to do it?
Apart what yust sayed, no.
If the 'testbed' are to little and phisically near you, normally i
modify the package but not the revision of, then i:
1) test the upgrade editing C:\WINDOWS\SYSTEM32\WPKG.XML and
subtracting
Hi all,
Thanks for all the suggestions! I think pinpointing is the way to go while
the
rest can serve as effective workaround for the moment. Going to file an
feature request...
-
--
Kent Tong
Wicket tutorials freely available at http://www.agileskills2.org/EWDW
Axis2 tutorials freely
http://bugzilla.wpkg.org/show_bug.cgi?id=131
Summary: pinpointing a package to a certain revision
Product: WPKG
Version: 0.9.10
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: enhancement
Priority: P2
Well, getting closer on this one. After a week off due to a server
changeover I've had a chance to play with this more in my test environment.
Getting hits on the log file now, but the edits still aren't applying.
I've tried as both SYSTEM and using Administrator Cridentials with the
same results.
Hi Christopher,
Christopher Leslie wrote:
Well, getting closer on this one. After a week off due to a server
changeover I've had a chance to play with this more in my test environment.
Getting hits on the log file now, but the edits still aren't applying.
I've tried as both SYSTEM and using
