Bug 953179 - Transaction check error on colord update
Summary: Transaction check error on colord update
Keywords:
Status: CLOSED DUPLICATE of bug 928117
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ales Kozumplik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-17 14:29 UTC by Richard Marko
Modified: 2016-02-01 02:22 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-17 14:49:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dnf output (243.39 KB, text/plain)
2013-04-17 14:29 UTC, Richard Marko
no flags Details

Description Richard Marko 2013-04-17 14:29:49 UTC
Created attachment 736884 [details]
dnf output

Description of problem:

Transaction Check Error:
  file /usr/lib64/girepository-1.0/Colord-1.0.typelib from install of colord-libs-0.1.31-1.fc18.x86_64 conflicts with file from package colord-0.1.25-1.fc18.x86_64
  file /usr/lib64/libcolord.so.1 from install of colord-libs-0.1.31-1.fc18.x86_64 conflicts with file from package colord-0.1.25-1.fc18.x86_64


Version-Release number of selected component (if applicable):
dnf-0.2.22-1.git97180b8.fc18.noarch
hawkey-0.3.8-1.git046ab1c.fc18.x86_64

How reproducible:
Always

Comment 1 Ales Kozumplik 2013-04-17 14:32:23 UTC
ah,

I think I know what's happening here (bug 928117).

what does 'dnf list installed libsolv' show?

Comment 2 Richard Marko 2013-04-17 14:39:53 UTC
libsolv.x86_64                     0.2.3-1.gitf663ca2.fc18                     @System

Comment 3 Ales Kozumplik 2013-04-17 14:49:56 UTC
this is a different manifestation of bug 928117. even though libsolv can see the colord package, it leaves it from the update (according to the output you attached). and then the transaction fails on conflicting files because the old colord is still present and in the new version it was moved into the colord-libs package.

Anyway, thanks for the report, there might be more people bitten by it. I don't plan to fix this in F18 but it already is fixed in the F19 builds.

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


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