SUDO_USER should be used also when calling with 'vcs commit'

Bug #1015941 reported by gizero
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
etckeeper (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

In the past a patch was submitted to have the unprivileged user calling 'sudo etckeeper' being reported as the commit author instead of root. This involved using SUDO_USER instead of USER when calling the undelying VCS command. This appear to be implemented only for 'etckeeper commit'. My workflow more frequently involves calling 'etckeeper vcs add/commit' to separate logically different changes and for documentation purpose. I can try to propose a patch for this but hints are welcome to focus on the right place to implement such a change. Reporting here because I use etckeeper (0.52) with Ubuntu server (11.04) but looking at upstream code, no related changes result in the repo.

Revision history for this message
Marc Cluet (lynxman) wrote :

Hi gizero,

Thanks for submitting this bug, I've been trying to reproduce the bug but it works as expected on a clean natty 11.04 install. I would suggest to check the bzr /or your vcs of your choice) settings for the user/users that are not behaving properly.

=================

------------------------------------------------------------
revno: 2
committer: Marc Cluet <email address hidden>
branch nick: natty /etc repository
timestamp: Thu 2012-06-21 05:42:23 -0700
message:
  test
------------------------------------------------------------
revno: 1
committer: ubuntu <email address hidden>
branch nick: natty /etc repository
timestamp: Thu 2012-06-21 05:41:11 -0700
message:
  Initial commit
=============

Marking as invalid

Changed in etckeeper (Ubuntu):
status: New → Invalid
Revision history for this message
gizero (gizero-gmail) wrote :

Hi Marc,

After checking my vcs backend configuration (I use git here), I found a misconfiguration of user settings. Now, I have a normalized behaviour of both workflows. Thank you for the valuable suggestion!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.