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