pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

pkg/41743: www/merb installation error (NetBSD 4.0)



>Number:         41743
>Category:       pkg
>Synopsis:       www/merb installation error (NetBSD 4.0)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 16 12:45: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:
        www/merb fails to install (and so also fails to generate a binary
        package).   (Other www/merb-* packages are all fine).
        The problem is a missing "lib" file (or just as likely, directory)
        somewhere (apparently) - the error message is very terse...

>How-To-Repeat:
        I use pkg_comp with libkver and NetBSD 4.0 sets installed
        (except x*, I use pkgsrc modular xorg instead).  Most probably
        none of that is relevant here.

        When building www/merb, except to see ...

===> Installing for merb-0.9.2
=> Generating pre-install file lists
=> Installing gem into installation root
File not found: lib
Successfully installed merb-0.9.2
1 gem installed
Installing ri documentation for merb-0.9.2...
*** Error code 1

Stop.

        What that "lib" is that is not found I have no idea
        (that is, whether it is something in the pkg that is
        to be copied, or something that should exist in /usr/pkg
        somewhere).   I'm even only guessing that the missing lib
        is the cause of the "Error code 1".

        I do see earlier ...

===> Building for merb-0.9.2
mkdir -p pkg
mkdir -p lib

        with no error from the mkdir (and no reason it should fail
        that I can imagine, though mkdir -p does tend to hide
        some errors - for those simple paths, is the -p really needed?)

        After that ...

WARNING:  no rubyforge_project specified
WARNING:  description and summary are identical
mv merb-more-0.9.2.gem pkg/merb-more-0.9.2.gem
WARNING:  no rubyforge_project specified
WARNING:  description and summary are identical
mv merb-0.9.2.gem pkg/merb-0.9.2.gem

        which seems to be the entire build process for www/merb !

        There's a little more output before the install phase
        starts, but that just seems to be providing some version
        info on those two files that we just mv'd.

>Fix:
        ??



Home | Main Index | Thread Index | Old Index