Vivid init system bug status

[John Meinel]

Iterating over a map is something that is likely to be deterministic in go
1.2 (which AIUI is what our CI systems use), and random in go 1.3+ (because
they force random map ordering). I would think we shouldn't do things in
"iterate over map" order in most cases.

Do you know what version of Go you're using in your custom builds?

The code that Menno did should probably have included a debug statement of
"initctl not found, trying another init system", or something to that
effect. Then you could observe that his change actually was being
triggered. *And* we have something that can give us debugging information
when someone wonders why juju isn't working with whatever init.

John
=:->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20150417/ca53abda/attachment.html>