I redid the update step and this time everything installed. Reboot
brings the machine to FCS Solaris 11 for SPARC and now the pkg install
of gcc-45 seems to be going along just fine. I will report any further
issues.
Thanks much.
Steve C.
On 10/02/12 11:51, Shawn Walker wrote:
On 10/02/12 02:00, Steve Christensen wrote:
OK, I ran the
> pkg update -v --accept --be-name=s11-fcs
and after maybe eight hours, it ended with
x11/xlock
0.5.11,5.11-0.151:20101026T201453Z ->
0.5.11,5.11-0.175.0.0.0.0.1215:20110927T130052Z
x11/xmag
1.0.3,5.11-0.151:20101026T201455Z ->
1.0.4,5.11-0.175.0.0.0.0.1215:20110927T130107Z
x11/xvidtune
1.0.2,5.11-0.151:20101026T201502Z ->
1.0.2,5.11-0.175.0.0.0.0.1215:20110927T130200Z
DOWNLOAD PKGS FILES XFER (MB)
Completed 1079/1079 81689/81688 1323.0/1323.0
I'm assuming you've elided some of the package versions that changed? If
so, yes, that looks right.
Expected 81688 files, received 81689 files instead.
Expected 1387250415 bytes, received 1387250435 bytes instead.
pkg: An unexpected error happened while preparing for update:
Traceback (most recent call last):
File "/usr/bin/pkg", line 5954, in handle_errors
__ret = func(*args, **kwargs)
File "/usr/bin/pkg", line 5937, in main_func
pargs=pargs, **opts)
File "/usr/bin/pkg", line 2323, in update
reject_list=reject_pats, update_index=update_index)
File "/usr/bin/pkg", line 1576, in __api_op
ret_code = __api_prepare(_op, _api_inst, accept=_accept)
File "/usr/bin/pkg", line 1224, in __api_prepare
api_inst.prepare()
File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 2021,
in prepare
self._img.imageplan.preexecute()
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line
2842, in preexecute
self.__progtrack.download_done()
File "/usr/lib/python2.6/vendor-packages/pkg/client/progress.py", line
252, in download_done
(self.dl_goal_nfiles, self.dl_cur_nfiles)
AssertionError: Expected 81688 files but got 81689
pkg: This is an internal error in pkg(5) version 630e1ffc7a19. Please
log a
Service Request about this issue including the information above and this
message.
My fault, my system, or a bug? Or don't worry about it?
A bug, but not one that exists anymore (this particular part of progress
tracking has been completely rewritten), and I can't recall ever seeing
this particular failure case.
You should be able to simply run the update again; since the download
content should be cached, it should work fine now.
-Shawn
_______________________________________________
pkg-discuss mailing list
pkg-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
