From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.8) Gecko/20051228 Fedora/1.5-3.fc4.remi Firefox/1.5 Description of problem: Updating to a new "epoch" is not handle. If a package change of epoch (ex : php-pear 0:4.3.11 to 1:1.4.5) yum doesn't update it. Version-Release number of selected component (if applicable): yum-2.2.2-0.fc3 How reproducible: Always Steps to Reproduce: 1. Try to upgrade to php 5.1 (rebuild from rawhide) from a depot 2. 3. Actual Results: php-pear not selected for update Expected Results: php-pear selected Additional info: Yum 2.4.1 works perfectly in this situation.
Can you give me the specific case and outputs of: yum list | grep php on the system where it would not update for you? also the output of yum -d5 update php would help. thanks
Created attachment 122851 [details] yum --enablerepo=remi list | grep php | sort php-pear.noarch (1:1.4.5-2.fc3.remi remi) is detected.
Created attachment 122852 [details] yum --enablerepo=remi list -d5 update Does the architecture explain the problem ? php-pear 0:5.0.4 is i386 php-pear 1:1.4.5 is noarch
in yum 2.2.X, yes, it does. 2.2.x had exactarch=1 on by default so no package could change arch on an upgrade. (it's dangerous behavior for some specific packages) That was adjusted in 2.4.X to be a list of package names which could not change arch, everything else, could. So this isn't really a bug for 2.2.X, it was intended and expected behavior.