On 06/21/10 12:59 PM, Sean Scott wrote:
On 06/18/10 17:53, Shawn Walker wrote:
On 06/18/10 01:17 PM, Sean Scott wrote:
On 06/07/10 16:14, Richard Lowe wrote:
Sean Scott wrote:
Also we often want our "mtst" users to install versions of the
package
that are not putback to ON yet. How can a package that is built in
a dev
ws be installed? I have not found the magic combination of
options/paths. IPS does not have to use http does it?
For example how can a package that is available at this location be
installed on a target system? Must the publisher settings be
modified or
can the path be specified just for one install?
/net/hyper.sfbay/tank/ws/cy152378/clr/drop1/packages/sparc/nightly/repo.extra/pkg
The publisher settings must be modified.
OK, so what is the correct set of options to use to set the publisher
appropriately? All my attempts returned errors. I also was not sure
how much
of the path should be used. For example is the above path ok or
should it end
at "repo.extra", or "sparc", or something?
Unless you have fairly recent pkg5 bits, you'd need to run a depot
pointing toward that location (pkg.depotd -d
/net/hyper.sfbay/tank/ws/cy152378/clr/drop1/packages/sparc/nightly/repo.extra)
Recent pkg bits (I think build 140 and above?) support file:// URIs in
the client, and you should be able to specify
file:///net/hyper.sfbay/tank/ws/cy152378/clr/drop1/packages/sparc/nightly/repo.extra
as an package origin directly, though this may not be wise with NFS
paths, as the code somewhat assumes access to the filesystem to be
low-latency.
Thanks for the above information, I looked into setting the depot.d but
thought I'd try using file:// instead. It seems to work (with build_142
bits).
Now that I've managed to install an mtst pkg, I thought I would try to
uninstall it. But I've run into unexpected problems likely due to the
way mtst is being packaged. Not only does it not uninstall, the reason
is NOT true for mtst (though it does have a driver component). Also
reboot-needed should be false.
Is there a manual override to force it to uninstall? Perhaps the
filelist has system directories listed separately and that is an issue
wrt the "live image" message below?
r...@bur99-41:~# pkg uninstall -rv mtst
Solver: [ State: Initialized]
Timings: []
Maintained incorporations: None
Package version changes:
pkg://on-extra/system/fault-management/[email protected],5.11-0.141:20100525T181202Z
-> None
Actuators:
reboot-needed: true
pkg: Requested "uninstall" operation would affect files that cannot be
modified in live image.
Please retry this operation on an alternate boot environment.
I also tried to just install a pkg version over top of the existing one
but it is too smart for that. Any way to force an install?
There is (intentionally) no way to force an install or uninstall.
I was afraid of that :).
The gap in functionality here is that uninstall isn't yet smart enough
to create a new BE for you (or offer you that option) so that you can
uninstall this package. However, this gap is known and will be
resolved at a future date.
So for now, you need to create a new BE, uninstall the package from
it, and then restart to that BE:
beadm create newbe
beadm mount newbe /mnt
pkg -R /mnt uninstall mtst
bootadm update-archive -R /mnt
beadm unmount newbe
beadm activate newbe
Thanks for the above instructions, I don't even know what a BE is but I
ran the above on my system and everything seemed to work. Only issue is
that at the end the pkg is still on the system and I still can't
uninstall it.
Here's the output:
r...@bur99-41:/usr/platform/sun4v/include/sys# beadm create newbe
r...@bur99-41:/usr/platform/sun4v/include/sys# beadm mount newbe /mnt
r...@bur99-41:/usr/platform/sun4v/include/sys# pkg -R /mnt uninstall mtst
PHASE ACTIONS
Removal Phase 42/42
PHASE ITEMS
Reading Existing Index 8/8
Indexing Packages 1/1
r...@bur99-41:/usr/platform/sun4v/include/sys# bootadm update-archive -R
/mnt
updating /mnt//platform/sun4v/boot_archive
r...@bur99-41:/usr/platform/sun4v/include/sys# beadm unmount newbe
r...@bur99-41:/usr/platform/sun4v/include/sys# beadm activate newbe
Any ideas?
So you rebooted the system, did a 'pkg info mtst' and it said the
package was installed?
Cheers,
-Shawn
_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
