On Thu, 2008-09-18 at 22:55 +0200, Nikola Ciprich wrote:
> Hello everybody,
> some time ago, I asked here for help, because I can't get allowdowngrade plugin
> working. We didn't come to any conclusion, and I didn't have time to play with
> it anymore, but now I got back to it, and I'd like to ask for bit of explanation.
> I did a bit of exploring, and I'm a bit confused. It seems that allowdowngrade adds
> hooks to postresolve, but if I try to install package, yum just doesn't get there
> at all, so plugin can't really change anything.
> It seems that it ends in yum/__init__.py, after line 2392 (install method):
>
> # make sure we don't have a name.arch of this already installed
> # if so pass it to update b/c it should be able to figure it out
> if self.rpmdb.contains(name=po.name, arch=po.arch) and not self.allowedMultipleInstalls(po):
> if not self.tsInfo.getMembersWithState(po.pkgtup, TS_REMOVE_STATES):
> self.verbose_logger.warning(_('Package matching %s already installed. Checking for update.')
> txmbrs = self.update(po=po)
> tx_return.extend(txmbrs)
> continue
>
> self.update(po=po) returns empty list, which causes package to be skipped. Is this intended behaviour?
> Should I be looking elsewhere?
> I'm using latest yum and yum-allowdowngrade
> Any ideas?
> thanks a lot in advance!
> with best regards
Nope, I think you're on the right path. Making sure allowdowngrade
semi-behaves is on my list to fix before 3.2.20 comes out.
If you can fix it w/o breaking more things please send a patch you may
have.
-sv
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum
