Bug 1458416 - File conflicts between maxima-runtime-sbcl ans sbcl
Summary: File conflicts between maxima-runtime-sbcl ans sbcl
Keywords:
Status: CLOSED DUPLICATE of bug 1436856
Alias: None
Product: Fedora
Classification: Fedora
Component: rpm
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-02 19:17 UTC by Anton Guda
Modified: 2017-06-04 11:00 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-06-04 10:59:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Anton Guda 2017-06-02 19:17:06 UTC
Description of problem:
maxima-runtime-sbcl ans sbcl have symlinks
with the same name in /usr/lib/.build-id:
2b/58aae48c1c175070d930e3a5d91982d431625a.
So, install is impossible.


Version-Release number of selected component (if applicable):
maxima-runtime-sbcl-5.40.0-2.fc27.x86_64
sbcl-1.3.17-1.fc27.x86_64
Some previous versions too...

How reproducible:
Always.


Steps to Reproduce:
1. Try to install/update maxima with sbcl.

Actual results:
file /usr/lib/.build-id/2b/58aae48c1c175070d930e3a5d91982d431625a conflicts between attempted installs of sbcl-1.3.17-1.fc27.x86_64 and maxima-runtime-sbcl-5.40.0-2.fc27.x86_64

Expected results:
Installation without conflicts.

Additional info:
It may be worth to have a rpm/dnf key/config - to install package(s) without debuginfo parts.

Comment 1 Rex Dieter 2017-06-04 02:35:17 UTC
Not sure who's responsible for making unique build-id's, rpm?

Comment 2 Mark Wielaard 2017-06-04 09:58:27 UTC
(In reply to Rex Dieter from comment #1)
> Not sure who's responsible for making unique build-id's, rpm?

Yes, rpmbuild is.
If rpmbuild is unable to then a package can set %global _build_id_links none.

BTW. This is a duplicate of bug #1436856 but I seem unable change state to mark it as such.

Comment 3 José Matos 2017-06-04 10:59:02 UTC

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

Comment 4 José Matos 2017-06-04 11:00:06 UTC
(In reply to Mark Wielaard from comment #2)
> BTW. This is a duplicate of bug #1436856 but I seem unable change state to
> mark it as such.

I did it. :-)


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