Thanks for the tip on pkg fix... I found I had a bunch of permission
issues, some on Gnome, some on other parts of the system, and I was
missing most of the license files...
I'm changing the permissions as suggested, maybe that helps some of the
frequent core dumps on plugin-container and the like.
Bryan
On 05/ 8/12 03:22 PM, Hans J. Albertsson wrote:
In the aftermath of my file system adventures when updating to 151a4,
I now have one mysterious "problem" left.
Well, it's not really a problem, just confusing and a little bit
mysterious to me, since I don't really know the IPS stuff that well.
Thing is I got to the point, doing lots of "pfexec pkg -R /otherBE fix
packagename", where my system reported no serious problems in pkg fix,
and
the package manager had a clean and consistent, and probably complete
view to present.
Then suddenly a bunch of python-related packages were updatable, and I
let updatemanager do that.
It set up a new BE, and after booting over to that one, I ran Package
Manager. I clicked around a bit, and finally selected All publishers,
All packages and View Updates.
Then there was one update: perl-584.
Now this guy cannot be updated, it cannot be removed, and it is
actually EMPTY and just has a marker saying it has been renamed to
perl-510.
It's no problem, really, but:
What determines if a package is reported as updatable??
pkg -u shows this same package as updatable, so it's not just the GUI
application that's wrong, here.
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
_______________________________________________
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss
