Bug 959729

Summary:	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
Product:	[Fedora] Fedora	Reporter:	Jay Finger <jay.finger>
Component:	ht	Assignee:	Andreas Bierfert <andreas.bierfert>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	andreas.bierfert, linuxedhorse
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-05 06:28:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.