Bug 959729 - YumRPMTransError Could not run transaction : file /usr/bin/ht conflicts between attempted installs of ht-2.0.18-4.fc19.x86_x64 and texlive-tex4ht-bin-2:svn26509.0-22.20130427_r30134.fc19.x86_64
Summary: YumRPMTransError Could not run transaction : file /usr/bin/ht conflicts betwe...
Keywords:
Status: CLOSED DUPLICATE of bug 954086
Alias: None
Product: Fedora
Classification: Fedora
Component: ht
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-05 06:25 UTC by Jay Finger
Modified: 2014-02-18 18:19 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-05 06:28:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jay Finger 2013-05-05 06:25:41 UTC
Description of problem:

Installation fails with message that isn't helpful in diagnosing problem.

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

Fedora-19-Beta-TC3-x86_64-netinst.iso

How reproducible:

every time

Steps to Reproduce:
1. Select GNOME Desktop, then select all the additional package for that environment.
  
Actual results:

a box that says "The following error occurred while installing.  This is a fatal error and installation will be aborted.  YumRPMTransError Could not run transaction

Expected results:

successful installation, or at the very least some UI that prevents me from selecting conflicting packages.

Additional info:
In /tmp/packaging.log I see:
01:16:01,811 DEBUG packaging: Transaction couldn't start:
01:16:01,813 DEBUG packaging: file /usr/bin/ht conflicts between attempted installs of ht-2.0.18-4.fc19.x86_x64 and texlive-tex4ht-bin-2:svn26509.0-22.20130427_r30134.fc19.x86_64
01:16:01.813 ERR packaging:  YumRPMTransError Could not run transaction.

Comment 1 Jay Finger 2013-05-05 06:28:32 UTC

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

Comment 2 Kazooza 2014-02-18 18:19:16 UTC
Bug is still exist.


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