pkg/41735: wm/metisse has PLIST problems (and maybe more) (NetBSD 4.0 - or any)

[kre%munnari.OZ.AU@localhost]

>Number:         41735
>Category:       pkg
>Synopsis:       wm/metisse has PLIST problems (and maybe more) (NetBSD 4.0 - 
>or any)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 15 12:00:00 +0000 2009
>Originator:     Robert Elz
>Release:        NetBSD 4.0_STABLE
>Organization:
        Prince of Songkla University
>Environment:
System: NetBSD jade.coe.psu.ac.th 4.0_STABLE NetBSD 4.0_STABLE 
(JADE-1.696-20080517) #9: Fri May 23 18:55:13 ICT 2008 
kre%jade.coe.psu.ac.th@localhost:/usr/obj/4/kernels/JADE i386
Architecture: i386
Machine: i386
>Description:
        With PKG_DEVELOPER set, wm/metisse fails pkgsrc's file-check tests.

        That's the immediate problem, but things look a little more serious
        than that, as while metisse is clearly using python ((it uses -I
        with python include files) iand some of the files in the PLIST that
        aren't found are python files, and might be missing purely because
        the PLIST has a python version hard coded into it, and it happens
        to be the wrong one), I cannot see anywhere where it says that python
        must be installed (it isn't in TOOLS, LANGUAGES and there's
        PYTHON_VERSION_REQUIRED or anything like that).

        If it weren't for the mention of python files in the PLIST, I'd
        be tempted to assume that the problem is that metisse's autoconf
        just happened to find python installed and decided to use it,
        when that hadn't been planned by the pkgsrc develper - but the
        PLIST entries kind of knock that theory on its head.

        I suspect this pakage needs a careful look over by someone
        who understand's pkgsrc's dependency stuff (incl buildlink)
        and perhaps who understands the python framework.

>How-To-Repeat:
        I use pkg_comp with libkver and NetBSD 4.0 sets installed
        (but pkgsrc modular xorg instead of the x* sets).  I doubt
        any of that is relevant to this problem.   My default
        python is pkgsrc's default (currently 2.5).

        When I build (with PKG_DEVELOPER=yes - courtesy of pkg_comp), I see ...

=> Automatic manual page handling
=> Generating post-install file lists
=> Please note the following:

===========================================================================
$NetBSD: MESSAGE,v 1.1 2007/06/02 19:29:27 agc Exp $

For instructions on how to run metisse, please look at:

        /usr/pkg/share/metisse/doc/docs/running.html

===========================================================================

pkg_create: can't stat `/usr/pkg/bin/metisse-combo2radio'
pkg_create: can't stat `/usr/pkg/bin/metisse-combo2radio-edit'
pkg_create: can't stat `/usr/pkg/bin/metisse-demo-address-app'
pkg_create: can't stat `/usr/pkg/lib/python2.4/site-packages/facade_setup.py'
pkg_create: can't stat `/usr/pkg/lib/python2.4/site-packages/facade_setup.pyc'
pkg_create: can't stat `/usr/pkg/lib/python2.4/site-packages/facade_setup.pyo'
=> Registering installation for metisse-0.4.0rc4nb5
pkg_admin: metisse-0.4.0rc4nb5: File `/usr/pkg/bin/metisse-combo2radio' is in 
+CONTENTS but not on filesystem!
pkg_admin: metisse-0.4.0rc4nb5: File `/usr/pkg/bin/metisse-combo2radio-edit' is 
in +CONTENTS but not on filesystem!
pkg_admin: metisse-0.4.0rc4nb5: File `/usr/pkg/bin/metisse-demo-address-app' is 
in +CONTENTS but not on filesystem!
pkg_admin: metisse-0.4.0rc4nb5: File 
`/usr/pkg/lib/python2.4/site-packages/facade_setup.py' is in +CONTENTS but not 
on filesystem!
pkg_admin: metisse-0.4.0rc4nb5: File 
`/usr/pkg/lib/python2.4/site-packages/facade_setup.pyc' is in +CONTENTS but not 
on filesystem!
pkg_admin: metisse-0.4.0rc4nb5: File 
`/usr/pkg/lib/python2.4/site-packages/facade_setup.pyo' is in +CONTENTS but not 
on filesystem!
metisse-0.4.0rc4nb5 requires installed package gtk2+-2.16.4
metisse-0.4.0rc4nb5 requires installed package libXft-2.1.13
metisse-0.4.0rc4nb5 requires installed package libXpm-3.5.7nb1
metisse-0.4.0rc4nb5 requires installed package libXt-1.0.5nb1
metisse-0.4.0rc4nb5 requires installed package nucleo-0.7.5
metisse-0.4.0rc4nb5 requires installed package readline-6.0
metisse-0.4.0rc4nb5 requires installed package rplay-3.3.2nb7
metisse-0.4.0rc4nb5 requires installed package rxvt-2.7.10nb6
=> Checking file-check results for metisse-0.4.0rc4nb5
ERROR: ************************************************************
ERROR: The following files are in the PLIST but not in /usr/pkg:
ERROR:         /usr/pkg/bin/metisse-combo2radio
ERROR:         /usr/pkg/bin/metisse-combo2radio-edit
ERROR:         /usr/pkg/bin/metisse-demo-address-app
ERROR:         /usr/pkg/lib/python2.4/site-packages/facade_setup.py
ERROR:         /usr/pkg/lib/python2.4/site-packages/facade_setup.pyc
ERROR:         /usr/pkg/lib/python2.4/site-packages/facade_setup.pyo
*** Error code 1

Stop.
make: stopped in /usr/pkgsrc/wm/metisse
*** Error code 1

        In the build log, the only mention of facade_setup or the
        string ".py" anywhere, are included above (they're all
        complaints about the files not existing, they're never built,
        installed, or anything else...)

        (The string "-I/usr/pkg/include/python2.5" is passed to
        the compiler, for it looks like, every file compiled).

        On the other hand ...

config.status: creating bin/metisse-demo-address-app
config.status: creating bin/metisse-combo2radio
config.status: creating bin/metisse-combo2radio-edit

        appear during the configure stage, but those are the only
        references (aside from the error messages included above)
        of any of those names (I did my search without the
        "metisse-" prefix).   There's nothing where it claims to
        be (attempting to) install them.

>Fix:
        Requires Gunga Din.