Before I open a bug and cause unnecessary noise, I want to see if I have
uncovered a problem with the pkg/external_deps.pkglintrc file for Build
171. On a system running Build 170, there are no issues, but on a
nightly build 171 system I see this when running pkglint as part of the
src/pkg make:
> WARNING pkglint.action005.1 obsolete dependency check skipped:
unable to find dependency pkg:/library/python-2/cherrypy-26 for
pkg://pkg5-nightly/package/pkg
> WARNING pkglint.action005.1 obsolete dependency check skipped:
unable to find dependency pkg:/library/python-2/m2crypto-26 for
pkg://pkg5-nightly/package/pkg
> WARNING pkglint.action005.1 obsolete dependency check skipped:
unable to find dependency pkg:/library/python-2/mako-26 for
pkg://pkg5-nightly/package/pkg
> WARNING pkglint.action005.1 obsolete dependency check skipped:
unable to find dependency pkg:/library/python-2/ply-26 for
pkg://pkg5-nightly/package/pkg
> WARNING pkglint.action005.1 obsolete dependency check skipped:
unable to find dependency pkg:/library/python-2/pybonjour-26 for
pkg://pkg5-nightly/package/pkg
> WARNING pkglint.action005.1 obsolete dependency check skipped:
unable to find dependency pkg:/library/python-2/pycurl-26 for
pkg://pkg5-nightly/package/pkg
This causes the pkg src build to fail.
I believe this is caused by the python 2.7 integration and the renaming
of the current 2.6 packages to *-26. While this won't pose a problem for
the official build 171 which will run on a system at build 170, it will
pose a problem for nightly builds and for build 172.
Should I go ahead and open a bug against pkg/external_deps.pkglintrc?
Should the packages above be added so that build 171 will work with the
change, or should they replace the existing entries and not be checked
in until ready for build 172?
Or am I totally misinterpreting what is happening?
-- Alan
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
