Re: Bug#443507: python-gobject: Importing gobject fails after libglib upgrade
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
Am Sa den 22. Sep 2007 um 0:18 schrieb Zakrn:
> On Sat, 2007-09-22 at 01:14 +0200, Josselin Mouette wrote:
> > I'm not talking about the libpcre3 package, but of the file
> > in /lib/libpcre.so.3 which was not brought by a Debian package.
>
> My fault, I didn't think about it. And you are right,
> removing /lib/libpcre.so.3 and /lib/libpcre.so.3.12.0 has helped. But I
> really don't know what could install them.
Well, maybe I can help out with the solution.
I had similar problem today on one of my systems and found this bug
report. So the solution was also true for me. But I cannot live without
to know why a library was in the /lib without coming from a .deb. So I
did some search and found the reason.
Years ago there was a /bin/grep depending on libpcre.so which stay in
/usr. So it was necessary to copy the library to /lib to let the system
boot again. And that was it. Just a temporary bugfix.
The bad is that all tools used the old /lib/libpcre.so.0 and not the
updated one in /usr/lib. So the bug is a kind of handmade security bug.
(Maybe other has the same but did not see it!)
So maybe there can be a warning in the NEWS of grep or libpcre3 if the
workaround exists on recent systems.
Regards
Klaus
Ps. This is just a note x post to debian-devel to rfc. The bug shouldn't
go open.
- --
Klaus Ethgen http://www.ethgen.de/
pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <Klaus@Ethgen.de>
Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQEVAwUBSg26S5+OKpjRpO3lAQr3WQgAsjdHNLbPjgb2XLgjJK9ye6AgRDsHGQwH
gv/UDUG6C0X9Llyv/OQxEpy6cfiJxLhvTP91NEx4bobj52LgOlUUP7Kz7NcGLROv
Hk/Bhjxet1xNJtEzGiHRmMRX+DycUQXcOsls3eclsVaqjuvTyaGy2TkQwFFsvlVP
8WvHyUHoPmhr/X/5sOxaantI5BbOOaPSZPyc9SYDaIJ+Dttz3NL6pRyOFl26tlhQ
I2glFpD4MhCIllwzJZ1kNpJ63GLLGn1xlMrl89Vc31FNREKPYJ9es0A4LO7G8azN
FYKLBoX4A01gBYg9Yibr/Lick0VbD/y8N4rXgzmerD6bHbbnnO/gpA==
=JThp
-----END PGP SIGNATURE-----
Reply to: