DNF producing nonsense results (and a bogus F28 updates compose?)

[Andrew Lutomirski]

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                   Repository      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.

[Felix M. Cobos]

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                   Repository      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.

-- 
Felix M. Cobos

[Sérgio Basto]

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.

[Coge Micro]

It should be working fine already. I had same issues, but it seems fine
already and "dnf upgrade" passes without warnings.

On Sun, May 6, 2018 at 8:45 PM, Sérgio Basto <sergio(a)serjux.com&gt; wrote:

>  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.
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>

[Todd Zullinger]

Coge Micro wrote:
>  It should be working fine already. I had same issues, but it seems
> fine
>  already and "dnf upgrade" passes without warnings. 
You're just hitting a stale mirror. :)

The perl update which vim-enhanced and vim-X11 require is
still in testing:

    https://bodhi.fedoraproject.org/updates/FEDORA-2018-d1ba58394e

The rpmdeplint check of the vim update caught this, so I'm
not sure why vim got pushed to stable:

    https://bodhi.fedoraproject.org/updates/FEDORA-2018-fc49e5d1dc
   
https://taskotron.fedoraproject.org/artifacts/all/7894dee4-5086-11e8-a257...

Perhaps the maintainer thought it was a false failure?
(Unfortunately the test gating has been a bit bumpy so far,
so I wouldn't be too surprised if it got waived past
mistakenly).

-- 
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence.
    -- Jeremy S. Anderson

[Kalev Lember]

On Sun, May 6, 2018 at 7:24 AM, Andrew Lutomirski <luto(a)mit.edu&gt; 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                   Repository
>  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?
>  
I think you may have misread the line above. It's updating vim-common, and
removing vim-enhanced to make this possible.

Kalev