Hello,

I'm quite sure I'm doing something dumb in order to get the gmake publish error below but I just don't see it? I fairly recently modified my environment slightly but I don't recall doing anything that should affect this (I commented out CANONICAL_REPO but it's now got a default setting in ips-build.mk so I don't see that setting it in my environment is necessary anymore.)

I couldn't find anything in my email or in the userland archives that seemed relevant.

This is on a clone today of the default (u1) branch of userland with no changes in the workspace:

[kc28005@jade2:/builds1/kc28005/workspace/components/httping ] $ gmake publish /usr/bin/pkgmogrify -D PERL_ARCH=i86pc-solaris-64int -D PERL_VERSION=5.12 -D MACH=i386 -D MACH32=i86 -D MACH64=amd64 -D PUBLISHER=userland -D CONSOLIDATION=userland -D BUILD_VERSION=5.11-0.175.1.0.0.4.617 -D SOLARIS_VERSION=2.11 -D OS_VERSION=5.11 -D HUMAN_VERSION= -D IPS_COMPONENT_VERSION=1.4.4 -D COMPONENT_VERSION=1.4.4 -D COMPONENT_PROJECT_URL=http://www.vanheusden.com/httping/ -D COMPONENT_ARCHIVE_URL=http://www.vanheusden.com/httping/httping-1.4.4.tgz -D COMPONENT_HG_URL= -D COMPONENT_HG_REV= httping.p5m \ /builds1/kc28005/workspace/transforms/variant-cleanup /builds1/kc28005/workspace/transforms/autopyc /builds1/kc28005/workspace/transforms/defaults /builds1/kc28005/workspace/transforms/actuators /builds1/kc28005/workspace/transforms/devel /builds1/kc28005/workspace/transforms/docs /builds1/kc28005/workspace/transforms/locale /builds1/kc28005/workspace/transforms/publish-cleanup | \ sed -e '/^$/d' -e '/^#.*$/d' | uniq >/builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.mogrified /bin/mkdir -p /builds1/kc28005/workspace/components/httping/build/prototype/i386/mangled /builds1/kc28005/workspace/tools/userland-mangler -D /builds1/kc28005/workspace/components/httping/build/prototype/i386/mangled -d /builds1/kc28005/workspace/components/httping/build/prototype/i386/mangled -d /builds1/kc28005/workspace/components/httping/build/prototype/i386 -d /builds1/kc28005/workspace/components/httping/build -d /builds1/kc28005/workspace/components/httping -d httping-1.4.4 -m /builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.mogrified >/builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.mangled /usr/bin/pkgdepend generate -m -d /builds1/kc28005/workspace/components/httping/build/prototype/i386/mangled -d /builds1/kc28005/workspace/components/httping/build/prototype/i386 -d /builds1/kc28005/workspace/components/httping/build -d /builds1/kc28005/workspace/components/httping -d httping-1.4.4 /builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.mangled >/builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.depend /usr/bin/pkgdepend resolve -m /builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.depend /usr/bin/touch /builds1/kc28005/workspace/components/httping/build/.resolved-i386 VALIDATING MANIFEST CONTENT: /builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.depend.res /usr/bin/env PYTHONPATH=/builds1/kc28005/workspace/tools/python PROTO_PATH="/builds1/kc28005/workspace/components/httping/build/prototype/i386/mangled /builds1/kc28005/workspace/components/httping/build/prototype/i386 /builds1/kc28005/workspace/components/httping/build /builds1/kc28005/workspace/components/httping httping-1.4.4"\
        /usr/bin/pkglint -c /builds1/kc28005/workspace/i386/pkglint-cache \
-f /builds1/kc28005/workspace/tools/pkglintrc /builds1/kc28005/workspace/components/httping/build/manifest-i386-httping.depend.res
Lint engine setup...
Error: Unable to access any pkglint images under /builds1/kc28005/workspace/i386/pkglint-cache gmake: *** [/builds1/kc28005/workspace/components/httping/build/.linted-i386] Error 1
[kc28005@jade2:/builds1/kc28005/workspace/components/httping ] $



Thanks in advance for any ideas,
Kevin.

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

Reply via email to