Re: I got visudo working
On Fri, Mar 14, 2014 at 05:21:23PM -0500, Peter Baumgarten wrote: On Fri, 2014-03-14 at 09:29 +0100, Samuel Thibault wrote: Use patch -ur between an unmodified version of sudo and your modified version. Send that to debian-h...@lists.debian.org for review, and then I sent the patch to debian-h...@lists.debian.org does that qualify me now for google summer of code to work on the hurd? What qualifies a student is the quality, seriousness and relevance of his proposal. Prior positive experience sure helps. Would you say replacing configure.in with configure.ac and adding it in a series file is enough ? -- Richard Braun
Re: I got visudo working
Peter Baumgarten, le Thu 13 Mar 2014 22:28:56 -0500, a écrit : So now, what is the PREFERRED way to generate the patch and send it upsteam? Use patch -ur between an unmodified version of sudo and your modified version. Send that to debian-h...@lists.debian.org for review, and then you'll use reportbug to submit it. Samuel
I got visudo working
to summerize my experiences with the visudo bug so far, 1. sudo will not build unless umask is something other than 000 even though /etc/login.defs says the default should be 022. I set the umask to 002 and 022 in a normal users's .profile and on both occasions sudo builds. 2. use-flock-on-hurd.diff is not in debian/patches/series file so it was never applied 3. Even if it was in series, use-flock-on-hurd.diff says to change configure.in which no longer exists. 4. I manually changed configure.ac from what the original patch said and sudo builds, I installed the resulting deb file and now visudo works! So now, what is the PREFERRED way to generate the patch and send it upsteam? signature.asc Description: This is a digitally signed message part
