On Tue, 3 Oct 2017, Konstantin Olchanski wrote:
> It is prudent to "yum erase libgpod" beforehand, or good chance
> yum will consume all ram and go into some kind of loop over dependancies.
Perhaps should have a local 'blacklist'
Conflicts: libgpod
in the 7.4 sl-release file then? That way one would not
inadvertently run into the issue
... and of course adding to the Release Notes the
explanation of WHY a simple:
yum clean all ; yum update
better requires that erasure manually first
-- Russ herrold
