View previous topic :: View next topic |
Author |
Message |
sebaro Veteran
Joined: 03 Jul 2006 Posts: 1141 Location: Romania
|
Posted: Fri Jun 08, 2012 1:37 pm Post subject: [Solved] libattica upgrade to 0.3.0 breaks KDE |
|
|
This version doesn't create a libattica.so.0 symlink, only libattica.so.0.3, so emerging or running KDE packages fails because libkdeui.so (kde-base/kdelibs) is built against libattica.so.0.
A workaround is to create the missing symlink:
> ln -s libattica.so.0.3.0 libattica.so.0
Solutions:
1. mask >dev-libs/libattica-0.2.0
2. remerge kde-base/kdelibs (maybe revdep-rebuild)
Last edited by sebaro on Mon Jun 11, 2012 9:07 am; edited 1 time in total |
|
Back to top |
|
|
chithanh Developer
Joined: 05 Aug 2006 Posts: 2158 Location: Berlin, Germany
|
Posted: Sun Jun 10, 2012 11:22 pm Post subject: |
|
|
Running revdep-rebuild would be preferable (remove symlink first). The change in soname is due to ABI break, which means that programs using your symlink may now behave in unexpected ways. |
|
Back to top |
|
|
sebaro Veteran
Joined: 03 Jul 2006 Posts: 1141 Location: Romania
|
Posted: Mon Jun 11, 2012 5:33 am Post subject: |
|
|
I found this on libattica's changelog: "0.3.0 - Bump soname from .0 to .0.3 since we have a BIC change."
Why aren't the "preserve_old_lib(_notify)" functions used in the ebuild? Why some ebuilds use them and other don't (libpng use them and tiff doesn't)?
Thanks. |
|
Back to top |
|
|
chithanh Developer
Joined: 05 Aug 2006 Posts: 2158 Location: Berlin, Germany
|
Posted: Mon Jun 11, 2012 8:06 am Post subject: |
|
|
preserve_old_lib is needed for packages where large parts of the system would break on soname change, or important packages like gcc. With libattica it was only a couple of KDE packages, so it was not justified. |
|
Back to top |
|
|
sebaro Veteran
Joined: 03 Jul 2006 Posts: 1141 Location: Romania
|
Posted: Mon Jun 11, 2012 9:05 am Post subject: |
|
|
OK, but I think the size (build time) of packages should be considered as well not just how many packages need to be rebuilt. But that's off topic. |
|
Back to top |
|
|
Decibels Veteran
Joined: 16 Aug 2002 Posts: 1623 Location: U.S.A.
|
Posted: Fri Aug 10, 2012 1:53 am Post subject: |
|
|
Well libattica-0.4.0 will stop KDE from loading. It doesn't upgrade/remerge libkde and attica, and your only left with libattica.so.0.4 and they want libattica.so.0.3.
If it hadn't been for twm and typing startkde wouldn't have figured it out and could only get a console. Using startkde in console didn't tell me what the problem was. _________________ Support bacteria – they’re the only culture some people have.”
– Steven Wright |
|
Back to top |
|
|
|