76edd9f0a3f10c1ee1ae57b2e62c28574a0c7efe
If splitdebug was previously enabled for a package, and its files were installed, when splitdebug is turned off Package kept printing collision messages about /usr/lib/debug files. This happened because packages contain /usr/lib/debug paths in their content metadata (even those with separate splitdebug tarballs) and this wasn't cleared out before installed packages repository metadata update. Thus, during the cleanup step, these paths popped out generating invalid warnings.
…
Description
No description provided
Languages
Python
98.8%
Shell
0.7%
Makefile
0.4%