mythtv has been updated to mythtv-0.27.5_p20150904 with no update to mythplugins, resulting in a conflict when emerging mythv. Reproducible: Always Steps to Reproduce: 1.emerge mythv -a 2. 3. Actual Results: WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: media-tv/mythtv:0 (media-tv/mythtv-0.27.5_p20150904:0/0::gentoo, ebuild scheduled for merge) conflicts with =media-tv/mythtv-0.27.5_p20150627*:0/0=[alsa,-hls,-ieee1394,-libass,python,theora,vorbis,xml,xvid] required by (media-plugins/mythplugins-0.27.5_p20150627-r1:0/0::gentoo, installed) ^ ^^^^^^^^^^^^^^^^^ =media-tv/mythtv-0.27.5_p20150627*:=[alsa,-hls,-ieee1394,-libass,python,theora,vorbis,xml,xvid] required by (media-plugins/mythplugins-0.27.5_p20150627-r1:0/0::gentoo, installed) ^ ^^^^^^^^^^^^^^^^^ Expected Results: Successful emerge of mythtv-0.27.5_p20150904
Thanks for the report. Fixed in http://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ea1b1246ef22f5ed6bfe89295c29656fa3d0d839
I don't believe upstream guarantees that any version of mythplugins-0.27.x is compatible with any version of mythtv-0.27. Generally mythtv requires the same protocol version throughout an installation, and they go further and consider an install unsupported if it isn't an identical build throughout. Protocol versions do change within a fixes branch. I was planning on fixing this once I got to test the new release by publishing a mythplugins-0.27.5_p20150904, even if it is identical to the current version. Do you have any objections to this solution and reverting the change you made?
(In reply to Richard Freeman from comment #2) > I don't believe upstream guarantees that any version of mythplugins-0.27.x > is compatible with any version of mythtv-0.27. Generally mythtv requires > the same protocol version throughout an installation, and they go further > and consider an install unsupported if it isn't an identical build > throughout. Protocol versions do change within a fixes branch. > > I was planning on fixing this once I got to test the new release by > publishing a mythplugins-0.27.5_p20150904, even if it is identical to the > current version. > > Do you have any objections to this solution and reverting the change you > made? The protocol doesn't change from what I've seen in a fixes branch for a 0.27.x version. So realistically any 0.27.5 plugins should work with any 0.27.5 MythTV. But if you want to undo it go for it. I would still keep the sub-slot configuration since the old ebuild had a sub-slot depend but we always set it to 0.
(In reply to Doug Goldstein from comment #3) > > The protocol doesn't change from what I've seen in a fixes branch for a > 0.27.x version. So realistically any 0.27.5 plugins should work with any > 0.27.5 MythTV. Likely, but the dependency is for >= 0.27, which includes 0.27.1, or 0.27.999. > I would still keep the > sub-slot configuration since the old ebuild had a sub-slot depend but we > always set it to 0. No argument there.
(In reply to Richard Freeman from comment #4) > (In reply to Doug Goldstein from comment #3) > > > > The protocol doesn't change from what I've seen in a fixes branch for a > > 0.27.x version. So realistically any 0.27.5 plugins should work with any > > 0.27.5 MythTV. > > Likely, but the dependency is for >= 0.27, which includes 0.27.1, or > 0.27.999. True we don't really have a ~mythtv-0.27.5 that would accept any _pXXXXXX do we? ~ will just accept any -rX if I recall. So yeah it's better to go back and put a plugins ebuild in. You're right.
Fixed with https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e3056e3803a209239da313162bf3193a6b796ff6
