I have a dual Opteron box that has successfully run a "nomultilib" 64-bit only system for years. For various reasons, the box had not been updated for a long time. I did a major upgrade over several days, incrementally. Somewhere along the way, some ebuild clobbered my /lib symlink to /lib64. My profile is "nomultilib" and my global USE flags include "-multilib". I discovered the problem when I tried to restart one of my servers, restored the symlink,and everything works fine. Happy ending.
My question: I have all the portage logs from the upgrade. Is there some way I can determine which ebuild first changed the symlink? I need to determine whether there is a bug in that ebuild, or it was simply a glitch because of the massive set of upgrades. In the first case, I'd like to file a bug on that package. On the other hand, it may not be worth the time and effort. But I'm willing to devote a couple of hours of research to this in the community interest. Any suggestions appreciated! Kirk
