Description of problem: Occaisionally, when installing rpm's I have made with rpmbuild, I get the following error: rpm: rpmte.c:589: rpmteColorDS: Assertion `ix < Count' failed I don't know if this is a problem with rpm or rpmbuild. There is a similar bug report, but their conclusion seemed to be that it was somethign specific to the package being installed. Version-Release number of selected component (if applicable): $ rpm -qa | grep rpm rpm-4.4.2-15.2 redhat-rpm-config-8.0.40-1 rpm-libs-4.4.2-15.2 rpm-build-4.4.2-15.2 rpm-python-4.4.2-15.2 rpm-devel-4.4.2-15.2 fedora-rpmdevtools-1.6-1.fc5
The other bug report I mentioned is #190972 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190972
Packages built with AutoReqProv: no should *not* be built with the internal dependency generator. Assertion failures result.
Are you saying that rpmbuild is not to be used to build rpms with autoreqprov = no? What then, should I use to build these rpms?
No I'm not saying that rpmbuild cannot be used. I'm saying that you cannot use the internal dependency generator with AutoReqProv:, you must also change to use the older find-{provides,requires} at the same time. This means that one cannot prepare multilib ready packages reliably using AutoReqProv:.
clearly I have not read enough documentation to understand how to properly use rpmbuild. is there some sort of documentation in addition to the man pages (developer docs of some sort?) which explains how to disable the internal dependency generator?
Add this line at the beginning of a spec file to disable %define _use_internal_dependency_generator 0 I'd suggest not using AutoReqProv: instead of adding the config line. Any package using AutoReqProv: which contains ELF binaries will not contain the information necessary to install correctly on multilib systems. Filtering out one or two unwanted dependencies that are being extracted can be done by removing the execute bit on the file that is generating the undesired dependency.
thanks. I was accidentally using "AutoReq: no" instead of "AutoReqProv: no". all is well now.