Description of problem: Version-Release number of selected component (if applicable): 0.9.97-5.fc17 How reproducible: Always Steps to Reproduce: 1. Upgrade to F17 from F18 2. yum list kdiff\* 3. yum update kdiff\* Actual results: [root@localhost ~]# yum list kdiff\* Loaded plugins: langpacks, presto, refresh-packagekit Installed Packages kdiff3.x86_64 0.9.97-5.fc17 @updates/17 [root@localhost ~]# yum update kdiff\* Loaded plugins: langpacks, presto, refresh-packagekit No Packages marked for Update Expected results: Update to F18 version Additional info: In the F17 branch, the kdiff3 version was bumped to -5 without explanation, whereas F18 (and master) sit at -4. This is the source of the problem.
Just in case anyone else is wondering: There are new builds for f19(rawhide) and f18 which would resolve the bug once they are pushed. Since the bug got closed NEXTRELEASE I can only assume that the intention is to push to rawhide but not f18-updates. I don't want to be a nuisance, but bugzilla gives as ON_QA and such to make it clear what's happening. fedpkg update takes care of updating bugs it's been told about (in case the intention is to push this to the f18 which it was reported against; in this case it will closed ERRATA, not NEXTRELEASE, once the update made it all the way to the updates repo). Not to mention koji links or even textual comments ;) So, without further pestering on closed vs. intended-to-be-closed, is the intention really to close this NEXTRELEASE, not ERRATA?
kdiff3-0.9.97-5.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kdiff3-0.9.97-5.fc18
Didn't know that - changed to closed errata.
Please add karma so this can be pushed to stable. Thanks.
(In reply to comment #4) > Please add karma so this can be pushed to stable. Thanks. Well, you can push it without karma, too.
kdiff3-0.9.97-5.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.