buildd: take sudo secure_path into account for PATH
Metadata
Current evaluation
Merged #24 in commit 912d88c, updating Buildd PATH handling so sudo's secure_path takes precedence over /etc/environment.
Resolution: closed resolved
Reason: PR #24 was merged via commit 912d88c. Its implementation commit, 5a5f451, combined the default environment PATH with sudo secure_path and gave secure_path precedence.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When using sudo the PATH gets set to a cofigured secure_path, which is
not quite the same as the default found in /etc/environment. Redefine
default_command_environment() to be the combination of the two with the
secure path taking precendence.
By relying on this behavior, we can set /etc/environment and stop
setting the environment out for each command.
Signed-off-by: Chris Patterson <chris.patterson@canonical.com>
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #24 in commit 912d88c, updating Buildd PATH handling so sudo's secure_path takes precedence over /etc/environment. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | PR merged to fix sudo secure_path handling in PATH configuration by updating default_command_environment() to combine /etc/environment with secure_path, giving secure_path precedence. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.