Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10709 - update to filesystem-2008.06-2 fails

Attached to Project: Arch Linux
Opened by M.N (milosn) - Friday, 20 June 2008, 09:01 GMT
Last edited by Dan McGee (toofishes) - Monday, 23 June 2008, 04:07 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dan McGee (toofishes)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

update to filesystem-2008.06-2 fails with fallowing error:

root@box src # pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets: filesystem-2008.06-2 mlocate-0.20-2

Total Download Size: 0.00 MB
Total Installed Size: 0.60 MB

Proceed with installation? [Y/n] y
checking package integrity...
(2/2) checking for file conflicts [###########################################################################################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
filesystem: /usr/local/share/man exists in filesystem
Errors occurred, no packages were upgraded.

Steps to reproduce:

pacman -Syu
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 23 June 2008, 04:07 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Do any manual cleanup on your own, directory was added to comply with FHS standards.
Comment by Dan McGee (toofishes) - Friday, 20 June 2008, 11:24 GMT
This is not much different than other file conflict that needs manual resolving. You sometimes have to sort these things out, and it looks like you have something installed locally that already created the /usr/local/share/man directory, which filesystem just added as a symlink to the /usr/local/man directory as the FHS states we should.
Comment by Glenn Matthys (RedShift) - Friday, 20 June 2008, 17:13 GMT
I didn't think much of it when I posted to the mailinglist why filesystem messes with /usr/local, but seeing this bug, it obviously has more implications than initially thought.

IMO:

* I don't get why FHS wants to create such a weird symlink,
* why it even defines /usr/local (it's called 'local' for a reason...)
* nobody says we have to follow FHS
* I don't know what will happen with the current content of /usr/local/share/man when filesystem-2008.06 is installed
Comment by Michele Gastaldo (pikiweb) - Saturday, 21 June 2008, 13:20 GMT
Just to let you know:
I had the same problem with this update, but for me the solution was quite easy: I found out that my /usr/local/share/man had just an empty "man1" directory, so I forced the update and everything was fine.

Discussions about FHS are not for me (but I guess it's good to follow a standard)
Regards

Loading...