On Thu, Mar 6, 2008 at 10:20 PM, Shawn Walker <[EMAIL PROTECTED]> wrote:
> On Wed, Mar 5, 2008 at 11:38 AM, Shawn Walker <[EMAIL PROTECTED]> wrote:
>  > On Wed, Mar 5, 2008 at 11:36 AM,  <[EMAIL PROTECTED]> wrote:
>  >  > My guess is that you pulled down the new test but forgot to install the
>  >  >  new version of pkgtarfile.py in your proto area.  If you run a make
>  >  >  install and then re-run the api-complete.py, do you still get the 
> error?
>  >
>  >  That's probably what it was, though I thought I did that.
>
>  Hrm, I did do that, and I'm still having the problem.
>
>  I did a make clobber && make install.
>
>  I even tried a clean checkout of the pkg tree.
>
>  Running developer preview2 here.
>
>  Here's my PATH:
>  
> /opt/SUNWspro/bin:/opt/onbld/bin:/usr/gnu/bin:/opt/SUNWspro/bin:/opt/onbld/bin:/usr/gnu/bin:/usr/bin:/usr/openwin/bin:/usr/sbin:/sbin:/usr/sbin:/sbin
>
>  Here's my PYTHONPATH:
>  /export/home/xxx/devel/pkg/proto/root_i386/usr/lib/python2.4/vendor-packages/
>
>  What am I missing?

Oh, one more interesting tidbit:

This failure only happens when I run "make test" as root.

In other words:

pfexec bash
make test

It seems to work fine if I run it as my own user.

Does that mean anything?

-- 
Shawn Walker, Software and Systems Analyst
http://binarycrusader.blogspot.com/

"To err is human -- and to blame it on a computer is even more so." -
Robert Orben
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to