Bug 1470547 - conflict error, Install failed.
Summary: conflict error, Install failed.
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: foo2zjs
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christopher Atherton
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-13 07:39 UTC by mejiko
Modified: 2018-06-06 13:31 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-28 15:44:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description mejiko 2017-07-13 07:39:01 UTC
I try install foo2hiperc. but install is failed. 
because "conflict error".


[Infomation]


foo2hiperc rpm is:

foo2hiperc-0.20170412-2.fc26.x86_64


conflict rpm is:

foomatic-db-4.0-52.20161003.fc26.noarch 


Conflict files:

/usr/share/foomatic/db/source/driver/foo2hiperc-z1.xml


I suggest that resolve install error problem.
Thanks.

Comment 1 Eduardo 2017-07-30 03:21:08 UTC
Hello,

I have the same problem but while trying to upgrade from F25 to F26:
$ sudo dnf system-upgrade download --refresh --releasever=26 --allowerasing
...
...
Error: Transaction check error:
  file /usr/share/foomatic/db/source/driver/foo2hiperc-z1.xml conflicts between attempted installs of foo2hiperc-0.20170412-2.fc26.x86_64 and foomatic-db-4.0-52.20161003.fc26.noarch

Error Summary
-------------

My current installed rpms are:
$ rpm -q foo2hiperc foomatic-db
foo2hiperc-0.20170412-2.fc25.x86_64
foomatic-db-4.0-50.20150819.fc24.noarch


Thank you,
Eduardo

Comment 2 Fedora End Of Life 2018-05-03 07:57:11 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora Update System 2018-05-28 14:16:53 UTC
foomatic-db-4.0-58.20180102.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-582bb1b468

Comment 4 Zdenek Dohnal 2018-05-28 15:44:59 UTC
Issue will be fixed in F27 by removing foo2hiperc-z1 from foomatic-db. See https://bugzilla.redhat.com/show_bug.cgi?id=1582865

Comment 5 Fedora Update System 2018-05-29 13:12:37 UTC
foomatic-db-4.0-58.20180102.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-582bb1b468

Comment 6 Fedora Update System 2018-06-06 13:31:28 UTC
foomatic-db-4.0-58.20180102.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.


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