Peter Baumgarten, le Thu 13 Mar 2014 21:33:24 -0500, a écrit :
> The reason the patch was not being applied was
> 1. The patch was not listed in debian/patches/series so it was not
> queued up.
> 2. The patch was for configure.in it no longer exists for sudo now there
> is a configure.ac
>
> So if
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
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
On Tue, 2014-03-11 at 10:15 +0100, Samuel Thibault wrote:
> Another way is to just fix lockf in glibc (for now it is just returning
> ENOSYS), it seems sudo simply locks the whole file, so it would be the
> simple case to implement.
If I did want to fix lockf in glibc where would I find the lockf
