Bug 680647 - qt: Local file conflict with packages on update
Summary: qt: Local file conflict with packages on update
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: qt
Version: 14
Hardware: i386
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 682010 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-26 17:45 UTC by David
Modified: 2013-01-10 06:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-14 10:45:46 UTC
Type: ---


Attachments (Terms of Use)

Description David 2011-02-26 17:45:09 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.started software update
2.clicked install updates
3.
  
Actual results:


Expected results:


Additional info:
Test Transaction Errors:   file /usr/lib/qt4/plugins/designer/libphononwidgets.so from install of qt-designer-plugin-phonon-1:4.7.1-17.fc14.i686 conflicts with file from package qt-x11-1:4.7.1-7.fc14.i686

Comment 1 Kevin Kofler 2011-02-28 16:25:38 UTC
qt-x11 should get upgraded too, why is it not? Is that a PackageKit or yum bug?

Comment 2 Rex Dieter 2011-02-28 16:33:47 UTC
designer-plugin-phonon indeed has this dep:
Requires: %{name}-x11%{?_isa} = %{?epoch:%{epoch}:}%{version}-%{release}

so qt-x11-4.7.1-17 should've been pulled into the transaction.

Comment 3 Kevin Kofler 2011-03-04 16:54:09 UTC
*** Bug 682010 has been marked as a duplicate of this bug. ***

Comment 4 Rex Dieter 2011-03-04 16:57:20 UTC
How are you updating?  yum?  packagekit?  other?

Comment 5 Rex Dieter 2011-03-04 17:41:03 UTC
OK, looks like both cases were packagekit.

Comment 6 Rex Dieter 2011-04-01 18:53:29 UTC
* Fri Mar 25 2011 Rex Dieter <rdieter> 1:4.7.2-6
- drop qt-designer-plugin-phonon

(this piece will be moved to phonon packaging soon)


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