Bug 19750 - libastro0 (mga6) file conflict with libastro1 (mga5)
Summary: libastro0 (mga6) file conflict with libastro1 (mga5)
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: David GEIGER
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-10 19:02 CET by claire robinson
Modified: 2016-12-01 15:35 CET (History)
1 user (show)

See Also:
Source RPM: marble
CVE:
Status comment:


Attachments

Description claire robinson 2016-11-10 19:02:27 CET
Noticed after cli upgrade from mga5 to cauldron. Attempting to recover some space on old system by removing old libs etc.

# urpme $(urpmq --not-available | tr '\n' ' ')

Noticed that mga6 marble was being removed due to missing libastro

  marble-16.08.2-2.mga6.i586
   (due to missing libastro.so.1,
    due to missing libmarblewidget-qt5.so.25)

# urpmq --whatprovides libastro.so.1
libastro0

Tried to install mga6 version..

# urpmi libastro0

installing libastro0-16.08.2-2.mga6.i586.rpm from /var/cache/urpmi/rpms                                                     
Preparing...                     #####################################
Installation failed:    file /usr/lib/libastro.so.0.17.20 from install of libastro0-16.08.2-2.mga6.i586 conflicts with file from package libastro1-4.14.3-1.mga5.i586

The version looks odd with libastro0 replacing libastro1, especially with libastro.so.1 - possible bad libification too?
claire robinson 2016-11-10 19:02:46 CET

Summary: libastro0 (mga6) file conflict with libastro (mga5) => libastro0 (mga6) file conflict with libastro1 (mga5)

Comment 1 Thierry Vignaud 2016-11-14 09:22:58 CET
Indeed, we've the same files in both lib64astro[01]:
/usr/lib64/libastro.so.0.17.20
/usr/lib64/libastro.so.1

CC: (none) => thierry.vignaud

Comment 2 David GEIGER 2016-11-14 16:15:20 CET
Should be fixed in next marble update reverting back libmajor "1" like on mga5.
Comment 3 David GEIGER 2016-12-01 15:35:21 CET
Fixed!

Feel free to reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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