e96a66709a
run upload-pack, not send-pack
...
we're doing a reverse pull from the client
2014-11-18 15:25:55 -04:00
638d834df0
propellor spin
2014-11-18 15:24:03 -04:00
6cb060b653
problem running propellor --gitpush
2014-11-18 15:23:39 -04:00
ca95788019
propellor spin
2014-11-18 15:20:53 -04:00
72e8086d7e
updte
2014-11-18 15:20:28 -04:00
3d98e31919
propellor spin
2014-11-18 15:18:43 -04:00
02fc9fcca9
propellor spin
2014-11-18 15:18:26 -04:00
573c6ab4b8
propellor spin
2014-11-18 15:17:12 -04:00
9dfae00bd3
propellor spin
2014-11-18 15:15:56 -04:00
781e35a333
protocol is one line response, not multiline
...
The privdata is shown, so contains no literal newlines, so that's ok.
2014-11-18 15:14:36 -04:00
dccdf0c0f0
propellor spin
2014-11-18 15:09:35 -04:00
d5091b6082
propellor spin
2014-11-18 15:09:13 -04:00
fcfd18578f
propellor spin
2014-11-18 15:08:24 -04:00
0a6f14ef9d
propellor spin
2014-11-18 15:06:49 -04:00
bad6a8c3e6
propellor spin
2014-11-18 15:05:15 -04:00
38fc71077d
propellor spin
2014-11-18 14:14:07 -04:00
473ce8b757
Nothing means end of protocol, not protocol error
2014-11-18 14:13:52 -04:00
824d834000
propellor spin
2014-11-18 14:12:48 -04:00
aa9aa832d2
refactor
2014-11-18 14:12:07 -04:00
a0ea904ecb
changelog for last commit's changes
2014-11-18 14:01:13 -04:00
45f8ebf0ef
propellor spin
2014-11-18 13:59:50 -04:00
9463963d85
reorg
2014-11-18 13:32:33 -04:00
fef2f77daf
propellor spin
2014-11-18 13:30:12 -04:00
46076e9a37
reorg and clean up bootstrap protocol
2014-11-18 13:29:50 -04:00
edf2640f2b
propellor spin
2014-11-18 01:29:15 -04:00
e4e2f44392
propellor spin
2014-11-18 01:25:54 -04:00
a30b5a6bfd
propellor spin
2014-11-18 01:17:22 -04:00
bc6b199d53
propellor spin
2014-11-18 01:15:34 -04:00
c58b51fd94
propellor spin
2014-11-18 01:11:58 -04:00
8d995b1574
need to chain, not spin
2014-11-18 01:11:32 -04:00
e9ac2643f4
propellor spin
2014-11-18 01:06:44 -04:00
8ea43c6302
avoid renaming --boot to --sync
...
That broke updating existing systems, since --boot is what makes the remote
propellor update itself.
The hostname is no longer needed by --boot for new propellor's, but is
still passed for old ones.
Note that there will be a double run of propellor when upgrading via
--spin, because it now runs --boot followed by --spin on the remote host,
and the old --boot also satisfied all properties.
2014-11-18 01:04:41 -04:00
deb763d8e8
propellor spin
2014-11-18 01:01:56 -04:00
40f6d06f1a
Run remote propellor --spin with a controlling terminal.
...
Avoids need for hack to make ansi colors work, but also things like apt-get
and wget process bars will be displayed.
2014-11-18 01:01:50 -04:00
973025723c
propellor spin
2014-11-18 00:42:27 -04:00
1a90604851
ssh won't allocate a tty; work around
...
stdin is not a terminal, drat ssh
I don't much like this workaround
2014-11-18 00:42:12 -04:00
194785b556
propellor spin
2014-11-18 00:36:00 -04:00
4f72ee56ad
propellor spin
2014-11-18 00:31:15 -04:00
340c8d1060
propellor spin
2014-11-18 00:30:19 -04:00
e6ff8bfc47
can't rely on TERM; use hIsTerminalDevice
...
This calls an ioctl, I don't think it's very expensive.
2014-11-18 00:28:46 -04:00
d609e47fca
propellor spin
2014-11-18 00:22:23 -04:00
7b796bcb9c
enable tty over ssh
2014-11-18 00:22:05 -04:00
3968241b82
propellor spin
2014-11-18 00:19:35 -04:00
82d50a5796
Avoid outputting color setting sequences when not run on a terminal.
...
Currently TERM is checked for every message. Could be memoized, but it
would add complexity, and typical propellor output is not going to be more
than a few hundred messages, and likely this will be swamped by the actual
work.
2014-11-18 00:19:11 -04:00
fcf4ad8464
propellor spin
2014-11-17 23:57:16 -04:00
8f88d45032
propellor spin
2014-11-17 20:21:21 -04:00
fbd8ea3b3d
Git: rename isRepo to isGitDir
...
Signed-off-by: Félix Sipma <felix.sipma@no-log.org>
2014-11-17 17:02:31 -04:00
f3beea212c
Git: isRepo
...
Signed-off-by: Félix Sipma <felix.sipma@no-log.org>
2014-11-17 17:02:31 -04:00
0847118cc4
propellor spin
2014-11-17 16:42:37 -04:00
46cd2ad0e0
DigitalOcean.distroKernel property now reboots into the distribution kernel when necessary.
...
It might be better to do this check on boot to limit the time running the
DO kernel (which is not well security supported), but that has the
possibility of entering a bad reboot loop. Limiting this check to when
propellor runs avoids that, while still fixing the problem pretty fast.
2014-11-17 16:42:15 -04:00
Joey Hess
Félix Sipma