FS#19967 - pacman should check if /sbin is in path
Attached to Project:
Pacman
Opened by David Watzke (dwatzke) - Friday, 25 June 2010, 09:29 GMT
Last edited by Allan McRae (Allan) - Tuesday, 29 June 2010, 05:44 GMT
Opened by David Watzke (dwatzke) - Friday, 25 June 2010, 09:29 GMT
Last edited by Allan McRae (Allan) - Tuesday, 29 June 2010, 05:44 GMT
|
Details
Description: pacman should check if /sbin and /usr/sbin is
in path - problem is when it isn't there and user sets his
own PATH without sbin dirs (/sbin and /usr/sbin) in it and
calls sudo pacman -S glibc (just for example) this
happens:
(1/1) upgrading glibc [######################] 100% /tmp/alpm_NjqEZT/.INSTALL: line 6: ldconfig: command not found /tmp/alpm_NjqEZT/.INSTALL: line 7: init: command not found I don't think that user should have sbin dirs in his PATH. We (users) should be able to decide. Additional info: * package version(s): recent pacman 3.4.0-2 Steps to reproduce: export PATH="~/bin:/usr/local/bin:/bin:/usr/bin" sudo pacman -S glibc |
This task depends upon
Closed by Allan McRae (Allan)
Tuesday, 29 June 2010, 05:44 GMT
Reason for closing: Not a bug
Additional comments about closing: This is a packaging and not a pacman one.
Tuesday, 29 June 2010, 05:44 GMT
Reason for closing: Not a bug
Additional comments about closing: This is a packaging and not a pacman one.
It could also be argued that if you are installing packages or updating a system then you are not a "user" but and "administrator" and would be expected to have /sbin in your path.
Please open bug reports in the Arch section for any other packages you find issues with.