At the end of the procedure, it says
Such packages can be detected using: grep '^lib/' /var/lib/pacman/local/*/files These packages need rebuilding so as not to include the /lib directory. Then the final "pacman -Su" will successfully install glibc.
- It will list packages that own files in /lib. If it only lists glibc, you're almost all set to go, all you have to do is check for unowned files and deal with those. thestinger (talk) 12:16, 15 July 2012 (UTC)
Add subsection to deal with common apps
Can we add a subsection to the "Issue 2" section that deals with known apps that need to be uninstalled and then reinstalled?
Specifically in my case (and others), there is UFW that causes this "Issue 2". Of course, it would be wise to put a statement in there that pacman will keep their old ufw configs as ".pacsave" files but that they manually must merge them back after reinstalling UFW.
--- Too many users are unsure about remaining contents in /lib directly. I propose someone adds the following to the issue 2 in the usrlib wiki as another warning:
"Do not delete or move away any files in /lib owned by your current glibc (2.16.0-1 on up-to-date systems) in any case at this point."