Bug 1917 - libgucharmap7-3.0.1-1.mga2 lacks [symlink to] libgucharmap.so.7, breaks bluefish and possibly other dependent packages
Summary: libgucharmap7-3.0.1-1.mga2 lacks [symlink to] libgucharmap.so.7, breaks bluef...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: check
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-06-25 21:44 CEST by Radu Cristian Fotescu
Modified: 2012-01-15 22:41 CET (History)
2 users (show)

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

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

Description Radu Cristian Fotescu 2011-06-25 21:44:26 CEST 
Description of problem:

Updating to libgucharmap7-3.0.1-1.mga2 breaks bluefish-2.0.3-1.mga1 "due to missing libgucharmap.so.7".

libgucharmap7-3.0.0-1.mga1 had:
        â/usr/lib/libgucharmap.so.7
        â/usr/lib/libgucharmap.so.7.0.0

libgucharmap7-3.0.1-1.mga2 has:
        â/usr/lib/libgucharmap_2_90.so.7
        â/usr/lib/libgucharmap_2_90.so.7.0.0

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Manuel Hiebel 2011-06-25 21:49:40 CEST

CC: (none) => jani.valimaa
Source RPM: libgucharmap7-3.0.1-1.mga2 => gucharmap

Comment 1 Ahmad Samir 2011-06-25 21:59:44 CEST 
bluefish needs a rebuild for new libgucharmap. Should be fixed in the next bluefish package, which has just been submitted by dmorgan.

Source RPM: gucharmap => bluefish

Comment 2 Radu Cristian Fotescu 2011-06-25 22:18:59 CEST 
So bluefish was the _only_ package/application that was looking for libgucharmap.so.7 instead of libgucharmap_2_90.so.7?

I am not familiar with libgucharmap, but a name like libgucharmap_2_90.so.7 looks silly as compared to libgucharmap.so.7.

If this is about the idiocies of GTK+3 and GNOME3, then I am glad I am currently in the process of getting [more and more] used to KDE4... because I expect 99% of the GTK+2 applications that had some GNOME2 dependency to need to be rebuilt.

In the meantime, if adding GTK+3/GNOME3 libraries that affect the preexisting GTK+2/GNOME2 breaks the GTK+ applications...

But I still don't get why updating libgucharmap7 (a *minor* version upgrade!) should *break* backwards compatibility. RTF, can't a symlink be added? Can't there be a libgucharmap7_3 / libgucharmap7_2.90 or smth?

"If it ain't break, then please break it" -- the new slogan in Linux...
Comment 3 Manuel Hiebel 2011-10-01 01:38:07 CEST 
Is that bug still valid ?

Keywords: (none) => NEEDINFO
Whiteboard: (none) => check

Comment 4 Manuel Hiebel 2011-11-20 00:51:04 CET 
ping ?
Comment 5 Marja Van Waes 2012-01-15 22:41:41 CET 
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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