https://bugzilla.redhat.com/show_bug.cgi?id=836840

--- Comment #8 from bebo_sudo <bebo.s...@gmail.com> ---
Hi all, 
I'm trying to build an updated version but rpmbuild exit with those results:
....[cut]
+ desktop-file-install --dir
/home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/applications
/home/makerpm/rpmbuild/SOURCES/gtkradiant.desktop
+ install -p -m 644 /home/makerpm/rpmbuild/SOURCES/gtkradiant.png
/home/makerpm/rpmbuild/BUILDROOT/gtkradiant-1.6-20121007.1.fc17.x86_64/usr/share/icons/hicolor/128x128/apps
+ /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
*          to fail. To ignore these errors, you can set the '$QA_RPATHS'
*          environment variable which is a bitmask allowing the values
*          below. The current value of QA_RPATHS is 0x0000.
*
*    0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
*               issue but are introducing redundant searchpaths without
*               providing a benefit. They can also cause errors in multilib
*               environments.
*    0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
*               nor relative filenames and can therefore be a SECURITY risk
*    0x0004 ... insecure RPATHs; these are relative RPATHs which are a
*               SECURITY risk
*    0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
*               RPATHs; this is just a minor issue but usually unwanted
*    0x0010 ... the RPATH is empty; there is no reason for such RPATHs
*               and they cause unneeded work while loading libraries
*    0x0020 ... an RPATH references '..' of an absolute path; this will break
*               the functionality when the path before '..' is a symlink
*          
*
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
*   $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
*   $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
*  
*******************************************************************************
ERROR   0004: file '/usr/share/gtkradiant/q3data' contains an insecure rpath
'.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/q3map2' contains an insecure rpath
'.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/bobtoolz.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/model.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/ufoai.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/bkgrnd2d.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/camera.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/surface_heretic2.so' contains
an insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/imagewal.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/map.so' contains an insecure
rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/vfswad.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/prtview.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/modules/mapxml.so' contains an
insecure rpath '.' in [.]
..[cut]..
ERROR   0004: file '/usr/share/gtkradiant/modules/vfsqlpk3.so' contains an
insecure rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/radiant.bin' contains an insecure
rpath '.' in [.]
ERROR   0004: file '/usr/share/gtkradiant/q3map2_urt' contains an insecure
rpath '.' in [.]
errore: Stato d'uscita errato da /var/tmp/rpm-tmp.RfZ5zk (%install)


Errori di compilazione RPM:
    Stato d'uscita errato da /var/tmp/rpm-tmp.RfZ5zk (%install)
$

how could I solve it?

Thank's to anyone.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/package-review

Reply via email to