Description of problem: I've updated from fc10 to fc11 to fc12. In trying to 'yum update' recently, I ran into this problem: Downloading Packages: Running rpm_check_debug ERROR with rpm_check_debug vs depsolve: python(abi) = 2.5 is needed by (installed) hulahop-1:0.4.6-5.fc10.x86_64 Complete! (1, [u'Please report this error in http://yum.baseurl.org/report']) Version-Release number of selected component (if applicable): The install set was: Updating: tkinter x86_64 2.6.2-4.fc12 updates 242 k Updating for dependencies: python x86_64 2.6.2-4.fc12 updates 4.6 M python-devel x86_64 2.6.2-4.fc12 updates 854 k python-libs x86_64 2.6.2-4.fc12 updates 609 k --- The odd thing is that the conflict is for a fc10 package (hulahop-1:0.4.6-5.fc10.x86_64) and I have the fc12 package installed (hulahop-0.6.0-2.fc12.x86_64). So this looks like an upgrade issue. How reproducible: I haven't tried. Steps to Reproduce: 1. Install fc10 with hulahop 2. Update to fc12 3. sudo yum update python
Here's some oddness: [jeremy@tifa-linux ~]$ sudo yum install hulahop Loaded plugins: dellsysidplugin2, refresh-packagekit Setting up Install Process Package matching hulahop-0.6.0-2.fc12.x86_64 already installed. Checking for update. Nothing to do [jeremy@tifa-linux ~]$ rpm -q hulahop hulahop-0.4.6-5.fc10.x86_64
And here are a list of others that haven't updated to their fc12 versions: [jeremy@tifa-linux ~]$ rpm -q -a | grep fc10 compat-db45-4.5.20-5.fc10.x86_64 hulahop-0.4.6-5.fc10.x86_64 libdhcp4client-4.0.0-36.fc10.x86_64 [jeremy@tifa-linux ~]$ rpm -q -a | grep fc11 libvolume_id-141-7.fc11.x86_64 xml-commons-which-javadoc-1.0-2.b2.0.3.fc11.x86_64 google-gadgets-0.11.1-3.fc11.x86_64 xml-commons-which-1.0-2.b2.0.3.fc11.x86_64 puretls-javadoc-0.9-0.3.b5.5.2.fc11.x86_64 cryptix-javadoc-3.2.0-12.fc11.x86_64 mod_dnssd-0.6-2.fc11.x86_64 goffice04-0.4.3-5.fc11.x86_64 google-gadgets-qt-0.11.1-3.fc11.x86_64 cryptix-asn1-javadoc-20011119-10.fc11.x86_64 python-json-3.4-6.fc11.noarch
*** Bug 584972 has been marked as a duplicate of this bug. ***
On F12 repoquery says hulahop-0:0.6.0-2.fc12.x86_64 but... python(abi) = 2.5 is needed by (installed) hulahop-1:0.4.6-5.fc10.x86_64 ^^ Hulahop had an epoch, but it's been dropped at some point after F10. Once introduced, you can never remove an epoch, short of renaming the package.
Sorry for the dupe. I thought I had reported this but couldn't find it. So hulahop on fc11, rc12, and fc13 should be epoch-bumped to match the "1" that was in fc10 ... seems like an easy enough fix...
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #5) > Sorry for the dupe. I thought I had reported this but couldn't find it. > > So hulahop on fc11, rc12, and fc13 should be epoch-bumped to match the "1" that > was in fc10 ... seems like an easy enough fix... Oh, an epoch can not be removed? Hmm, if that is the case I can add it again. Which versions should I fix it for? Still worth for F12 as well?
Might as well do it for FC12 since it's such a trivial fix and some people may need to be on it still...
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still relevant on all supported versions. Just bump the dang epoch already.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Yes, this is still an issue. Please bump the epoch.
closing as WONTFIX. afaict, the epoch was only present on one branch (F10). This bug is valid, but I expect that by now those users affected will have manually upgraded. F10 has been EOL for a while now so I think it's safe to just pretend it never happened. Fresh installs will get the updated version, this really only affects those that had that version from F10 installed and updated manually since.
It might be worth seeing if running ``yum downgrade hulahop'' on an affected system causes it to install the latest version that lacks the epoch instead.