Mailinglist Archive: opensuse-packaging (220 mails)

[Ralf Lang <lang@xxxxxxxxxxxxx>]

Hi,



the following happened before with other packages 
(which I then packaged without fancy macros which lead to some factory 
complaints)


but this puzzles me once again:


RPMLINT report:

php5-pear-phpunit-PHP_CodeBrowser.noarch: W: no-manual-page-for-binary phpcb
Each executable in standard binary directories should have a man page.

php5-pear-phpunit-PHP_CodeBrowser.noarch: W: files-duplicate 
/usr/share/php5/PEAR/data/PHP_CodeBrowser/templates/img/treeToggle-
extended.png 
/usr/share/php5/PEAR/data/PHP_CodeBrowser/templates/js/jquery.sidebar/css/codebrowser/inject-
right.png
php5-pear-phpunit-PHP_CodeBrowser.noarch: E: file-contains-buildroot (Badness: 
10000) /usr/share/php5/PEAR/PHP_CodeBrowser/CLIController.php
php5-pear-phpunit-PHP_CodeBrowser.noarch: E: file-contains-buildroot (Badness: 
10000) /usr/bin/phpcb
Your file contains traces of $RPM_BUILD_ROOT.

(none): E: badness 20000 exceeds threshold 1000, aborting.
2 packages and 0 specfiles checked; 2 errors, 2 warnings.


The original file does not contain static paths but relative ones (../)
After rpm packaging they contain static paths and generate errors



Why is that? I think rpm imagines these references to  runtime dependencies 
are compile-time objects in the buildroot.

How to circumvent this?

-- 
Ralf Lang
Linux Consultant / Developer

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx