@th3dan said in js52: /usr/lib/libmozjs-52.so.0 exists in filesystem:
I moved all files of those packet (just in case):…
It was a bad decision. You’ve backed up two wrong files.
The old js52 was not installed in a clean way. The package either changed a repo or something else has happened with it a time ago. Pacman was asking at that time, whether or not we want to install js52.
After that three problems have arised:
the soname /usr/lib/libmozjs-52.so of the real shared library was incorrect. The correct soname of the library should be /usr/lib/libmozjs-52.so.0.
ldlinker has created the softlink with incorrect /usr/lib/libmozjs-52.so.0 name to a file with incorrect soname. The correct softlink name should be /usr/lib/libmozjs-52.so
the softlink with incorrect /usr/lib/libmozjs-52.so.0 name was not owned by the old js52 package. The file was created by ldlinker, not came out from the js52 package
The new, upgraded js52 has corrected three errors:
- the real shared library is correctly named /usr/lib/libmozjs-52.so.0
- the softlink to it is correctly named /usr/lib/libmozjs-52.so
- both library and softlink are owned by js52 package now
$ ls -lh /usr/lib/libmozjs-52*
lrwxrwxrwx 1 root root 16 May 4 18:13 /usr/lib/libmozjs-52.so -> libmozjs-52.so.0
-rwxr-xr-x 1 root root 21M May 4 18:13 /usr/lib/libmozjs-52.so.0
You’d better delete your backups asap.
The almighty pacman corrects all that stuff automagically, so that a user doesn’t required to know techy details:
sudo pacman -Sy --force --asdeps js52