[Piuparts-commits] [SCM] piuparts git repository branch, develop, updated. 0.53-22-g84e7279

[Holger Levsen]

The following commit has been merged in the develop branch:
commit 84e7279c1010cb058ab1d55e85e5241396c341bf
Author: Holger Levsen <holger at layer-acht.org>
Date:   Tue Jul 16 15:27:09 2013 +0200

    README_server.txt: be more verbose about configuring sudo. (Closes: #711155)

diff --git a/README_server.txt b/README_server.txt
index fbf428f..287e0ac 100644
--- a/README_server.txt
+++ b/README_server.txt
@@ -37,9 +37,9 @@ To set this up for yourself, the following steps should suffice:
  The key should be restricted to only allow running
  'piuparts-master' by prefixing it with
  'command="/usr/share/piuparts/piuparts-master",no-pty,no-port-forwarding'
-. Configure sudo on the slave machine to allow the slave account
- run '/usr/sbin/piuparts' as root without password (otherwise
- you'll be typing in a password all the time).
+. Configure sudo (via '/etc/sudoers.d/piuparts') on the slave machine(s)
+ to allow the slave account to run '/usr/sbin/piuparts' as root without
+ password (otherwise  you'll be typing in a password all the time).
 . Run '/usr/share/piuparts/piuparts-slave' on the slave accounts.
  Packages that are installed want to use '/dev/tty', so you can't
  do this from cron. Also, you'll want to keep an eye on what is
@@ -60,7 +60,7 @@ repository. Consider setting up a local mirror, or a caching proxy for http
 and apt-get, to reduce the load. Running multiple slaves on a fast host can
 easily saturate a 100 MBit link.
 
-Edit /etc/sudoers.d/piuparts to grant permissions to the piupartss user.
+Edit '/etc/sudoers.d/piuparts' to grant permissions to the piupartss user.
 Start the server using /usr/sbin/piuparts_slave_run, which will launch a
 'screen' session. The slave will launch a master process via ssh, as needed,
 to retrieve work and return results. Use /usr/sbin/piuparts_slave_join to
diff --git a/TODO b/TODO
index 878c3bb..ea8a1bb 100644
--- a/TODO
+++ b/TODO
@@ -15,8 +15,8 @@ for 0.5x:
 
 - make piuparts-master + piuparts-slave packages work with documented steps:
   - do not enable sudoers.d/piuparts-slave in p-s.deb, neither the cronjobs.
-    - this is manual work one has done once after installation. we should
-      whats needs to be done how.
+    - this is manual work one has done once after installation. we only
+      document whats needs to be done how.
   - the shipped crontabs are not suitable from cron.d/ due to missing user
     column -> provide instructions how to install them as piuparts(s|m) user
     from /u/s/doc/p-(s|m)/examples
diff --git a/debian/changelog b/debian/changelog
index fee04f6..5e6ddeb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,8 @@ piuparts (0.54) UNRELEASED; urgency=low
   [ Holger Levsen ]
   * known_problems: fix some adequate patterns. 
   * piuparts-master: recommend apache2 | httpd.
+  * README_server.txt: be more verbose about configuring sudo.
+    (Closes: #711155)
 
   [ David Steele ]
   * pupartslib/packagesdb.py

-- 
piuparts git repository