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#4398 - makepkg doesn't like paths with spaces

Attached to Project: Pacman
Opened by GCN (gilcn) - Friday, 07 April 2006, 16:59 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 09 April 2006, 09:20 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Whenever I try to build some packages as a normal user and there are one or more spaces in the path I get the following error from makepkg:

$ pwd
/home/user/Arch Packages/mypkg
$ makepkg
==> ERROR: Package destination directory does not exist or permission denied.

If I rename "Arch Packages" to something like "Arch_Packages" then it works !
This task depends upon

Closed by  Judd Vinet (judd)
Monday, 10 April 2006, 17:21 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Perhaps in the future, but not now.
Comment by Judd Vinet (judd) - Monday, 10 April 2006, 17:18 GMT
This is true, and has been a bug for sometime. Unfortunately, it may not ever get fixed. Bash is quite tricky to manage spaced-pathnames with, especially in a script. On the command-line, with explicit pathnames and explicit escaping, it works well enough. But trying to escape a pathname that's stored in a variable (ie, $path) is quite cumbersome.

I'd recommend that you avoid directories with spaces in them. This may get fixed at some point, but it's not a priority now, as it only affects a few people. If you'd like, you can try and fix makepkg to play nice with spaces. If you do, please send me the patch.

Loading...