Description of problem: When I downgrade a package that has related packages from the same src rpm, it would be nice if yum tried harder to do a consistent downgrade by downgrading the related packages rather than by starting to erase things, which can cascade into removing most of one's system. The work around for this is to find the related packages and explicitly downgrade them all, so it isn't a very important feature. But I think it would be a nice touch if someone eventually has time to include it. For example today I needed to downgrade glibc to work around a sound problem and after getting the old version (all of the rpms generated from the glibc srpm) into a local repo, I tried: yum downgrade glibc despite knowing better. glibc-common was downgraded, but then things starting showing up on the erase list. I killed this off before seeing the entire list of packages proposed for removal as I knew I wasn't going to want to do that. Then I did what I should have done in the first place: yum downgrade glibc glibc-common glibc-devel glibc-headers glibc-static glibc-utils nscd And that only downgraded the packages in that list. My request is that the shortcut I tried should really work like the more expanded version. Version-Release number of selected component (if applicable): Currently yum-3.2.25-7.fc13.noarch doesn't do this. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Yeh, we know about it ... but we don't think it's easy to fix. A couple of workarounds to make it more bearable are: 1. You can run: yum downgrade 'glibc*'. 2. Try to do smaller transactions, and then you can use "yum history undo" to downgrade (we're also looking at ways we can make it easier to do N small transactions instead of a large one). ...but, as always, patches are welcome ;).
*** Bug 631291 has been marked as a duplicate of this bug. ***
*** Bug 669810 has been marked as a duplicate of this bug. ***
yum and related packages are no longer actively developed. They are being replaced with dnf, dnf-utils, etc. I'm closing this bug because it's most likely never going to be fixed. If you still consider your bug report important, reopen it, please.