|Summary:||rpmtsCheck() returns 0 (No Problems) when dependencies don't match|
|Product:||Red Hat Enterprise Linux 3||Reporter:||James Olin Oden <james.oden>|
|Component:||rpm||Assignee:||Panu Matilainen <pmatilai>|
|Status:||CLOSED WONTFIX||QA Contact:||Mike McLean <mikem>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2007-10-11 10:51:57 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description James Olin Oden 2005-06-06 13:48:23 UTC
Description of problem: In rpmts.h, rpmtsCheck() has the following doxygen: * Check that all dependencies can be resolved. * @param ts transaction set * @return 0 on success */ int rpmtsCheck(rpmts ts) The part germain to this discussion is that it should return 0 on success and I assume non-zero on failure. When I run rpmtsCheck on a transaction with missing dependencies, though I get a problem set returned (via the transaction) rpmtsCheck() always returns 0. Version-Release number of selected component (if applicable): 4.2.3 How reproducible: Always Steps to Reproduce: 1. Create some packages with unmet dependencies. 2. Either write enough code to create the transaction and run rpmtsCheck() or add some debug code to rpm that printes the return value of rpmtsCheck(). 3. Now this transaction through your program or the patched rpm. Actual results: rpmtsCheck() == 0 Expected results: rpmtsCheck != 0 Additional info: I realize this may not be a bug if you mean by success that it actually could check dependencies. If some clarification needs to be done to the doxygen.
Comment 1 Jeff Johnson 2006-04-04 12:03:45 UTC
rpmtsCheck() returns 0 meaning that resolution was successfully attempted for all dependencies. The result you want, that no dependencies were unmatched, is in the problem set that is computed by rpmtsCheck().
Comment 2 Panu Matilainen 2007-10-11 10:51:57 UTC
rpmtsCheck() documentation clarified in rpm.org upstream, but WONTFIX for RHEL3.