We depend on grepping stuff from the Tor log (especially for
tordate/20-time.sh), so deleting it seems like a Good Thing(TM).

Doing this as early as possible exposes Vidalia's "broken onion" icon
to users less.

When using a bridge Tor reports TLS cert lifetime errors (e.g. when
the system clock is way off) with severity "info", but when no bridge
is used the severity is "warn". tordate/20-time.sh depends on grepping
these error messages, so we termporarily increase Tor's logging
severity when using bridge mode. If we don't do this tordate will
sleep forever, leaving Tor in a non-working state.

These are shared among multiple of our scripts.

This is a workaround for the IPv6 link-local multicast leak that was recently
discovered. Tails has no local service that listens on IPv6, so there should be
no regression, hopefully, unless one wants to play with OnionCat and VoIP,
but those of us should know how to workaround this anyway.

The documented way for "external" contributors to add custom packages is to put
them in chroot_local-packages, and once we pull we import any such package into
our APT repo and rewrite the history appropriately.

Also, the ability to add packages in there and not see them in "git status"
makes it very easy to build tainted ISO images with non-standard packages,
which makes some of us fear can lead to hard to debug situations.

Conflicts:
	debian/changelog