Since we're dropping libmusicbrainz4 in F19+, libmusicbrainz5 in F19+ should Obsolete it. How reproducible: Upgrade from F-18 to F-19, then run: [hans@shalem ~]$ sudo package-cleanup --orphans Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit libmusicbrainz4-4.0.3-3.fc18.x86_64 [hans@shalem ~]$ Given that the latest build of libmusicbrainz4 in koji is libmusicbrainz4-4.0.3-4.fc19, libmusicbrainz5 should add: Obsoletes: libmusicbrainz4 < libmusicbrainz4-4.0.3-5 Provides: libmusicbrainz4 = libmusicbrainz4-4.0.3-5
libmusicbrainz5 is not a drop-in replacement for libmusicbrainz4 (different sonames, ...), and I think both can be installed in parallel if needed). If the user has an external package built against libmusicbrainz4, this Obsoletes/Provides addition will cause breakage. I generally don't consider Obsoletes as a good way to automatically remove old packages on upgrades. Did you get any issues with these 2 libraries apart from the slightly higher disk space use?
(In reply to Christophe Fergeau from comment #1) > libmusicbrainz5 is not a drop-in replacement for libmusicbrainz4 I know. > and I think both can be installed in parallel if needed) Correct. > If the user has an external package built against libmusicbrainz4, this > Obsoletes/Provides addition will cause breakage. True, but we do the same often when we upgrade libraries to versions with a different soname as part of the regular package upgrade, ie libfoo-1.0 -> libfoo-2.0, without having any compat packages, like we use(d) to have for libmusicbrainz. Also otherwise the user will keep having an old unsupported package around, with no security updates, etc. > I generally don't consider Obsoletes as a good way to automatically remove > old packages on upgrades. It depends on the package, if it is being replaced by something else, which more or less is the case here. The Obsoletes / Provides make sense. > Did you get any issues with these 2 libraries apart from the slightly higher > disk space use? My biggest issue, from a user pov, is they are unsupported.
My $0.02, *If* you want cleanup of the unsupported libmusicbrainz4, then adding an Obsoletes is the way to go. But, I'd object to adding Provides: , libmusicbrainz5 is really no replacement (api or abi)
libmusicbrainz5-5.0.1-6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libmusicbrainz5-5.0.1-6.fc19
Package libmusicbrainz5-5.0.1-6.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libmusicbrainz5-5.0.1-6.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-10545/libmusicbrainz5-5.0.1-6.fc19 then log in and leave karma (feedback).
libmusicbrainz5-5.0.1-7.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/libmusicbrainz5-5.0.1-7.fc19
libmusicbrainz5-5.0.1-7.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.