On 01/12/17 16:47, Patrick Boutilier wrote:
On 12/01/2017 10:35 AM, John Pilkington wrote:
> On 01/12/17 14:04, Lukas Middendorf wrote:
>> On 28.11.2017 17:40, John Pilkington wrote:
>>> I should explain that I'm running a local build of mythtv master
>>> that is
>>> seen as a downgrade from the version in rpmfusion, and I don't want it
>>> overwritten. I haven't yet found a good change to the specfile, which
>>> seems fine in other respects.
>>
>> You could increase the rpm Epoch of your local mythtv build, so it is
>> seen as newer by yum.
>> If you already have an Epoch set in your spec simply increase that. If
>> you have not, set an epoch, add a line
>> "Epoch: 1"
>> (or what ever, I think even 0 is seen as higher as no epoch at all)
>> where you set the version.
>> And keep in mind that any sub-package-requirements now also have to be
>> changed to
>> "%{epoch}:%{version}-%{release}"
>> instead of
>> "%{version}-%{release}"
>>
> OK, thanks for that suggestion. ISTR 'epoch' being mentioned as a
> possibility before, but I hadn't experimented. You have given more
> details and I'll look at trying it for the next build.
>
> That could fix my specific 'feature', but won't fix dnfdragora. I'll
> give it a bit longer, but then maybe a BZ?
Same thing in Fedora 27 with dnfdragora . Doesn't matter what you select
for repositories, always shows the same updates available. Even when
running as root.
As an update: dnfdragora still does this (and had BZs aplenty when I
looked), but software-updates and/or yumex-dnf seem ok for me.
I've now built mythtv-master for both el7 and fc26 with an 'Epoch' and
don't see the pseudo-downgrades any more. The first attempt failed with
two conflicts, apparently resolved by expanding plain "%{version}"s for
a theme package as well. Thanks.
John P