On 10/12/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > On Thu, 12 Oct 2006 19:50:40 +0200, Hisham Muhammad <[EMAIL PROTECTED]> > wrote: > > > On 10/12/06, Jonas Karlsson <[EMAIL PROTECTED]> wrote: > >> On Thu, 12 Oct 2006 19:18:46 +0200, Hisham Muhammad <[EMAIL PROTECTED]> > >> > Log message: > >> > Removed redundant flag which causes errors with recent versions of > >> sudo > >> > > >> It was me that added that flag as otherwice it got the error "sudo: no > >> password for root" every time. Is that foxed in later versions of sudo? > > > > Oh, true. I just did some extra tests here and that happens. But new > > versions of sudo don't allow -u and -v. I'm changing this to run > > "true" instead of -v. It should have the same result (revalidate sudo > > so that the next sudo command can run unattended in the pipeline). > > > The interesting thing is that if one does 'sudo -v' as superuser in a > normal prompt one doesn't get this error. Is the shell Compile is runned > in started as root?
It's tricky. Trouble arises when the name of #0 is different from the one where the sudo package was compiled in. Our usual workaround is to use -u, which we can't anymore with -v. The best solution would probably be to patch sudo to use uid instead, but I thought it could be risky to do this now that we're trying to get an -rc out. Scripts are more easily tweakable, if we have to (and we're more intimate with the codebase than dealing with the sources of sudo). -- Hisham _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
