Description of problem:
When a %prentans script is specified in a spec file and it exits with non-zero code, the installation of the current RPM is aborted; however, if additional packages were selected as dependencies, they still get installed even though the %pretrans has failed and the main RPM does not get installed.

It is important to note that %pretrans is checked before any dependencies are installed, so a failure there should abort the whole transaction (including the dependencies).

Version-Release number of selected component (if applicable):
yum-3.4.3-153.fc21.noarch

How reproducible:
Every time.

Steps to Reproduce:
1. Create an RPM from a spec file which has a %prentans section. Add a dependency RPM package to the spec and make the %pretrans section exit with non-zero code.
2. Install the RPM package on a machine where the dependency RPM package is missing. 

Actual results:
The %preptans will fail and the main RPM package will not be installed, but the dependency package will be installed.

Expected results:
The dependency packages should not be installed if a %pretrans form the main RPM has failed. 

Additional info:
The main problem here is not so much the fact that dependencies still get installed, but the fact that the failure of %pretrans from the main RPM (hence the failure to install the main RPM) remains obscure, especially if running yum in interactive mode from console. One can well consider the main RPM installed, which leads to much confusion later about it actually missing.