[csw-maintainers] checkpkg problem under Solaris 11 ?

[Maciej (Matchek) Bliziński]

2012/5/24 Maciej (Matchek) Bliziński <maciej at opencsw.org>

> One question ‒ how can you check any 5.11 package at all, since checkpkg
> doesn't support checking packages against SunOS5.11 catalogs?


Maybe I should clarify what I mean: the package database on the buildfarm
does not have the system files imported. Here's what happens when you try
to test the package, the error message says it all:

$ bin/checkpkg --arch sparc --os-release SunOS5.11 --catalog-release
unstable /home/yann/build/libssl_dev-1.0.1c\,
REV\=2012.05.24-SunOS5.11-sparc-UNCOMMITTED.pkg.gz
INFO:root:Juicing the srv4 package stream files...
100%
|#####################################################################################################################################################################|
Traceback (most recent call last):
  File "bin/checkpkg", line 197, in <module>
    main()
  File "bin/checkpkg", line 148, in main
    dm.VerifyContents(sqo_osrel, sqo_arch)
  File "/home/maciej/src/opencsw-git/gar/v2/lib/python/database.py", line
139, in VerifyContents
    sqo_osrel.short_name, sqo_arch.name))
database.DatabaseError: Checkpkg can't find system files for SunOS5.11
sparc in the cache database.  These are files such as /usr/lib/libc.so.1.
 Private DB setup: you can only check packages built for the same Solaris
version you're running on this machine.  For instance, you can't check a
SunOS5.9 package on SunOS5.10. Shared DB setup (e.g. OpenCSW maintainers):
If you have one home directory on multiple hosts, make sure you run
checkpkg on the host you intended to.  To fix, go to a sparc SunOS5.11 host
and execute: pkgdb system-files-to-file; pkgdb import-system-file
install-contents-SunOS5.11-sparc.pickle; See
http://wiki.opencsw.org/checkpkg for more information.

I'll see if I can prepare the package database to support Solaris 11 checks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20120524/2e236cad/attachment.html>