Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: upgrade man-db (gremlins) fails because /lib exists (Read 137 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

upgrade man-db (gremlins) fails because /lib exists

Upgrading man-db from 2.8.4-r1 (system) to 2.8.5-r1 (gremlins) fails with "man-db: /lib exists in filesystem (owned by filesystem)".  I have not looked into the package or PKGBUILD, but I assume it is a typo related to installing files and not a serious issue (i.e., should hopefully be easy to fix.)

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #1
Upgrading man-db from 2.8.4-r1 (system) to 2.8.5-r1 (gremlins) fails with "man-db: /lib exists in filesystem (owned by filesystem)".  I have not looked into the package or PKGBUILD, but I assume it is a typo related to installing files and not a serious issue (i.e., should hopefully be easy to fix.)
I installed it with --force option

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #2
me too
anti-X  - artix - obarun - Void - systemD Free Space

I can no longer participate in a public forum side by side with neo-nazis and NSA trolls in a moderated sterile environment that is good for business.
Obviously the terms Open and Free mean nothing to you, or your business!

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #3
Yes, worked for me also.  Hopefully it will be fixed before moving from gremlins to system.

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #4
Don't use --force all the time.
Pacman has  gained --overwrite arg btw.

You now got a /lib/systemd/ dir on your system, can be deleted.

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #5
Thanks.  /lib is otherwise empty.  Out of curiousity, was it just a historical leftover from before /lib64 was used?  Or, was it there to block systemd stuff? 

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #6
Thanks.  /lib is otherwise empty.  Out of curiousity, was it just a historical leftover from before /lib64 was used?  Or, was it there to block systemd stuff? 

https://gitea.artixlinux.org/packagesM/man-db/commit/3be943fde001405b4220d1a0b91e5a8489ed1d82

Overlooked new option, enabled by default.

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #7
Thanks.  /lib is otherwise empty.  Out of curiousity, was it just a historical leftover from before /lib64 was used?  Or, was it there to block systemd stuff? 
At least on my machine /lib is symlink to /usr/lib
Some programs might want to use this path.
Mna is as good as his tools.

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #8
Don't use --force all the time.
Pacman has  gained --overwrite arg btw.

You now got a /lib/systemd/ dir on your system, can be deleted.
Unfortunately, i found your comment too late

Re: upgrade man-db (gremlins) fails because /lib exists

Reply #9
Sorry to not let this die quite yet, but I'm still curious why it would fail just because /lib already exists.  While we don't want it, I would have assumed it would have just created /lib/systemd and put those two files in it.  Does it assume /lib is/should be owned by systemd instead of filesystem?  Wouldn't it also fail on a PC with systemd, or is the ownership of /lib there different?