FS#23902 - [namcap] parsepkgbuild can hang on valid PKGBUILD
Attached to Project:
Arch Linux
Opened by Dan McGee (toofishes) - Saturday, 23 April 2011, 18:32 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Monday, 25 April 2011, 10:56 GMT
Opened by Dan McGee (toofishes) - Saturday, 23 April 2011, 18:32 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Monday, 25 April 2011, 10:56 GMT
|
Details
$ cd arch-repos/postgresql/trunk/
$ namcap PKGBUILD It will never return, getting stuck waiting for parsepkgbuild to return...which does not happen, due to this: $ parsepkgbuild PKGBUILD <snip> PKGBUILD: line 100: cd: restricted make: *** No rule to make target `install'. Stop. make: *** contrib: No such file or directory. Stop. make: *** doc/src/sgml: No such file or directory. Stop. make: *** src/bin/pg_config: No such file or directory. Stop. rm: cannot remove `/usr/share/man/man1/pg_config.1': No such file or directory install: cannot stat `COPYRIGHT': No such file or directory rm: cannot remove `/usr/include/postgresql/internal/libpq-int.h': Permission denied rm: cannot remove `/usr/include/postgresql/internal/libpq/pqcomm.h': Permission denied rm: cannot remove `/usr/include/postgresql/internal/port.h': Permission denied rm: cannot remove `/usr/include/postgresql/internal/postgres_fe.h': Permission denied rm: cannot remove `/usr/include/postgresql/internal/c.h': Permission denied rm: cannot remove `/usr/include/postgresql/internal/pqexpbuffer.h': Permission denied rm: cannot remove `/usr/include/libpq/libpq-fs.h': Permission denied rm: remove write-protected regular file `./term.h'? ^C Where it hangs. |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Monday, 25 April 2011, 10:56 GMT
Reason for closing: Fixed
Additional comments about closing: To appear in upcoming namcap 3.1
Monday, 25 April 2011, 10:56 GMT
Reason for closing: Fixed
Additional comments about closing: To appear in upcoming namcap 3.1
What do you think of the attached patch?
However, the PATH setting works in this case, but still hides the problem here- we attempt to run everything and we shouldn't be doing so. Setting path doesn't help one bit if I am using shell builtins, absolute paths (/bin/rm), etc.
What builtins are you thinking about which are not disabled by the restricted mode?