On Thu, 2017-08-24 at 13:59 +0100, Christopher Ross wrote:
On 24/08/17 13:48, Patrick O'Callaghan wrote:
>
> The man page for dnf says: "Allow erasing of installed packages to
> resolve dependencies" (which is actually not as clear as it might be -
> would removing every package on the system resolve dependencies?).
>
> However that is consistent with what it did in your case. It removed FF
> because it couldn't update nspr, not "Because dnf wasn't able to
update
> Firefox to the best version it removed it instead", which is the phrase
> I was reacting to.
I disagree. It could not install the updated Firefox because it depends
on a version of nspr that has not been released yet. Removing the
currently installed Firefox did not resolve any dependencies at all. At
best, that would imply that it needed to uninstall Firefox because it
was blocking the update of something else, which so far as I can tell is
not the case.
Or, if that is the case, which packages in the current update DO depend
on the newest version of Firefox, which in turn depends on a package
that hasn't been released yet? Surely under your interpretation they
would have been removed too?
I think the exact meaning of the man-page phrase is unclear, so I for
one can't tell if what happened is a bug or a feature. Either way, I'd
suggest you file it as a bug against dnf and maybe someone will react.
poc