Bug 627387 - compat-db47 doesn't upgrade cleanly when compat-db-headers is installed
Summary: compat-db47 doesn't upgrade cleanly when compat-db-headers is installed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: compat-db
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-25 22:20 UTC by Michael Young
Modified: 2013-07-02 23:47 UTC (History)
3 users (show)

Fixed In Version: compat-db-4.7.25-17.fc14
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-04 05:21:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Young 2010-08-25 22:20:09 UTC
I was updating Fedora 14 and got the error
Transaction Check Error:
  file /usr/include/db4.7.25/db.h from install of compat-db47-4.7.25-16.fc14.x86_64 conflicts with file from package compat-db-headers-4.7.25-15.fc13.noarch

It looks like compat-db-headers has been removed as a separate package but the packaging of compat-db47 doesn't tell yum what to do if compat-db-headers is installed.

Comment 1 Fedora Update System 2010-08-26 17:39:59 UTC
compat-db-4.7.25-17.fc14 has been submitted as an update for Fedora 14.
http://admin.fedoraproject.org/updates/compat-db-4.7.25-17.fc14

Comment 2 Fedora Update System 2010-08-26 18:35:39 UTC
compat-db-4.7.25-17.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update compat-db'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/compat-db-4.7.25-17.fc14

Comment 3 Fedora Update System 2010-09-04 05:21:09 UTC
compat-db-4.7.25-17.fc14 has been pushed to the Fedora 14 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.