As I mentioned before, I'm very much an IPS newbie and, naturally, am not familiar with all of the IPS nomenclature so it was hard to understand the man pages. I tried using pkgdepend(1) and got this:

% pkgdepend generate /builds/benc/6982090/service-network-nis.mf /builds/benc/6975568/snv/proto > t.dep
Couldn't find /builds/benc/6975568/snv/proto/path=etc/default/yppasswdd
Couldn't find /builds/benc/6975568/snv/proto/path=lib/svc/manifest/network/nis/passwd.xml Couldn't find /builds/benc/6975568/snv/proto/path=lib/svc/manifest/network/nis/server.xml Couldn't find /builds/benc/6975568/snv/proto/path=lib/svc/manifest/network/nis/update.xml Couldn't find /builds/benc/6975568/snv/proto/path=lib/svc/manifest/network/nis/xfr.xml
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/inityp2l
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/mkalias
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/multi
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/multi.awk Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/rpc.yppasswdd Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/rpc.ypupdated Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/stdethers
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/stdhosts
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/udpublickey Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/ypmap2src
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/yppush
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/ypserv
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/ypxfr_1perday Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/ypxfr_1perhour Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/ypxfr_2perday
Couldn't find /builds/benc/6975568/snv/proto/path=usr/lib/netsvc/yp/ypxfrd
Couldn't find /builds/benc/6975568/snv/proto/path=usr/sbin/mknetid
Couldn't find /builds/benc/6975568/snv/proto/path=usr/sbin/revnetgroup
Couldn't find /builds/benc/6975568/snv/proto/path=var/yp/Makefile
Couldn't find /builds/benc/6975568/snv/proto/path=var/yp/updaters

The contents of t.dep was a copy of the manifest. Did I supply the right arguments? I also tried "resolve":

pkgdepend resolve -m -d /builds/benc/6975568/snv/proto t.dep
Traceback (most recent call last):
  File "/bin/pkgdepend", line 505, in <module>
    __ret = main_func()
  File "/bin/pkgdepend", line 491, in main_func
    return resolve(pargs, img_dir)
  File "/bin/pkgdepend", line 272, in resolve
    prune_attrs=not verbose, use_system=use_system_to_resolve)
File "/usr/lib/python2.6/vendor-packages/pkg/publish/dependencies.py", line 723, in resolve_deps
    pfmri = fmri.PkgFmri(name).get_short_fmri()
File "/usr/lib/python2.6/vendor-packages/pkg/fmri.py", line 129, in __init__
    nested_exc=iv)
IllegalFmri: Illegal FMRI 'pkg:/service/network/n...@$(PKGVERS)': Bad Version: $(PKGVERS)


pkgdepend: 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 '552262a56a9a'.


   I tried pkglint(1) and got:

# pkglint -c /var/tmp/cache -r http://localhost:13000 /net/train.sfbay/builds/benc/6982090/service-network-nis.mf
Lint engine setup...
CRITICAL lint.manifest002 Error in file /net/train.sfbay/builds/benc/6982090/service-network-nis.mf: Illegal FMRI 'pkg:/service/network/n...@$(PKGVERS)': Bad Version: $(PKGVERS) Error: Unable to create reference image: No lint image or manifests provided.


Thanks,
Ben

On 7/09/10 3:01 PM, [email protected] thus spake:
On Tue, Sep 07, 2010 at 02:28:57PM -0700, Ben Chang wrote:
    Thanks.

    Also thanks to those of you who answered Shawn's question about "make".

    BTW, are there any test suites that I need to run before RTI'ing
my code change?

You might consider running pkglint(1) and pkgdep(1) against the new
packages. These utilities can alert you to potential problems with your
package.

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

Reply via email to