Bug 508418 - libwvstreams-devel multilib conflict
Summary: libwvstreams-devel multilib conflict
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libwvstreams
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-26 22:55 UTC by Philippe Troin
Modified: 2009-07-16 07:26 UTC (History)
1 user (show)

Fixed In Version: 4.5.1-6.fc11
Clone Of:
Environment:
Last Closed: 2009-07-16 07:26:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Philippe Troin 2009-06-26 22:55:23 UTC 
Description of problem:

yum install libwvstreams-devel.i586 libwvstreams-devel.x86_64 

yields:

Transaction Check Error:
  file /usr/include/wvstreams/wvautoconf.h from install of libwvstreams-devel-4.5.1-5.fc11.i586 conflicts with file from package libwvstreams-devel-4.5.1-5.fc11.x86_64


Version-Release number of selected component (if applicable):
libwvstreams-devel-4.5.1-5.fc11
Comment 1 Ondrej Vasik 2009-06-27 10:47:00 UTC 
Thanks for report, HAVE_LIBC_STACK_END differs. Will check what's the best way to solve it later.
Comment 2 Fedora Update System 2009-06-27 16:39:10 UTC 
libwvstreams-4.5.1-6.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/libwvstreams-4.5.1-6.fc11
Comment 3 Fedora Update System 2009-06-30 21:29:08 UTC 
libwvstreams-4.5.1-6.fc11 has been pushed to the Fedora 11 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 libwvstreams'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7100
Comment 4 Fedora Update System 2009-07-16 07:26:17 UTC 
libwvstreams-4.5.1-6.fc11 has been pushed to the Fedora 11 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.