It also seems that having a disabled repo when the update process takes
places isn't such a hot idea:
pkg list resulted in:
~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/usr/bin/pkg", line 2813, in handle_errors
__ret = func(*args, **kwargs)
File "/usr/bin/pkg", line 2730, in main_func
img.find_root(mydir, provided_image_dir)
File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 259, in
find_root
progtrack=progtrack)
File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 356, in
__set_dirs
self.__check_image(progtrack=progtrack)
File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 363, in
__check_image
self.__upgrade_image(progtrack=progtrack)
File "/usr/lib/python2.4/vendor-packages/pkg/client/image.py", line 1601, in
__upgrade_image
if f.version != newest[f.pkg_name]:
KeyError: 'virtualbox/kernel'
pkg: This is an internal error. Please let the developers know about this
problem by filing a bug at http://defect.opensolaris.org and including the
above traceback and this message. The version of pkg(5) is '5c92c9d342ef'.
~~~~~~~~~~~~~~~~
Packagemanager crashed shortly after launch.
(Resolved by performing a rollback, enabling Extra, and reinstalling from gate)
--joanie
On Fri, 2009-09-11 at 05:53 -0500, Shawn Walker wrote:
> Shawn Walker wrote:
> > Some additional points of interest to be aware of:
>
> One additional note before I forget:
>
> The first time you run the new package client as a privileged user, the
> image upgrade process will happen. This can a few minutes depending on
> your system (about 40 seconds on my system). Once this process has
> happened though, all future operations should execute quickly.
>
> Cheers,
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
