On this revelational Saturday, of the seventh month of 2004 you wrote: > And if this happens with something like glibc, you're hosed.
Okay, I just happen to be the poor sod you were referring to in this nugget I found in the archives of just three months ago. What's worse is that my carelessness was just confined to an accidental one stable line in my sources.list in my otherwise purely sid distro. Now I've got libglib1.2 and libglib2.0-0 handling different packages. I guess I put too much confidence in aptitude to catch any package mixing. I'm also somewhat fortunate that uninstalling 1.2 only blows away about half of my packages instead of all of them. Yet even after removing 1.2 and trying to install the packages that WERE dependent on 1.2, hoping that they'll assume the already installed 2.0-0 dependencies, neither apt-get or aptitude have enough wisdom to recognize it. They still try and install 1.2 when using apt to reinstall them. So question is, is there a way to strace what packages and why the packages i'm trying to reinstall to depend on 2.0 are trying to pull and install 1.2? Or, another method I'm wondering about whether if it's safe for me to install glibc1.2 into /usr/local and if there is, whether there's a way to do this way apt or dpkg without having to compile it. That could be a temp quickfix although ideally I want everything depending on 2.0 without potential 1.2 liabilities like this happening again. Any advise would be greatly appreciated. A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
