Bug 53841

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.14-5.0smp i686)

Description of problem:
When two RPMs are listed on the command line as part of an 'rpm -e <1> <2>'
command, RPM doesn't figure out which should be removed last.

IE:

If packageA "Requires:" packageB:

# rpm -Uvh packageA packageB

installs packageB first, then packageA, since B depends on A.

However, 

# rpm -e <1> <2>

doesn't look at dependencies, it simply removes the two packages in the
order that they're specified in.

-- Which IMO is broken, since you can't remove A without removing B first
if you specify the packages singly on the command line, but as soon as you
specify both at the same time, order doesn't matter.

So:

# rpm -e <1> <2>

removes 1, then 2

# rpm -e <2> <1> 

removes 2, then 1.

Which breaks things if you have a %postun script that needs to be run after
packageB (which is required by packageA) is removed, but not before.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create two RPMS, one (packageA) which requires: the other (packageB).
2. Make sure that packageA has a %postun script in it.
3. rpm -evvv <packageA> <packageB> and observe results
4. rpm -evvv <packageB> <packageA> and observe results
	

Actual Results:  During 3., packageA's %postun gets run before packageB is
removed -- BAD.
During 4., packageA's %postun gets run after packageB is removed -- GOOD.

Expected Results:  Both 3 and 4 should yield proper and deterministic
results.

If packageA requires packageB, packageB should always be removed before
packageA.

Additional info: