Bug 1576448 - slick-greeter breaks yum-cron after Fedora 28 upgrade
Summary: slick-greeter breaks yum-cron after Fedora 28 upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-cron
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-09 13:27 UTC by todd_lewis
Modified: 2018-05-09 20:21 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-09 16:07:59 UTC
Type: Bug


Attachments (Terms of Use)

Description todd_lewis 2018-05-09 13:27:20 UTC
Description of problem:
Since upgrading to Fedora 28, daily yum-cron updates fail with the following message:
  Failed to build transaction: slick-greeter-1.1.5-0.4.20180309gitfc13bd0.fc28.x86_64 requires (slick-greeter-cinnamon = 1.1.5-0.4.20180309gitfc13bd0.fc28 if cinnamon)

After "yum group upgrade "MATE Desktop"", yum-cron now fails with the message:
  Updates failed to install with the following error message: 
  Invalid version flag: if
I believe the "if" it's referring to is the one at the end of the first message above.


Version-Release number of selected component (if applicable):
slick-greeter-1.1.5-0.4.20180309gitfc13bd0.fc28.x86_64

How reproducible:
Extremely. All 6 of my Fedora 28 boxes are exhibiting the same behavior. They are all running MATE Desktop.

Steps to Reproduce:
1. dnf upgrade a MATE Desktop system from Fedora 27 to 28
2. run yum-cron
3.

Actual results:
yum-cron fails with "Failed to build transaction: slick-greeter-1.1.5-0.4.20180309gitfc13bd0.fc28.x86_64 requires (slick-greeter-cinnamon = 1.1.5-0.4.20180309gitfc13bd0.fc28 if cinnamon)"

Expected results:
List of successfully updated packages.

Additional info:

Comment 1 leigh scott 2018-05-09 16:07:33 UTC
If you choose to use obsolete yum you can expect issues like this as it can't handle recent rpm changes.

Comment 2 leigh scott 2018-05-09 16:09:03 UTC
yum-cron is also orphaned so no one is going to fix this non issue.

Comment 3 todd_lewis 2018-05-09 20:21:36 UTC
The solution is to transition from yum-cron to dnf-automatic like so:

sudo dnf install dnf-automatic
sudo $EDITOR /etc/dnf/automatic.conf
for action in status enable start status ; do
   sudo systemctl $action dnf-automatic-install.timer
done
sudo dnf erase yum-cron

yum has been using dnf on the back end for some time. I didn't realize that yum-cron wasn't doing the same. yum-cron is fresh-built for F28, distributed, but doomed-to-fail package.

Thanks for the clues. Maybe someone else will find the above useful.


Note You need to log in before you can comment on or make changes to this bug.