Bug 1663341 - dnf & hplip is confused - what is going on?
Summary: dnf & hplip is confused - what is going on?
Keywords:
Status: CLOSED DUPLICATE of bug 1661922
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-03 22:41 UTC by John Dodson
Modified: 2019-01-04 08:21 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-04 08:21:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Dodson 2019-01-03 22:41:53 UTC
Description of problem:
dnf & hplip is confused - what is going on?


Version-Release number of selected component (if applicable):

Installed Packages
hplip.x86_64                       3.18.3-1.fc28                         @fedora
Available Packages
hplip.x86_64                       3.18.6-11.fc28                        updates

How reproducible:
just allow updates.

Steps to Reproduce:
1. dnf update.
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 hplip-common             x86_64     3.18.6-11.fc28          updates      110 k
Skipping packages with broken dependencies:
 hplip                    x86_64     3.18.6-11.fc28          updates       16 M
 hplip-gui                x86_64     3.18.6-11.fc28          updates      1.3 M
 hplip-libs               x86_64     3.18.6-11.fc28          updates      204 k
 libsane-hpaio            x86_64     3.18.6-11.fc28          updates      127 k


2.
If it updates other conflicts occur later - been happening on & off for a while (before Xmas)

3.

Actual results:

Conflicts

Expected results:

No conflicts

Additional info:

Comment 1 Zdenek Dohnal 2019-01-04 08:21:51 UTC
Hi John,

thank you for reporting the issue! It is actually known issue as https://bugzilla.redhat.com/show_bug.cgi?id=1661922 , which is solved by today's update, so '$ sudo dnf -y upgrade' fixes it now. I'm sorry for caused problems.

*** This bug has been marked as a duplicate of bug 1661922 ***


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