mvera <[email protected]> writes:

> I didn't accept the new version of files provided by the new version of the
> package because I didn't need any new functionnality. 

I'm sorry, but that was a poor decision.  If you're going to refuse a
package maintainer's updates, you should at least look at the changes to
see what's going on.

> The path provided to the commands is incomplete, some commands can't be
> launched

They can be launched, you just need to fully qualify their paths if they
aren't in $PATH.

> A default action that migrates my /etc/sudoers transparently and
> doesn't change the behaviour of the squeeze sudo.

I'm sorry, but this really isn't entirely possible.  

> Now i have to purge the package, remove the /etc/sudoers file and configure
> sudo again.

Or, alternatively, you could look at the differences between
/etc/sudoers and the /etc/sudoers.dpkg-dist file that should have been
left by dpkg during the upgrade, and manually update your sudoers file.

> I'm lucky I am also root on this computer.

There should be no luck involved.  Updating a system requires elevated
privs, which should be sufficient to work around upgrade issues.

We've already talked about adding something to the wheezy release notes
about the changes in sudo, I'll leave this bug open until that is done.

Bdale

Attachment: pgpuhmu7fzoNe.pgp
Description: PGP signature

Reply via email to