Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: aqsis - 3D Rendering system https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202946 ------- Additional Comments From paul@xxxxxxxxxxxx 2006-09-13 13:50 EST ------- (In reply to comment #6) > Ok, so the package builds under mock for me, but rpmlint complains: > > [build@zeus aqsis]$ rpmlint aqsis-1.0.1-2.fc6.x86_64.rpm > W: aqsis incoherent-version-in-changelog 1.0.1-1 1.0.1-2.fc6 > W: aqsis objdump-failed objdump: > /tmp/aqsis-1.0.1-2.fc6.x86_64.rpm.18847/usr/lib64/aqsis/libbake2tif.so.0.0.0: > File format not recognized > E: aqsis binary-or-shlib-defines-rpath /usr/lib64/aqsis/libdisplay.so.0.0.0 > ['/usr/lib64'] > W: aqsis objdump-failed objdump: > /tmp/aqsis-1.0.1-2.fc6.x86_64.rpm.18847/usr/lib64/aqsis/libgif2tif.so.0.0.0: > File format not recognized > W: aqsis objdump-failed objdump: > /tmp/aqsis-1.0.1-2.fc6.x86_64.rpm.18847/usr/lib64/aqsis/libjpg2tif.so.0.0.0: > File format not recognized > W: aqsis objdump-failed objdump: > /tmp/aqsis-1.0.1-2.fc6.x86_64.rpm.18847/usr/lib64/aqsis/libpcx2tif.so.0.0.0: > File format not recognized > W: aqsis objdump-failed objdump: > /tmp/aqsis-1.0.1-2.fc6.x86_64.rpm.18847/usr/lib64/aqsis/libppm2tif.so.0.0.0: > File format not recognized > W: aqsis objdump-failed objdump: > /tmp/aqsis-1.0.1-2.fc6.x86_64.rpm.18847/usr/lib64/aqsis/libtga2tif.so.0.0.0: > File format not recognized > W: aqsis objdump-failed objdump: > /tmp/aqsis-1.0.1-2.fc6.x86_64.rpm.18847/usr/lib64/libslpp.so.0.0.0: File format > not recognized > E: aqsis shlib-with-non-pic-code /usr/lib64/libslpp.so.0.0.0 > W: aqsis devel-file-in-non-devel-package /usr/share/aqsis/shaders/bake.h > W: aqsis devel-file-in-non-devel-package /usr/share/aqsis/shaders/DPProctext.h > W: aqsis devel-file-in-non-devel-package /usr/share/aqsis/shaders/patterns.h > W: aqsis devel-file-in-non-devel-package /usr/share/aqsis/shaders/noises.h > > The headers sound like they should be there (comment #1); the first warning is > an easyfix (needs a changelog entry). The rpath error needs to be dealt with; > the objdump errors may be related to that I ran rpmlint against them on my fc5 > system (anyone know an easy way to install rpmlint in a mock chroot?) Just came across this issue myself. It's possible to do this as follows: 1. Copy the packages you're trying to run rpmlint against into the chroot's root: $ cp *.rpm /var/lib/mock/fedora-development-x86_64-core/root/ 2. Install rpmlint into the chroot: $ /usr/sbin/mock-helper yum --installroot /var/lib/mock/fedora-development-x86_64-core/root install rpmlint 3. Get a shell in the chroot: $ mock -r fedora-devel-x86_64-core.cfg shell 4. Run rpmlint: mock-chroot> rpmlint *.rpm 5. Exit from the chroot: mock-chroot> exit -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review