summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorhttp://joeyh.name/2016-03-30 19:30:50 +0000
committeradmin2016-03-30 19:30:50 +0000
commitd4e8c2ceaa8e185bb713a79fe4eb94f42ae00461 (patch)
treeb7a20f9826d5e60351fd5b1273effb1219448ab7 /doc
parentbc607807f9aa7dffea4e6e3267b4874acd64747f (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/problem_with_spin_after_new_dependencies_added/comment_1_3adbcc7db82f14d10c7efaba889ab009._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/todo/problem_with_spin_after_new_dependencies_added/comment_1_3adbcc7db82f14d10c7efaba889ab009._comment b/doc/todo/problem_with_spin_after_new_dependencies_added/comment_1_3adbcc7db82f14d10c7efaba889ab009._comment
new file mode 100644
index 00000000..9020078c
--- /dev/null
+++ b/doc/todo/problem_with_spin_after_new_dependencies_added/comment_1_3adbcc7db82f14d10c7efaba889ab009._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ subject="comment 1"
+ date="2016-03-30T19:30:50Z"
+ content="""
+Well, I don't see a way around needing to release a version of propellor that fixes this bug before I can release a version of propellor that depends on the fix (by adding a new dependency on concurrent-output).
+
+So, I'll go that route. Users will need to upgrade all deployed hosts to propellor 2.17.2 first, before 3.0.0. If a user neglects to do so, and tries to update a host using propellor --spin, it will fail. The user can then either
+
+1. Wait for the cron job to run, if they set it up, which will install the deps.
+2. Manually log into the host and fix the deps by eg, cabal install concurrent-output as root.
+"""]]