Thanks Danek,

that indeed does let me update SUNW0punchin which was my aim
in the beginning.

Will I be needing to uninstall all my other non compliant pkgs before
I can update to snv_160 once that is available ??

-George

On 24/02/2011 19:39, Danek Duvall wrote:
[email protected] wrote:

Ouch that will require me to uninstall all of our VPNs so that won't happen,
I work from home.

     4 packages deliver 'dir group=bin mode=0755 owner=root path=usr':
...
         
pkg://software-packages.org/vpn/[email protected],5.11-0.134:20100701T210505Z
         pkg://software-packages.org/vpn/[email protected],5.11-0.134:20100701T185150Z

    1 package delivers 'dir group=sys mode=0755 owner=root 
path=usr/share/applications':
         pkg://punchin/[email protected],5.11-1:20101124T135926Z
     83 packages deliver 'dir group=other mode=0755 owner=root 
path=usr/share/applications', including:
You could always pkgrecv (all) the broken packages, fix them up, and
republish them to a local publisher, until their owners have fixed the
problems.

The fix I have for the problem is really simple, though, and you can apply
it yourself:

   - as root, edit /usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py

   - line 808 should read:

         if not nproblems:

   - change it to read:

         if not nproblems or len(actions)<= len(oactions):

and try your removals again.  That should, I think, even let you upgrade to
the latest version of SUNW0punchin, which has a fix for this particular
problem.

Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to