Bug 457241 - Transaction check error: conflict with redhat-lsb ....
Transaction check error: conflict with redhat-lsb ....
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: redhat-lsb (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Dmitry Butskoy
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-30 09:37 EDT by Tom London
Modified: 2008-07-31 08:29 EDT (History)
3 users (show)

See Also:
Fixed In Version: 3.1-21
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-31 08:29:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tom London 2008-07-30 09:37:26 EDT
Description of problem:
Got this with today's yum update.

Running rpm_check_debug
Running Transaction Test
Finished Transaction Test


Transaction Check Error:
  file /bin/mailx from install of mailx-12.3-1.fc10.i386 conflicts with file
from package redhat-lsb-3.1-19.fc8.i386

Error Summary
-------------

[root@localhost ~]# 


Version-Release number of selected component (if applicable):
mailx-12.3-1.fc10.i386
redhat-lsb-3.1-19.fc8.i386

How reproducible:
yes

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Dmitry Butskoy 2008-07-30 09:51:15 EDT
Yep, it is expected.

redhat-lsb will be changed soon accroding to my contacts with its maintainer.

Comment 2 Rex Dieter 2008-07-30 10:02:24 EDT
maybe this should be reassigned to redhat-lsb (unless there's something 
already assigned against it to track this?)
Comment 3 Dmitry Butskoy 2008-07-30 10:14:28 EDT
I already posted to Lawrence Lim today again (he reported me yesterday that he
will remove extra symlink in rawhide). I hope the issue will be fixed soon enough...
Comment 4 Lawrence Lim 2008-07-30 11:27:45 EDT
redhat-lsb-3_1-21_fc10 should fix it. My apologies for the delay.

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