FS#17534 - [filesystem] contains file /usr/local/share/man. why??

Attached to Project: Arch Linux
Opened by Tomas Mudrunka (harvie) - Thursday, 17 December 2009, 10:37 GMT
Last edited by Allan McRae (Allan) - Saturday, 23 January 2010, 13:00 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas Bächler (brain0)
Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Hello, i have some software installed using make install (outside the pacman db) in /usr/local and it have manpages, so why new filesystem package is trying to replace my manpage-directory with file? isn't instaling something in local breaking arch rules? thx.

sudo LANG=C pacman -S filesystem
warning: filesystem-2009.11-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...

Targets (1): filesystem-2009.11-1

Total Download Size: 0.00 MB
Total Installed Size: 0.34 MB

Proceed with installation? [Y/n]
checking package integrity...
(1/1) checking for file conflicts [######################################################] 100%
(1/1) upgrading filesystem [######################################################] 100%
warning: directory permissions differ on srv/http/
filesystem: 775 package: 755
error: extract: not overwriting dir with file usr/local/share/man
error: problem occurred while upgrading filesystem


Additional info:
* package version(s)
filesystem-2009.11-1


Steps to reproduce:
pacman -S filesystem
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 23 January 2010, 13:00 GMT
Reason for closing:  Not a bug
Comment by xduugu (xduugu) - Thursday, 17 December 2009, 11:39 GMT
It's actually a symlink to /usr/local/man:

$ bsdtar tvf /var/cache/pacman/pkg/filesystem-2009.11-1-any.pkg.tar.gz | grep local/share/man
lrwxrwxrwx 0 root root 0 Nov 1 04:53 usr/local/share/man -> ../man
Comment by Tomas Mudrunka (harvie) - Thursday, 17 December 2009, 13:11 GMT
oh, sorry, that makes sense ;)
btw why? man looks to /usr/local/share/man by default so why you just don't keep it vanilla?
Comment by Jan de Groot (JGC) - Thursday, 17 December 2009, 13:20 GMT
The symlink should be the other way around. /usr/local/man should point to /usr/local/share/man instead.
Comment by Tomas Mudrunka (harvie) - Thursday, 17 December 2009, 14:16 GMT
jgc: i think so
Comment by Allan McRae (Allan) - Thursday, 17 December 2009, 21:04 GMT
Note that this has been the case for ages. So you must have overwritten the symlink in the past to have these issues.
Comment by Tomas Mudrunka (harvie) - Thursday, 17 December 2009, 21:16 GMT
Allan: no offence ;)
Comment by Allan McRae (Allan) - Saturday, 19 December 2009, 22:32 GMT
I'm not sure what we can do here... This should always have been a symlink on a users system given the filesystem package has not changed in this regard. Switching symlinks from /usr/local/man to /usr/local/share/man is a near impossible upgrade path.

So.... "Works for me"?
Comment by Allan McRae (Allan) - Saturday, 23 January 2010, 13:00 GMT
Closing as this is almost impossible to fix and having this bug required the user to overwrite a symlink from the filesystem package.

Loading...