Bug 613865 - /usr/share/gdb/auto-load/usr/lib/libstdc++.so.6.0.14-gdb.py conflicts between attempted installs of libstdc++-4.5.0-2.fc14 and gdb-7.1-28.fc14
Summary: /usr/share/gdb/auto-load/usr/lib/libstdc++.so.6.0.14-gdb.py conflicts between...
Status: CLOSED DUPLICATE of bug 613710
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Kratochvil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-13 01:57 UTC by Jens Petersen
Modified: 2010-07-13 06:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-13 06:37:49 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Jens Petersen 2010-07-13 01:57:19 UTC
Description of problem:
Rawhide has a conflict now between libstdc++ and gdb.

Version-Release number of selected component (if applicable):
libstdc++-4.5.0-2.fc14
gdb-7.1-28.fc14

Steps to Reproduce:
1. Yum update rawhide
  
Actual results:
See https://bugzilla.redhat.com/show_bug.cgi?id=612720#c4

Transaction Check Error:
  file /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.14-gdb.py conflicts
between attempted installs of libstdc++-4.5.0-2.fc14.x86_64 and
gdb-7.1-28.fc14.x86_64
  file /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.14-gdb.pyc conflicts
between attempted installs of libstdc++-4.5.0-2.fc14.x86_64 and
gdb-7.1-28.fc14.x86_64
  file /usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.14-gdb.pyo conflicts
between attempted installs of libstdc++-4.5.0-2.fc14.x86_64 and
gdb-7.1-28.fc14.x86_64

Expected results:
No conflict and being able to install or spin rawhide.

Comment 1 Jan Kratochvil 2010-07-13 06:37:49 UTC

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


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