chromium/update.sh: Fix spacing in cache messages.

This commit doesn't add any feature and just fixes a small annoyance which
result in messages like this:

Checking if xxx applies...no.

See that there is no whitespace between "..." and "no"? Well, the world cares
for more important things, but for me personally those minor annoyances can turn
into major annoyances.
chromium: Update to new release channels.

If you look at what changed, you'll surely notice that version 22 is now in
beta, so we have to expect things to break. And one thing that will break for
sure is the seccomp patch, because beginning with 22 the new BPF seccomp sandbox
is going to replace the mode 1 seccomp sandbox.
chromium: Drop dependency on subversion.

Versions older than 21 needed subversion in order to build. As the oldest
version we support is 21, we no longer need this dependency.
chromium: Don't use the sandbox patch on v21.

The patch doesn't apply in version 22 and newer, because mode 1 sandboxes are
connsidered "legacy" (well, apart from the fact that I'd personally prefer BPF
anyway), for reasons I wasn't able to find, yet. But let's proceed on BPF
integration and thus gain more insight on the exact reasons.
Add package: plowshare-git20120807
Merge remote-tracking branch 'upstream/master' into plowshare
Default 'jdk' and 'jre' to openjdk and openjre, respectively, on supporting systems
go: make it accept armv5tel

It doesn't build though, due to some problems fixed in go trunk. But
I failed to port them over to 1.0.2.
go: Removing an out of date comment
fetchhg: removing the nix dependency

I don't think it's required for anything. I tried once without it, and it
worked equally fine.
go: improving the expression so it works if overriden by hg src

Users might want to override the 'src' and 'name' of go from 'hg'.
I make the expression compatible with that.

Aside, I also set GOARM in the wrapper for it to build programs fine on
armv5tel by default.
chromium: Re-enable legacy sandbox for version 22.

This enables legacy seccomp sandbox by default even on chromium 22, because the
BPF sandbox is still work in progress, please see:

http://crbug.com/139872
http://crbug.com/130662

Because the BPF seccomp sandbox is used in case the legacy seccomp mode
initialization fails, we might need to patch this again, as soon as the BPF
sandbox is fully implemented to fall back to legacy seccomp and use BPF by
default.

We now have two patches for "default to seccomp" - one for Chromium 21 and one
for 22 or higher.
Merge branch 'chromium-beta-22-update'.

This updates the stable version from 21.0.1180.79 to 21.0.1180.81 and introduces
version 22/23 for the beta/dev channels respectively. This needed quite a bit of
patching because beginning in version 22, the seccomp sandbox is considered
legacy (though BPF is still unfinished) and in order to successfully build, we
need to update the patches as well.

I'm merging this right into master for two reasons:

- There are no changes to the derivation if you're building the stable version
  (which is the default), except for the upgrade to version 21.0.1180.81.
- Chromium currently has no reverse dependencies that may break due to this
  update.

This originally was one single commit (just an update of all channels) until I
discovered the seccomp BPF build failure.
haskell-test-framework: update to version 0.6.1
haskell-mathblog: drop obsolete package; it doesn't build with current versions of GHC
haskell-CouchDB: update to version 1.2
haskell-MonadRandom: update to version 0.1.8
haskell-blaze-textual: update to version 0.2.0.8
haskell-derive: update to version 2.5.11
haskell-double-conversion: update to version 0.2.0.5