Zypper installs procps > ps as a symlink to itself

since dup from 15.4 to 15.5 now 15.6 zypper says there or file conflicts. If I ‘say yes’ the install goes forward, but all the files installed eg, procps [ps] are symlinks to themselves.
My /bin/ is Not a symlink to /usr/bin/ or vice-versa.
Both directories are directories but ‘files’ eg utilities like ‘PS’ are symlinks to themselves.
This has been an issue since dup from 15.4 to 15.5 and again is percisting in 15.6.
I’ve removed procps (which also removed all or most ‘patterns’ without asking to.
This is getting to be a real problem.
I downloaded the procps.rpm, decompressed and copied the ps and sysctl binaries to /bin/ and /sbin/ but now command says I’m missing libproc2… wth?
Why isn’t zypper in -f ‘procps’ installing All required?




‘ps’ says it requires libproc2… but libproc7 and 8 are all that are available in current repos.
HOW can I be the ‘only one’ that has this or similar issue.
OpenSuse have been installed from opensuse repos, updates have been done from opensuse repos’ how is this possible?

similar problem, same non-functioning results.

It actually sounds like it is.

Show

ls -ld /bin
ls -ld /usr/bin
cat /proc/self/mountinfo

On opensuse 15.6 /usr/ps is a symbolic link to /usr/ps and /usr/bin/ps is a symbolic link to /usr/ps, so actually there is no elf binary there. Indeed a very annoying problem with the zypper package manager since at least 15.4

1 Like

There is no such file anywhere. Stop telling fairy tales and start showing the actual facts.

That was my typo. It’s /bin/ps a symbolic link to /bin/ps and /usr/bin/ps a symbolic link to /bin/ps .

1 Like

Again, don’t tell stories, show:

ls -l /bin/ps*

on a fresh 15.6 install /bin/ps is the actual executable, /usr/bin/ps is a simlink to /bin/ps .

This is not on a fresh install but on an install that was installed about half a year ago and then updated roughly once every 2 months with zypper up.

@LandisTwo and @rjmathar ,

Please note that people here do not like stories when they can be communicated by computer output. So you do not tell x is a symlink to y, but you show:

henk@boven:~> ls -l /usr/bin/ps
lrwxrwxrwx 1 root root 7 Feb 21 15:59 /usr/bin/ps -> /bin/ps
henk@boven:~> ls -l /bin/ps
-rwxr-xr-x 1 root root 134360 Feb 21 15:59 /bin/ps
henk@boven:~> 

Doing so tells people here what you did, what the computer answered and also who you were (e.g root or not) and were you were (working directory). Doing so also avoids confusing typos of the type that @rjmathar made above.

And please do not use screen shots when not really needed. They are difficult to read, one can not search through them with the browser search function and one can not quote from it in an answer. Instead please, to make the pieces of computer code in your posts better consumable by technical oriented people:

And post as complete as possible. That is starting with the line with the prompt and the command, then all output, and ending with the new prompt line.
When you really feel you need to change anything in such a copy, then in a comment, else we take all characters literally.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.