Re: BLCR 0.6.3 a few rpmlint errors

From: Paul H. Hargrove (PHHargrove_at_lbl_dot_gov)
Date: Wed Jan 23 2008 - 12:26:36 PST

  • Next message: Locus Jackson: "Why do I get the error "cri_syscall(CR_OP_RSTRT_PROCS):Invalid arguments""
    Thanks, Neal.
    
    As I explained in a previous round, the "library-not-linked-against-lib"
    issue is one we cannot resolve w/o significant changes in the way we
    build the libraries - changes I am not prepared to make in the 0.6.x
    series.  The good news is that this one has been fixed for 0.7.0 (see
    http://upc-bugs.lbl.gov/bugzilla/show_bug.cgi?id=2042 for details).
    
    The unstripped kernel modules and packages w/o documentation are easy
    enough to fix.  I'll make a note to myself, but there are not a high
    priority for me.
    
    The lack of blcr-devel -> blcr dependency is intended.  The blcr-devel
    package depends on blcr-libs because that is where the required
    libraries reside.  The "base" blcr package contains nothing that is
    needed for blcr-devel to function.  On a machine where one wished to
    compile BLCR clients but not run them, blcr-libs + blcr-devel is
    sufficient.  In theory renaming here might silence the warning (blcr
    becomes blcr-base or blcr-utils and blcr-libs becomes blcr).  However, I
    am not prepared to make this change right now if silencing this warning
    is the only benefit.  However, if package updaters like YUM need this
    naming scheme, I'll consider the change. Is there Fedora documentation
    about how packages like this are supposed to be named?
    
    -Paul
    
    Neal Becker wrote:
    > Here's what rpmlint on fedora f8 says (only 2 are really errors):
    > 
    > rpmlint RPM/RPMS/x86_64/blcr-*6.3*
    > blcr.x86_64: W: incoherent-version-in-changelog 0.6.0_b7 0.6.3-1
    > blcr.x86_64: W: service-default-enabled /etc/init.d/blcr
    > blcr-devel.x86_64: W: no-documentation
    > blcr-devel.x86_64: W: no-dependency-on blcr
    > blcr-libs.x86_64: E: library-not-linked-against-libc /usr/lib64/libcr.so.0.2.1
    > blcr-libs.x86_64: E: library-not-linked-against-libc /usr/lib/libcr.so.0.2.1
    > blcr-modules_2.6.23.9_85.fc8.x86_64: W: no-documentation
    > blcr-modules_2.6.23.9_85.fc8.x86_64: W: 
    > unstripped-binary-or-object /lib/modules/2.6.23.9-85.fc8/extra/blcr_imports.ko
    > blcr-modules_2.6.23.9_85.fc8.x86_64: W: 
    > unstripped-binary-or-object /lib/modules/2.6.23.9-85.fc8/extra/blcr_vmadump.ko
    > blcr-modules_2.6.23.9_85.fc8.x86_64: W: 
    > unstripped-binary-or-object /lib/modules/2.6.23.9-85.fc8/extra/blcr.ko
    > blcr-testsuite.x86_64: W: no-documentation
    
    
    -- 
    Paul H. Hargrove                          PHHargrove_at_lbl_dot_gov
    Future Technologies Group
    HPC Research Department                   Tel: +1-510-495-2352
    Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900
    

  • Next message: Locus Jackson: "Why do I get the error "cri_syscall(CR_OP_RSTRT_PROCS):Invalid arguments""