FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 06-15-2011, 10:51 PM
Rex Dieter
 
Default Problem with strange debug package requirements being added to package & a self introduction

Veeti Paananen wrote:

> Hi!
>
> My name is Veeti and I'm a student from Finland. (Studying, however, is
> not one of my favourite pastimes).
>
> I'm currently packaging (or trying to package) a small application
> called paco. paco is a simple tool for managing installations of source
> packages. (Basically, it logs what files "make install" litters your
> system with so that uninstallation is easy). The paco website is at
> http://paco.sourceforge.net/.
>
> In any case, I've encountered a small problem. I've got a spec file that
> I think passes all the guidelines, etc. and it builds and works just
> fine on x86_64. However, when doing a mock/koji build for i686, some
> strange requirements are added for the package, as seen in this build log:
>
>> Processing files: paco-2.0.9-3.fc15.i686
>> (snip)
>> Requires: /bin/bash /bin/sh /usr/bin/perl
>> c08d9c216b94d87ba9e48b9ba6f243b21dd2ef.debug libc.so.6
>> libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2.3)
>> libc.so.6(GLIBC_2.3.4) libc.so.6(GLIBC_2.4) libdl.so.2
>> libdl.so.2(GLIBC_2.0) libgcc_s.so.1 libgcc_s.so.1(GCC_3.0) libm.so.6
>> libpaco-log.so.0 libpaco-log.so.0.debug libpaco-log.so.debug
>> libstdc++.so.6 libstdc++.so.6(CXXABI_1.3) libstdc++.so.6(GLIBCXX_3.4)
>> libstdc++.so.6(GLIBCXX_3.4.11) libstdc++.so.6(GLIBCXX_3.4.9) perl(Cwd)
>> perl(Getopt::Long) perl(strict) perl(warnings) rtld(GNU_HASH)
>
> More specifically, the following:
>
> * c08d9c216b94d87ba9e48b9ba6f243b21dd2ef.debug
> * libpaco-log.so.0.debug
> * libpaco-log.so.debug
>
> These don't exist on the x86_64 package.
>
> (libpaco-log is a library used by the application internally only to log
> installations.)
>
> How do I get rid of these, and what is causing this?

It's this overly broad glob in %files
%{_libdir}/*

Narrow this down to at least not include /usr/lib/debug too

-- Rex

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 09:14 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org