[csw-pkgsubmissions] newpkgs idle, python, python_devel, python_tk

[Maciej (Matchek) Blizinski]

No dia 23 de Abril de 2010 21:49, Philip Brown <phil at bolthole.com> escreveu:
> erm... there's some really really old legacy garbage in the python package.
>
> ERROR: build-machine paths found in file
> python-2.6.5,REV=2010.04.19-SunOS5.9-sparc-CSW.pkg.gz

Yes, this is known and expected.  It deserves a bit of explanation.
I'm cc'ing maintainers@, as the same issue might affect other people
too.

The CSWpython package contains legacy shared library, namely
/opt/csw/lib/libpython2.5.so.1.0.  This file is stored in the
repository in the binary form and added to the pkgroot in a separate
step during building.  It's not recompiled any more.  There's no
description to compile it, so it's bound to stay the way it is until
it's removed.

The legacy library contains build-machine paths, and it always did.
Here's a session dump from build9s:

maciej at current9s :~/src/opencsw/pkg/python/trunk > ggrep medusa
/opt/csw/lib/libpython2.5.so.1.0
Binary file /opt/csw/lib/libpython2.5.so.1.0 matches

The reason we didn't know about it is because the pre-maciej version
of checkpkg failed to detect that.  Current version of checkpkg does
detect and report it.  There is a need to tell checkpkg that we know
about this problem and that it's okay.  If you look into
python-2.6.5,REV=2010.04.19-SunOS5.9-sparc-CSW.pkg.gz, you'll notice:

/opt/csw/share/checkpkg/overrides/python

containing:

CSWpython: file-with-bad-content /export/medusa
root/opt/csw/lib/libpython2.5.so.1.0
CSWpython: file-with-bad-content /opt/build root/opt/csw/lib/libpython2.5.so.1.0
CSWpython: file-with-bad-content /export/medusa
root/opt/csw/share/checkpkg/overrides/python
CSWpython: file-with-bad-content /opt/build
root/opt/csw/share/checkpkg/overrides/python

The override file is a plaintext file, and it contains the
"/export/medusa" string.  I believe that this is the file that the old
checkpkg complained about.  If it was able to detect build-machine
paths reliably, it would have always complained about CSWpython.

Looking at the whole catalog, there are currently 189 packages
affected by this issue (build-machine paths).  Here's the list of
packages with details: http://www.opencsw.org/~maciej/bad-content.txt

Maciej