Hi Michael, Michael Biebl wrote: > Do you have an idea, where this file might have come from?
On a first thought: No. The package is no package I installed on purpose, it came in by dependencies and I surely didn't fiddle around with its configuration (if it has one). On a second thought: I know that in the very beginning of that system (i.e. during 2015) I had issues with the SD card the system runs off and I at least replaced the SD card once, maybe twice. IIRC the original SD card went readonly and I dd'ed its contents onto a new one and ran fsck (offline). While that in theory could cause stray files, IMHO especially dpkg is rather good in keeping things consistent. So I slightly doubt that this is the cause for this issue. On the other hand, it seems the best explanation currently available. > So it looks like a local misconfiguration which went unnoticed so far as > /lib/arm-linux-gnueabihf/libglib-2.0.so.0.5* took precedence over > /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 I have no idea what kind of "configuration" could be involved here. > I guess there is nothing really the libglib2.0-0 package can do about > this. Do you agree? If I'm the only one who happens to have this issue, I'm fine with closing this as unreproducible. > As soon as you clean up the stray > /lib/arm-linux-gnueabihf/libglib-2.0.so.0.4200.1 and run ldconfig, the > problem should go away? No, because there's also a symlink to it which (according to the timestamp) seem to have been created by maintainer scripts of this package: 6080 lrwxrwxrwx 1 root root 23 Apr 4 09:03 /lib/arm-linux-gnueabihf/libglib-2.0.so.0 -> libglib-2.0.so.0.4200.1 Not sure how I should clean up that one. Can I safely delete it, too? Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE