MOn Jul 14, 2011, at 8:03 PM, "James C. McPherson" <[email protected]>
wrote:
>
> Hi folks,
> I'm trying to rebuild our fattened version of onbld, but
> it's failing with this rather strange error:
>
> Publishing developer-build-onbld to redist repository
> pkgsend: No such file:
> '/export/builds/onnv-tools/proto/root_i386-nd/licenses/opt/onbld/bin/i386/aw'.
> *** Error code 1
> The following command caused the error:
> m=$(basename packages.i386/developer-build-onbld.metadata.*); \
> r=${m#developer-build-onbld.metadata.+(?).}; \
> if [ -s packages.i386/developer-build-onbld.res ]; then \
> print "Publishing developer-build-onbld to $r repository"; \
> PYTHONPATH=//usr/lib/python2.6/vendor-packages //usr/bin/pkgsend -s
> file:///export/builds/onnv-tools/usr/src/../../packages/i386/nightly-nd/repo.$r
> publish \
> -d /export/builds/onnv-tools/proto/root_i386-nd -d
> /export/builds/onnv-tools/usr/src/tools/proto/root_i386-nd \
> -d packages.i386 -d
> /export/builds/onnv-tools/proto/root_i386-nd/licenses \
> --fmri-in-manifest --no-index --no-catalog
> packages.i386/developer-build-onbld.res \
> > /dev/null; \
> fi; \
> /usr/bin/touch packages.i386/developer-build-onbld.pub;
> dmake: Fatal error: Command failed for target
> `packages.i386/developer-build-onbld.pub'
> Current working directory /export/builds/onnv-tools/usr/src/pkg
>
>
> The script runs this sequence of commands from within bldenv:
>
> PKGPUBLISHER_REDIST="on-onbld" ; export PKGPUBLISHER_REDIST
>
> BLDCMD="unset CC ; cd ${WS}/usr/src && ${DMAKE} setup && cd ${TOOLSRC} && "
> BLDCMD="${BLDCMD}${MAKE} clobber && rm -rf ${PKGARCHIVE} && "
> BLDCMD="${BLDCMD}${FIND} ${TOOLSRC} -name .make.state -exec rm {} \; && "
> BLDCMD="${BLDCMD}${DMAKE} install >> ${WS}/log/log.${BUILDDATE} 2>&1 ;"
> BLDCMD="${BLDCMD}cd ${WS}/usr/src/pkg ;"
> BLDCMD="${BLDCMD}${DMAKE} PKGPUBLISHER_REDIST=\"on-onbld\"
> PKGS=\"developer-build-onbld\" install "
>
>
> (/ws/onnv-tools/public/gate/bin/build_blended_onbld.sh)
>
>
> What am I doing wrong? (Note that this has worked perfectly
> well in the past, including the last time we pushed new tools
> to ipkg).
>
I made some pkgsend changes in the last few days but those aren't in the wos
yet. Are you running pkg nightly bits?
If so, I may have broken something because we're missing a test case.
Otherwise, no idea at the moment. I can look at this in the morning in more
detail.
If you are running pkg nightly bits, downgrading to the 169 wos bits for pkg
would be helpful. pkg update will let you do that if you explicitly name te
older versions of all the pkg(5) packages and incorportation.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
