Bug 22545 - File in /usr/lib/.build-id/54/ conflicts with a file in clisp-1:2.49-18.mga7.x86_64
Summary: File in /usr/lib/.build-id/54/ conflicts with a file in clisp-1:2.49-18.mga7....
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-08 14:13 CET by Yuri Chornoivan
Modified: 2018-02-10 09:10 CET (History)
3 users (show)

See Also:
Source RPM: maxima-runtime-clisp-5.41.0-1.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Yuri Chornoivan 2018-02-08 14:13:23 CET 
Description of problem: When trying to update Cauldron I got the message that usr/lib/.build-id/54/bdc01c48240dc79b4d4b85534c05742a1db0af from maxima-runtime-clisp-5.41.0-1.mga7.x86_64 conflicts with the same file from clisp-1:2.49-18.mga7.x86_64

Version-Release number of selected component (if applicable): 5.41.0-1.mga7


How reproducible: always


Steps to Reproduce:
1. Try to update system via mgaaplet

Thanks in advance for fixing this bug.
Comment 1 Marja Van Waes 2018-02-09 09:29:47 CET 
(In reply to Yuri Chornoivan from comment #0)
> Description of problem: When trying to update Cauldron I got the message
> that usr/lib/.build-id/54/bdc01c48240dc79b4d4b85534c05742a1db0af from
> maxima-runtime-clisp-5.41.0-1.mga7.x86_64 conflicts with the same file from
> clisp-1:2.49-18.mga7.x86_64
> 
both were pushed by Jani on 21 January, I'll ping him on IRC.

CC'ing the registered clisp and maxima maintainers, don't know whom to assign to.

CC: (none) => marja11, rverschelde, shlomif

Comment 2 Jani Välimaa 2018-02-10 09:10:22 CET 
Should be fixed with maxima-5.41.0-2.mga7.

Closing as FIXED, feel free to reopen if needed.

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.