On Tue, Jun 12, 2012 at 7:36 AM, Holger Levsen <[email protected]> wrote: > I want to be able to do "apt-get install..." and get a working setup.
I think we are close to being there. > >> But, honestly, other than an unchecked reference >> to ssh-keygen, I don't see a policy violation in it. ... > > yes, but it's run for every upgrade... thats why. Ultimately, I don't know that my original strategy was not the optimum one. The 'act appropriately' section of the policy could use some fleshing out. > >> I've also added a few patches resulting from issues I ran across >> setting up a new server. > > how about moving this to another branch so that one day we might maybe merge > this one? Adding more and more stuff on top of this branch makes it more and > more unlikely :( The added patches address bugs I found from recent fresh install. Without them, the package will not work out-of-the-box. > If I look at the branch dave/piuparts-server I see 15 commits. Last time it > was 7 or 8. Please merge/rebase/squash those commits. I have this staged. Look right? pick 7650ca0 Create a piuparts-server package out of the merged piatti.git files fixup 7bc9779 Use '1.0' format for the packages fixup 1515eee Update server README to explain the logs in /var/lib/piuparts fixup 43ddbf7 Rename the public links to slave_run/join to piuparts_slave_* and place in$ fixup 77f08f0 Add argument support to piuparts-server.postinstall fixup b94d703 Remove obsolete piuparts-server.preinst fixup b4849f3 sudoer files with a '.' are invalid. Change file to 'piuparts' fixup 0ce198d Add server Depends on 'screen' fixup c43c9eb Slave working directory owned by piupartss pick 0247687 Modify scripts to use /var/tmp and /var/lib/piuparts as base dirs pick e8f6218 Modify slave_run to work if the previous log doesn't exist pick 5d41ce0 piuparts-slave can ssh to master without known-hosts intervention pick 052757e piuparts-report - add ht_root to allow the root of the html docs to be modi$ pick 6b24129 detect-well-known-errors - use relative addressing for log links. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
