On 24/08/17 10:59, Patrick O'Callaghan wrote:
On Thu, 2017-08-24 at 09:03 +0100, Christopher Ross wrote:
> On 23/08/17 14:27, Ed Greshko wrote:
>> On 08/23/2017 08:40 PM, Bob Goodwin wrote:
>>> # dnf upgrade
>>> Last metadata expiration check: 0:00:00 ago on Wed Aug 23 04:43:05 2017.
>>> Dependencies resolved.
>>>
>>> Problem: cannot install the best update candidate for package
>>> firefox-55.0.1-1.fc26.x86_64
>>> - nothing provides nspr >= 4.16.0 needed by
firefox-55.0.2-1.fc26.x86_64
>>
>>
>> nspr is still in updates-testing. If you want you can run "dnf
--enablerepo
>> updates-testing update firefox"
>
> Thank you! I have just done that. Because dnf wasn't able to update
> Firefox to the best version it removed it instead! I assume this is a
> result of the combination --best --allowerasing which I generally use.
> I've never had it just remove things completely leaving no version
> installed though :(
That doesn't look right. AFAIK "--allowerasing" will delete a package
that is blocking something else from updating, but not otherwise. It
shouldn't remove a package just because it can't get the latest
version.
Well that is exactly what happened. The command
dnf --refresh --best --allowerasing upgrade
Could not update Firefox because of the missing dependency (nspr) so it
removed Firefox completely instead. This is not what I expected to
happen. This is the command I generally use to update the system, pretty
much daily.
Subsequently entering the command
dnf install firefox
installed firefox.x86_64 54.0-2.fc26, not the 55.0-1 that it removed.
I then followed Ed Greshko's advice (above) to enable the
updates-testing repository to get the required dependency and that
worked, so that I now have firefox.x86_64 55.0.2-1.fc26 installed.
Regards,
Chris R.