Hmm, maybe not a big deal as baloo is only in the kde for EPEL7 repo, but still seems a bit off.

baloo is provided by the base system and needed for KDE4, so indeed we should not obsolete, but find a way for them to co-exist (I think we did something like that in the beginning when Baloo was moved to Frameworks?).

baloo is not part of base system.

Icky.  

So yeah, I agree with Dan in comment #2, need to come up with a co-existence plan.

quick-n-dirty fix for now until we have something better:

%changelog
* Wed Apr 27 2016 Orion Poplawski <orion.com> - 5.21.0-2
- Do not obsolete/provide baloo{-file} in EPEL, use Conflicts (for now)
- update URL

kf5-baloo-5.21.0-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-8524df769c

kf5-baloo-5.21.0-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-8524df769c

Unfortunately we may need manual intervention:

---> Package kf5-baloo.x86_64 0:5.21.0-1.el7 will be updated
--> Processing Dependency: baloo >= 4.14.3-1.el7.centos for package: baloo-libs-4.14.3-1.el7.centos.x86_64
---> Package kf5-baloo.x86_64 0:5.21.0-2.el7 will be an update
--> Running transaction check
---> Package baloo.x86_64 0:4.14.3-1.el7.centos will be installed
--> Processing Conflict: kf5-baloo-5.21.0-2.el7.x86_64 conflicts baloo < 5

I can work around it with:

yum swap kf5-baloo baloo

I suppose for one release we to omit the Conflicts and not ship /usr/bin/baloo* in kf5-baloo.  This would allow users to update and then remove the kf5* packages without any fancy yum commands.

This will only affect users who had kf5-baloo installed since the last update, is that a large enough audience to be worth implementing more workarounds?

I thought there was more to conflicts than just the /usr/bin/baloo* stuff (but I could be wrong)

More thoughts:

I *think* kf5-baloo can work with baloo-libs-4.x too (that's why the baloo-libs dep is baloo >= 4.14).  

Actually, the Requires: baloo dep in baloo-libs could probably be dropped too

(sorry for comment spam), but for completeness, as far as conflicts go, the only other thing to worry about is:
/usr/share/icons/hicolor/*/apps/baloo.*

(In reply to Rex Dieter from comment #9)
> This will only affect users who had kf5-baloo installed since the last
> update, is that a large enough audience to be worth implementing more
> workarounds?

I really don't know - but it's everyone who is using the rdieter/kde4 COPR.  I know how to workaround it though so I'm fine either way.

> I thought there was more to conflicts than just the /usr/bin/baloo* stuff
> (but I could be wrong)

That's all that yum reported to me.  Looks like the icon is identical so no conflict there.

kf5-baloo-libs no longer requires kf5-baloo, and yeah that requires looks odd to me.

OK, so here's what I'm leaning towards...  going back to using Obsoletes then (with no kf5-baloo-libs dep on kf5-baloo)

I don't follow - there already is no dep on kf5-baloo from kf5-baloo-libs, and any obsoletes will pull in the kf5 stuff which I don't think is desirable.

kf5-baloo-5.21.0-5.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-8524df769c

kf5-baloo-5.21.0-5.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-8524df769c

kf5-baloo-5.21.0-5.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.