FS#43309 - [pacman] PLEASE ENTER SUMMARY

Attached to Project: Arch Linux
Opened by James (thx1138) - Friday, 02 January 2015, 22:36 GMT
Last edited by Allan McRae (Allan) - Friday, 02 January 2015, 23:10 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Upgraded to pacman 4.2.0-5

Installing a package which includes "/bin/", which already exists as a symbolic link from package "filesystem":

lrwxrwxrwx 1 root root 7 Oct 25 12:41 bin -> usr/bin

pacman gives an install error:

(1/1) checking for file conflicts
error: failed to commit transaction (conflicting files)
springseed: /bin exists in filesystem

Running "pacman" install with "--debug", there is:

debug: checking possible conflict: /bin/
debug: found file conflict /bin, packages springseed and (filesystem)

in contrast to, for instance:

debug: checking possible conflict: /usr/
debug: file is a directory, not a conflict

presumably since "/bin/" is a symbolic link and not a "directory" per se.

Is that not a bug in pacman, seemingly not distinguishing between a "directory" and a symbolic link to a directory?

James
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 02 January 2015, 23:10 GMT
Reason for closing:  Not a bug
Comment by Stefan Majewsky (majewsky) - Friday, 02 January 2015, 22:55 GMT
Handling of symlink directories has changed in pacman-4.2, as noted in the release announcement: (Ctrl-F for "Directory Symlink Handling")

http://allanmcrae.com/2014/12/pacman-4-2-released/

So this is not a bug; packages which try to install to /bin/ are now intentionally in conflict with core/filesystem, and need to be fixed to install to /usr/bin/ instead.

Loading...