Bug 435449

Created attachment 296338 [details]
yum output

Created attachment 296339 [details]
adobe-release.repo

I'm attaching all the repos from /etc/yum.repos.d to reproduce this bug.
FWIW, "yum clean all" doesn't change the behavior.

Created attachment 296340 [details]
atrpms.repo

Created attachment 296341 [details]
emacs-22 repo

Created attachment 296342 [details]
fedora.repo

Created attachment 296343 [details]
fedora-development.repo

Created attachment 296344 [details]
fedora-updates.repo

Created attachment 296345 [details]
fedora-updates-testing.repo

Created attachment 296346 [details]
livna.repo

Created attachment 296347 [details]
livna-testing.repo

Created attachment 296348 [details]
rhts.repo

Created attachment 296349 [details]
brew.repo

I removed the emacs-22 repo (which I wasn't using anyway), did a "yum clean all"
followed by a "yum install -y mpg321" and hit the same infinite recursion bug.

yumdownloader worked fine to download the package, which had two unresolved
dependencies:

$ sudo rpm -ivh mpg321-0.2.10.3-3.lvn6.i386.rpm 
error: Failed dependencies:
        libid3tag.so.0 is needed by mpg321-0.2.10.3-3.lvn6.i386
        libmad.so.0 is needed by mpg321-0.2.10.3-3.lvn6.i386

yum was able to install each of those separately:

$ sudo yum install -y libid3tag
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package libid3tag.i386 0:0.15.1b-3.fc6 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 libid3tag               i386       0.15.1b-3.fc6    fedora             44 k

Transaction Summary
=============================================================================
Install      1 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 44 k
Downloading Packages:
(1/1): libid3tag-0.15.1b- 100% |=========================|  44 kB    00:00     
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: libid3tag                    ######################### [1/1] 

Installed: libid3tag.i386 0:0.15.1b-3.fc6
Complete!
[coldwell@localhost tmp]$ sudo yum install libmad
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package libmad.i386 0:0.15.1b-4.lvn6 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 libmad                  i386       0.15.1b-4.lvn6   livna              82 k

Transaction Summary
=============================================================================
Install      1 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 82 k
Is this ok [y/N]: y
Downloading Packages:
(1/1): libmad-0.15.1b-4.l 100% |=========================|  82 kB    00:00     
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing: libmad                       ######################### [1/1] 

Installed: libmad.i386 0:0.15.1b-4.lvn6
Complete!

After which, I could manually install the package, no problem:

$ sudo rpm -ivh mpg321-0.2.10.3-3.lvn6.i386.rpm 
Preparing...                ########################################### [100%]
   1:mpg321                 ########################################### [100%]
$ echo $?
0

Can you run with -d6 added to the yum command line and grab the output?

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "CLOSED INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.

Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.