Bug 1349671 - file conflict between libedit-devel and readline-devel
Summary: file conflict between libedit-devel and readline-devel
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libedit
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Boris Ranto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-23 23:57 UTC by George R. Goffe
Modified: 2016-06-28 16:28 UTC (History)
7 users (show)

Fixed In Version: libedit-3.1-16.20160618cvs.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-28 16:28:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description George R. Goffe 2016-06-23 23:57:11 UTC 
Description of problem:

/usr/share/man/man3/history.3.gz appears to be shared/owned by BOTH of these two pkgs which is causing the rpm (and dnf) command(s) to choke and puke. see below.

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

libedit-devel-3.1-15.20160618cvs.fc25.x86_64
readline-devel-6.3-8.fc24.x86_64 : Files needed to develop programs which use the readline library

How reproducible:

always

Steps to Reproduce:
1.dnf -y upgrade
2.
3.

Actual results:

see below

Expected results:


Additional info:

Error: Transaction check error:
  file /usr/share/man/man3/history.3.gz from install of libedit-devel-3.1-15.20160618cvs.fc25.x86_64 conflicts with file from package readline-devel-6.3-8.fc24.x86_64
Comment 1 Jan Kratochvil 2016-06-28 08:24:49 UTC 
It is only a symlink in libedit-devel, I believe libedit should remove it:

libedit-devel:
lrwxrwxrwx 1 root root 13 Jun 21 14:46 /usr/share/man/man3/history.3.gz -> editline.3.gz
readline-devel:
-rw-r--r-- 1 root root 7530 Feb 5 05:30 /usr/share/man/man3/history.3.gz
Comment 2 George R. Goffe 2016-06-28 15:22:43 UTC 
Jan,

Thanks for your help with this.

WIll the libedit people be taking this bug?

Regards,

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