| Summary: | sudo-trinity conflicts with sudo | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Dan Dart <dandart> |
| Component: | ubuntu | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | anchorschmidt, bimaljr, bugwatch, darrella, jayaramanmani, leoklein |
| Priority: | P1 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Dan Dart
2011-12-06 15:55:54 CST
It looks like the required functionality to use the distribution-provided sudo was added in the past year or so, so this bug can finally be addressed for R14.0. Specifically, a file can be placed in /etc/sudoers.d/ with the following contents: Defaults secure_path=/usr/local/sbin:/usr/local/bin:/opt/trinity/sbin:/usr/sbin:/opt/trinity/bin:/usr/bin:/sbin:/bin:/usr/X11R6/bin sudo-trinity should be changed to a metapackage that depends on sudo and provides the file mentioned above. The only question is how far back this change can be applied; IIRC lucid and maverick do NOT provide this new directive and would need to use the old modified sudo-trinity package. Marking as P1 and blocker as a solution is now available and must be implemented before R14.0 release. *** Bug 410 has been marked as a duplicate of this bug. *** *** Bug 240 has been marked as a duplicate of this bug. *** *** Bug 209 has been marked as a duplicate of this bug. *** This has been fixed in the R14.0 nightly builds for some time. Marking as such. |