Description of problem: trying to upgrade, I'm getting broken dependencies Version-Release number of selected component (if applicable): megaglest-3.7.1-1.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. install old F17 (i.e. without updates) 2. yum upgrade --skip-broken 3. yum upgrade Actual results: --> Running transaction check ---> Package glest.x86_64 0:3.2.2-10.fc17 will be obsoleted --> Processing Dependency: glest >= 3.2.1 for package: glest-data-3.2.1-5.fc17.noarch ---> Package megaglest.x86_64 0:3.7.1-1.fc17 will be obsoleting --> Processing Dependency: megaglest-data = 3.7.1 for package: megaglest-3.7.1-1.fc17.x86_64 --> Processing Dependency: p7zip for package: megaglest-3.7.1-1.fc17.x86_64 --> Processing Dependency: libxerces-c.so.27()(64bit) for package: megaglest-3.7.1-1.fc17.x86_64 --> Processing Dependency: libminiupnpc.so.8()(64bit) for package: megaglest-3.7.1-1.fc17.x86_64 --> Processing Dependency: libircclient.so.0()(64bit) for package: megaglest-3.7.1-1.fc17.x86_64 --> Running transaction check ---> Package glest.x86_64 0:3.2.2-10.fc17 will be obsoleted --> Processing Dependency: glest >= 3.2.1 for package: glest-data-3.2.1-5.fc17.noarch ---> Package libircclient.x86_64 0:1.6-3.fc17 will be installed ---> Package megaglest-data.noarch 0:3.7.1-1.fc17 will be installed ---> Package miniupnpc.x86_64 0:1.6-6.fc17 will be installed ---> Package p7zip.x86_64 0:9.20.1-3.fc17 will be installed ---> Package xerces-c27.x86_64 0:2.7.0-10.fc17 will be installed --> Finished Dependency Resolution Error: Package: glest-data-3.2.1-5.fc17.noarch (@fedora) Requires: glest >= 3.2.1 Removing: glest-3.2.2-10.fc17.x86_64 (@fedora) glest = 3.2.2-10.fc17 Obsoleted By: megaglest-3.7.1-1.fc17.x86_64 (updates) Not found Expected results: no errors Additional info: seems that megaglest-data forgot to obsolete glest-data ...?
(In reply to comment #0) > Description of problem: > trying to upgrade, I'm getting broken dependencies [...] > Error: Package: glest-data-3.2.1-5.fc17.noarch (@fedora) > Requires: glest >= 3.2.1 > Removing: glest-3.2.2-10.fc17.x86_64 (@fedora) > glest = 3.2.2-10.fc17 > Obsoleted By: megaglest-3.7.1-1.fc17.x86_64 (updates) > Not found > > > Expected results: > no errors > > Additional info: > seems that megaglest-data forgot to obsolete glest-data ...? I noticed it also and already commited a fix, see current last commit in all branches of http://pkgs.fedoraproject.org/cgit/megaglest-data.git/ but did not yet rebuild as I was waiting for some feedback on https://bugzilla.redhat.com/show_bug.cgi?id=889685 as that could require a new upstream release (unless those conditions are specific to my setup) but it may take some time. I will submit a megaglest-data update to correct the upgrade problem.
megaglest-data-3.7.1-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/megaglest-data-3.7.1-2.fc16
megaglest-data-3.7.1-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/megaglest-data-3.7.1-2.fc17
megaglest-data-3.7.1-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/megaglest-data-3.7.1-2.fc18
I want to believe it is correct now, and the autoqa test failed is bogus (because it tests installing *only* megaglest-data), but that assuming that megaglest and megaglest-data are installed in the same transaction, so that megaglest obsoletes glest and megaglest-data obsoletes glest-data, otherwise, would need to hack a bit to have megaglest and megaglest-data obsoleting both, glest and glest-data.
Package megaglest-data-3.7.1-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing megaglest-data-3.7.1-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0248/megaglest-data-3.7.1-2.fc17 then log in and leave karma (feedback).
(In reply to comment #5) > I want to believe it is correct now, and the autoqa > test failed is bogus (because it tests installing *only* > megaglest-data), yes, it works for me now, thanks > but that assuming that megaglest > and megaglest-data are installed in the same transaction, I guess it is safe to assume that because of the dependencies
Created attachment 674161 [details] sample empty glest.spec
Created attachment 674162 [details] Sample empty glest-data.spec
(In reply to comment #7) > > but that assuming that megaglest > > and megaglest-data are installed in the same transaction, > > I guess it is safe to assume that because of the dependencies That is what I expect, otherwise it would be "ugly" to have megaglest obsoleting glest-data, and megaglest-data obsoleting glest. I tested building a fake glest and glest-data package with the attached glest.spec and glest-data.spec, and updates did work correctly.
megaglest-data-3.7.1-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
megaglest-data-3.7.1-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
megaglest-data-3.7.1-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.