after installing icu-49.1.1 the most of the other packages failed with DLOPEN error on libicu-1.4.8 In addition gvim would no longer run or compile and cave was reporting errors but was still functional. I downgraded the package and was then able to mask it. There are at least 6 .la files on my system that reference -licu18 or some variant. That could explain the build errors. I think it would be a good idea to provide migration information in the ebuild before unmasking such a disruptive package.
You should just run revdep-rebuild. It is normal for packages after ABI changes.
If only it was that simple. Most reinstalls failed until libxml2 was reinstalled. Even then, a cave fix-linkage wanted to downgrade icu to 1.4.8 because of chromium which still has a <icu-49 depend. Also most system tools were at least partially broken until gnustep-base was reinstalled. If would seem that breaking chromium would be an important thing to know about since it is a somewhat important package.
(In reply to comment #2) > If only it was that simple. Most reinstalls failed until libxml2 was > reinstalled. Even then, a cave fix-linkage wanted to downgrade icu to 1.4.8 > because of chromium which still has a <icu-49 depend. > > Also most system tools were at least partially broken until gnustep-base was > reinstalled. > > If would seem that breaking chromium would be an important thing to know > about since it is a somewhat important package. Bug #410777 which is why that version blocker is in place. Otherwise there appears to be nothing to see here.
