Sebastien Bacher wrote:
(please keep the bug in the Cc:, I've forwarded the previous mail to
[EMAIL PROTECTED])
Le jeudi 31 mars 2005 à 12:20 +0200, Marek W. Gutowski a écrit :
So, indeed, there is something under /usr/local/lib, but,
frankly, I didn't put it there 'by hand'.
The debian packages don't use /usr/local, you have installed these by
hand for sure (with a "make install" or you have used a build
system/autopackage/something).
The first and
last file in /usr/local/lib are real files; second and third
are merely pointers to the first file.
That's how libs work.
How can I fix this? Do I have to check/reinstall nearly
70 affected applications? Or, maybe, I should replace
only the two above links to point to /usr/lib/libglib-2.0.so.0.600.3
from now on?
Just remove the crap you have put in /usr/local and work with the
packages.
I'm closing the bug since that's not due to the packages.
Cheers,
Sebastien Bacher
Thank you!
I have removed all files libg* (and pointers to them) in
/usr/local/lib directory. This, however, was not enough.
I had to reinstall the packages: libgtk2.0-bin (which
finally got set as it should, with no complaints) and,
in addition:
libpango1.0-0
libpango1.0-dev
libpango1.0-common.
Only after that my applications are in working shape again,
most notably gimp.
--
Marek Gutowski, [EMAIL PROTECTED]
Institute of Physics, ON-3.2, Al. Lotnikow 32/46,
(PL) 02-668 Warszawa, POLAND, tel. +48-22-8436601 ext. 3122
>> To talk or not to talk? Yes, talk, plain ASCII please <<
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
