[SOLVED] Symlinks in some packages are not recognized by pacman

felixonmars · 2012-08-30 03:18:17

Hi,

I found it that some symlinks in my disk are generated by specific package, and removed along with the package when using pacman, but not recognized by pacman -Qo.

For example:

# pacman -S community/xplc
...
# file /usr/lib/libxplc.so.0.3.13-unstable
/usr/lib/libxplc.so.0.3.13-unstable: symbolic link to `libxplc.so.0.3.13'
# pacman -Qo /usr/lib/libxplc.so.0.3.13-unstable
error: No package owns /usr/lib/libxplc.so.0.3.13-unstable
# pacman -R xplc
...
# ls /usr/lib/libxplc.so.0.3.13-unstable
ls: cannot access /usr/lib/libxplc.so.0.3.13-unstable: No such file or directory

I tried download the package source from ABS and makepkg myself, but no pkg/usr/lib/libxplc.so.0.3.13-unstable found in the build directory.

I must be missing something, could someone point it out? Thanks a lot.

Last edited by felixonmars (2012-08-30 04:01:17)

progandy · 2012-08-30 03:21:15

Probably the symlink is created and removed with the install script and not as part of the package file structure.
Edit: Not true in this case...

Last edited by progandy (2012-08-30 03:26:32)

falconindy · 2012-08-30 03:22:19

If pacman didn't install it as part of a package, it isn't going to track it. It's as simple as that. There's no general problems with symlinks being tracked.

felixonmars · 2012-08-30 03:39:08

falconindy wrote:

If pacman didn't install it as part of a package, it isn't going to track it. It's as simple as that. There's no general problems with symlinks being tracked.

Thanks for the explanation, but may I know where does the -unstable file come?

I've tried strace -f -eopen, but it shows that file was not opened during installation of xplc, but did exist after then.

Last edited by felixonmars (2012-08-30 03:39:36)

progandy · 2012-08-30 03:45:09

felixonmars wrote:

I've tried strace -f -eopen, but it shows that file was not opened during installation of xplc, but did exist after then.

You traced the wrong system call:

sudo strace -f -esymlink pacman -S xplc

felixonmars · 2012-08-30 04:00:32

progandy wrote:

felixonmars wrote:
I've tried strace -f -eopen, but it shows that file was not opened during installation of xplc, but did exist after then.
You traced the wrong system call:
sudo strace -f -esymlink pacman -S xplc

Oops, thanks a lot.

I finally know that it is ldconfig which creates the symlink, by using:

# strace -f -e trace=file,process pacman -S xplc

Arch Linux

#1 2012-08-30 03:18:17

[SOLVED] Symlinks in some packages are not recognized by pacman

#2 2012-08-30 03:21:15

Re: [SOLVED] Symlinks in some packages are not recognized by pacman

#3 2012-08-30 03:22:19

Re: [SOLVED] Symlinks in some packages are not recognized by pacman

#4 2012-08-30 03:39:08

Re: [SOLVED] Symlinks in some packages are not recognized by pacman

#5 2012-08-30 03:45:09

Re: [SOLVED] Symlinks in some packages are not recognized by pacman

#6 2012-08-30 04:00:32

Re: [SOLVED] Symlinks in some packages are not recognized by pacman

Board footer