fixing the amIAuthorized issues
don't print out add messages when no versions file present
download all dependencies to be on the safe side
do not close the connection
Merge branch 'devel' into packaging
api.versionsFrom may only be called once
Updated skeleton app with a reactive example and changed code style
this should fix local versionsFrom in most cases and is technically right
fetch dependencies for publish-for-arch
Client sync queue: better logic around setTimeout

In the old code, if you queued a task, did something which flushes the
queue (runTask, flush, or drain), and then queued another task, you'd
end up with two pending timeouts, rather than zero. With this change,
we're careful to never have two pending timeouts, and also to clear the
timeout if we're about to run all current tasks.
fix updateServerPackageData test
use just one connection in updateServerPackageData
replacing --mine with --maintainer
Reset data.json when server tells us to
support maintainer as an optional argument
Rename Blaze.{,_}materializeView, add _createView

_materializeView is internal.

Factor out beginning of _expandView and _materializeView into _createView to drive home the point that Views are “created” on-demand when you go to render them.

There’s really no reason to use _materializeView directly instead of Blaze.render.
don't write buildinfo.json in tropohouse

(it was basically empty anyway)

also, simpler implementation of not writing buildinfo.json in published
builds
include a data.json in the bootstrap tarball

this will allow us to react to resetData by deleting packages, without
having that be everybody's first experience
don't include buildinfo.json in tool's unipackages
wipe all packages (from this server) on resetData

note that we should NOT wipe the symlinked tool if we're running from a
release, but we haven't done that yet