[12:28:02] <volans>	 jbond42: the patch to disable-puppet has a small issue when run with cumin (root user, no SUDO_USER), it sets the message to:
[12:28:06] <volans>	 'Disabled by disable-puppet - '
[12:28:11] <volans>	 cc effie 
[12:28:28] <effie>	 jbond42: I broke it!
[12:29:33] <effie>	 --force works, so I will run it and fix it 
[12:29:42] <volans>	 effie: no run with that
[12:29:47] <volans>	 enable-puppet "Disabled by disable-puppet - "
[12:29:52] <effie>	 lol lol 
[12:29:53] <volans>	 it's safer than with --force
[12:29:54] <effie>	 let me try 
[12:29:58] <volans>	 it works
[12:30:02] <effie>	 alright then 
[12:32:18] <effie>	 ok fixed it 
[12:32:20] <effie>	 thank you 
[12:32:24] <effie>	 sorry I broke you 
[12:32:46] <jbond42>	 :) that was a quick fix 
[12:33:04] <jbond42>	 seriosly though volans is there anything cumin may pass that we can use instead?
[12:33:07] <volans>	 but is a bit counterintuitive
[12:33:26] <volans>	 not really
[12:37:55] <effie>	 mm there is one more issue 
[12:38:10] <effie>	 so since my $SUDO_USER would be empty  
[12:38:27] <effie>	 I run with "installing onhost memcached - jiji"
[12:38:43] <effie>	 but I ended up with administratively disabled (Reason: 'installing onhost memcached - jiji - ');
[12:39:26] <effie>	 so if this is a root user with an empty $SUDO_USER, maybe we shouldn't add anything