On Sun, 2018-05-06 at 07:33 +0200, Felix M. Cobos wrote:
On Sat, May 05, 2018 at 09:24:15PM -0700, Andrew Lutomirski wrote:
> I just got some very strange behavior from dnf:
>
> $ sudo dnf upgrade --best --allowerasing
> Last metadata expiration check: 0:04:26 ago on Sat 05 May 2018
> 09:13:56 PM PDT.
> Dependencies resolved.
> ===================================================================
> =============
> Package Arch Version Reposito
> ry Size
> ===================================================================
> ============$
> Upgrading:
> vim-common x86_64 2:8.0.1788-
> 1.fc28 updates 6.4 M
> Removing:
> vim-enhanced x86_64 2:8.0.1763-
> 1.fc28 @updates 2.9 M
>
> Somehow dnf's solution was to upgrade vim-enhanced and them
> immediately remove it. How does that make sense?
>
> This was triggered by the following problem with the repo:
>
> Problem 1: cannot install the best update candidate for package
> vim-enhanced-2$
> 8.0.1763-1.fc28.x86_64
> - nothing provides perl(:MODULE_COMPAT_5.26.2) needed by vim-
> enhanced-2:8.0.1$
> 88-1.fc28.x86_64
> Problem 2: package vim-enhanced-2:8.0.1763-1.fc28.x86_64 requires
> vim-common =
> 2:8.0.1763-1.fc28, but none of the providers can be installed
> - cannot install both vim-common-2:8.0.1788-1.fc28.x86_64 and
> vim-common-2:8.$
> .1763-1.fc28.x86_64
> - problem with installed package vim-enhanced-2:8.0.1763-
> 1.fc28.x86_64
> - cannot install the best update candidate for package vim-
> common-2:8.0.1763-$
> .fc28.x86_64
> - nothing provides perl(:MODULE_COMPAT_5.26.2) needed by vim-
> enhanced-2:8.0.1$
> 88-1.fc28.x86_64
>
> but I don't see how it makes sense at all.
It seems like vim-enhanced depends on perl 5.26.2 but it hasn't been
pushed to stable.
if so, (you need some packages from updates-testing to complete dnf
upgrade) you can quickly workaround with [1] :
[1]
dnf upgrade --best --allowerasing --enablerepo=updates-testing vim-
common
--
Sérgio M. B.