X would not start after updates: a cautionary tail about slackpkg and slackbuilds.org
I use a lot of packages from slackbuilds.org.
With one of the recent set of updates to -current, I could no longer launch X. Normally I stay -current by using slackpkg install-new, slackpkg upgrade-all, and then searching through the Changelog for removed packages and removing them manually. This process works fine except when a package formerly maintained at slackbuilds.org is moved into slackware itself. Such was the case for icu4c.
Since I had SBo packages blacklisted, when icu4c was added about a year ago, it did not get added to my system. And it did not get upgraded in March. Strangely enough, it only caused me problems after one of the more recent updates, which searched for blah.so.51 instead of the older one.
All is sorted out now, but I guess I will have to manually check new packages as well now. Is there any mechanism that highlights packages (scripts) formerly maintained at slackbuilds.org but then added to Slackware?