Bug#697490: cloud: 697490: use sudoers.d

["Chris Fordham" <chris.fordham@rightscale.com>]

On Sun, 06 Jan 2013 18:09:49 +1100, Charles Plessy <plessy@debian.org>  
wrote:

> user cloud.debian.org@packages.debian.org
> usertags 697490 image
> retitle 697490 cloud.debian.org: use /etc/sudoers.d.
> quit
>
> > On Sun, 06 Jan 2013 15:49:17 +1100, Paul Wise <pabs@debian.org> wrote:
> >
> > >There is the /etc/sudoers.d directory in recent Debian versions:
>
> Le Sun, Jan 06, 2013 at 03:52:46PM +1100, Chris Fordham a écrit :
> > Either way, basically root is needed, so I am wondering what
> > Charles' use case is here..
>
> The problem I would like to solve is dpkg interrupting upgrades when
> /etc/sudoers is updated, because the file used in Debian's images is  
> modified.
> Using sudoers.d is indeed the good solution, that I overlooked when  
> inspecting
> the Ubuntu image.
>
> root@ip-10-148-5-107:/etc# cat sudoers.d/90-cloudimg-ubuntu
> # ubuntu user is default user in cloud-images.
> # It needs passwordless sudo functionality.
> ubuntu ALL=(ALL) NOPASSWD:ALL
Not sure what you mean by 'interrupting' but I don't see how this is a bug  
and its for Ubuntu images not Debian all the same. The original mail was  
to allow the group sudo, not ubuntu too.
For non-human upgrades to the sudo package, how the debian maintainer  
scripts manage /etc/sudoers should be checked out when using  
DEBIAN_FRONTEND=noninteractive as this file is not provided physically in  
the package itself, http://packages.debian.org/squeeze/amd64/sudo/filelist

Glad you found a solution :)

> Cheers,


--

Chris Fordham

Backline Support Engineer
RightScale Technical Services


Direct: +1 805 243 0252

Cell: +61 423 003 417

Skype: chris.fordham.rs

Email: chris.fordham@rightscale.com