Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#19907 - [repo-add] symbolic link not permitted

Attached to Project: Pacman
Opened by Ike Devolder (BlackEagle) - Tuesday, 22 June 2010, 19:34 GMT
Last edited by Dan McGee (toofishes) - Thursday, 08 July 2010, 05:02 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version 3.4.0
Due in Version 3.4.1
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

ln: creating symbolic link `herecura-stable.db': Operation not permitted


Steps to Reproduce:

repo-add herecura-stable.db.tar.gz *.pkg.*
This task depends upon

Closed by  Dan McGee (toofishes)
Thursday, 08 July 2010, 05:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  Will be fixed in 3.4.1, see http://projects.archlinux.org/pacman.git /commit/?h=maint&id=21d5dedf
Comment by Dan McGee (toofishes) - Tuesday, 22 June 2010, 19:48 GMT
Wow, what a helpful bug report. What is the filesystem? What are the directory permissions? You have to give us a lot more than this to work from if you aren't going to do some debugging or advance scouting yourself...
Comment by Dan McGee (toofishes) - Tuesday, 22 June 2010, 19:57 GMT
I'm guessing the filesystem is FAT or FAT32 or something that doesn't natively support symlinks.

Can you try the following and attach the output?

cd /path/to/your/directory
touch test-file
ln -s test-file test-symlink
ln test-file test-hardlink
ls -l test-*
Comment by Ike Devolder (BlackEagle) - Tuesday, 22 June 2010, 20:49 GMT
vboxsf

and indeed there is no symlinking in this filesystem

sorry for the not very informative bug report, i was just lazy to search

thx for the very constructive 1st comment
Comment by Dan McGee (toofishes) - Tuesday, 22 June 2010, 21:41 GMT
I'd rather not close this thus the reason for those last questions. If hardlinking is a viable option we could at least consider trying that after a failure to symlink. With pacman 3.5.0 and later your repository will not work at all if that link we are attempting to create does not exist.
Comment by Ike Devolder (BlackEagle) - Wednesday, 23 June 2010, 04:55 GMT
more info:

vboxsf, used for getting the data out of the VirtualBox, when this really is getting a problem, in no time sshfs or something can be used

$ ln -s herecura-stable-any.txt herecura-bla
ln: creating symbolic link `herecura-bla': Operation not permitted

$ ln herecura-stable-any.txt herecura-bla
ln: creating hard link `herecura-bla' => `herecura-stable-any.txt': Operation not permitted


so maybe if the links become required, a big notification could be given someone has to use a filesystem capable of symlinking or at minimal hardlinking
or you could for some filesystems like vboxsf, fat32, ... fall further back to a copy of the file in stead of a link ?
Comment by Dan McGee (toofishes) - Wednesday, 23 June 2010, 11:34 GMT
For reference: http://www.virtualbox.org/ticket/818
Comment by Allan McRae (Allan) - Thursday, 08 July 2010, 04:59 GMT
http://projects.archlinux.org/pacman.git/commit/?h=maint&id=21d5dedf

Loading...