Bug 928950

Summary: emacs update runs afoul of info package
Product: [Fedora] Fedora Reporter: Michal Jaegermann <michal>
Component: emacsAssignee: Petr Hracek <phracek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jonathan.underwood, phracek, tmz
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-29 07:53:55 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:
Bug Depends On:    
Bug Blocks: 928328    

Description Michal Jaegermann 2013-03-28 19:19:59 UTC
Description of problem:

An attempted update which includes the current emacs packages fails with the following:

Transaction check error:
  file /usr/share/info/info.info.gz from install of emacs-common-1:24.3-1.fc20.x86_64 conflicts with file from package info-5.1-1.fc20.x86_64

Version-Release number of selected component (if applicable):
emacs-24.3-1.fc20

Additional info:
One would think that a documentation on using a stand-alone info reader indeed belongs to a package like 'info' and not to 'emacs-common'

Comment 1 Todd Zullinger 2013-03-28 22:45:09 UTC
This also prevents building packages which BR emacs, like git.

http://koji.fedoraproject.org/koji/taskinfo?taskID=5181474

Specifically, the tail of mock's root.log:

http://koji.fedoraproject.org/koji/getfile?taskID=5181474&name=root.log&offset=-4000

DEBUG util.py:264:  Transaction Check Error:
DEBUG util.py:264:    file /usr/share/info/info.info.gz from install of emacs-common-1:24.3-1.fc20.x86_64 conflicts with file from package info-5.1-1.fc20.x86_64
DEBUG util.py:264:  Error Summary

Comment 2 Petr Hracek 2013-03-29 07:53:55 UTC

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