privoxy: upstart to systemd conversion, actions file editing

fix missing actions and filters
haskell: package diagrams-rasterific and deps
lzo: update from 2.06 to 2.08
revert fsnotify back to 0.0.11

fsnotify changes need more testing on Darwin
sox: Enable support for FLAC and PNG.

In case you wonder: PNG support is needed for example to generate
spectograms.

For example:

sox shiny-song.flac -n spectrogram -o even-shinier.png

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Chromium patch, fixes missing header
ats2: Bump
pkgs: add Rainbowstream, a streaming command-line twitter client.

Signed-off-by: Austin Seipp <aseipp@pobox.com>
Fix pianobar license to be accurate (MIT)

This was broken, in a well-intentioned way, in 9350c1d. The maintainer
believed that the Pandora license was in conflict with nixpkg's rights
to build the package, and that it would be safer to avoid picking a
fight. However well-intentioned, though, it was still inaccurate and
unnecessary to change the metadata for the package nixexpr. I will
attempt to support this assertion through several arguments that should
hopefully be independent, such that any one of them would be convincing
enough in isolation to merit merging this commit.

1. The limits of Pandora's TOS

The legal agreement between Pandora and its users applies to the user,
not to third parties. It definitely does not have such an outrageous
scope that Pandora should be allowed to dictate what we may or may not
compile.

Furthermore, most TOS and EULA documents are completely (or at least
mostly) legally bunk. They are constructed such that using any website
or software in a typical manner will result in a violation, and the
consequences for violation are then enforced selectively. However,
when such issues go to court, the court regularly favors the user.
Legal precedent generally follows that such agreements are non-binding
scare tactics, rather than enforceable contracts.

2. Most software can be used for evil

If I buy a lockpick kit, it may have a fully open-source hardware
design, be 3D-print-able, etc. And as long as I don't use it to break
into someone else's home, it is perfectly appropriate for me to
manufacture as many copies as I want, and contribute improvements
upstream.

Conversely, if I do misuse the tools, and I am prosecuted, the person
who made the designs available online is *not* responsible for how I
used them.

If we only package things that cannot be used for evil, we'll have to
stop shipping the Linux kernel, and that could make things...
complicated. But it certainly would discourage the NSA from using NixOS.

3. Intent doesn't matter

There was an argument, in channel, that pianobar's intent is entirely
or predominantly illegal. This is not true, as I'll explain shortly,
but I'd first like to explain why intent does not matter.

First of all, intent is subjective. If someone bumps me on the street,
I may infer ill intent. But from the other person's perspective, she's
just in a rush to get from Point A to Point B.

Second, intent is not related to consequences or development
methodology. Ill intent may lead to positive consequences, and vice
versa, and in all cases the subjectivity argument applies (good for
whom? bad for whom?).

4. Pianobar does not have bad intent

Just look at the project page:

    http://6xq.net/projects/pianobar/

The "most important" means of contribution, according to author, is
keeping Pandora alive. In fact, monetary donations of any kind will not
be accepted.

This seems like it's in conflict with one of the most popular features
of the software - an ad-free experience. But pianobar actually has a
better experience when you have a paid Pandora account - higher-quality
streams become available. Pianobar is fully compatible with paid
accounts, and if the developer does not pay for his Pandora account, I
will eat my hat.

Furthermore, a command line client enables more people to use Pandora in
more ways than the stock Pandora client allows. The stock client is
written in Flash, and is slow, resource-hungry, and useless on a
headless server. Pianobar can be used on just about any hardware, and
there are several hardware recipes listed on the project page which
provide straightforward Pandora-based music appliances, using pianobar's
minimal footprint and remote-control-ability.

Because it opens up more use cases and improves the experience for paid
users, it's actually arguable whether pianobar is "bad for Pandora",
when it clearly *could* be the opposite. It is also probably fair to
note that pianobar has been around for awhile, and Pandora has never
expressed an interest in picking a legal fight with it, or even blocking
pianobar from working.

5. Pianobar's source really is MIT-licensed

It is disingenuous to say that pianobar is nonfree. It's absolutely free
software, you can verify the license content against the MIT license
text for yourself. It is developed and distributed as free and open
source software.

The extent of its 'nonfreedom' is that it interacts with a nonfree
service, in ways that the nonfree service may not allow for in their
TOS. To block it on these grounds, would be like blocking Libreoffice
for its Microsoft Word compatibility, or preventing users from visiting
websites that say "this site only for use with IE7".

------------

In summary, we should strive for technical accuracy, rather than
allowing a third-party pseudocontract that does not apply to us, to
dictate what we may or may not package for our users (who may or may not
use it in a way that benefits Pandora).
licenses: comment about two versions of MIT

I decided to follow spdx.org and not to differentiate those two.
Packages would often have the wrong version anyway.
nanoblogger: adding version 3.5-rc1
Merge pull request #3871 from robberer/pkgs/nanoblogger

nanoblogger: adding version 3.5-rc1
Merge pull request #3840 from bergey/diagrams-rasterific

haskell: package diagrams-rasterific and deps
chromium: Remove all NSAPI browser wrappers.

Chromium doesn't support NSAPI anymore, so it doesn't make sense to keep
the wrappers, especially because some of them trigger bugs in more
recent versions of Chromium.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
chromium: Update beta and dev to latest versions.

beta: 37.0.2062.94 -> 38.0.2125.24 (builds fine, tested)
dev:  38.0.2125.8  -> 39.0.2138.3  (builds fine, tested)

Introduces the new version 39 and finally separates stable/beta again.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
axis: remove the unused vulnerable version 1.3
Merge pull request #3344 from ehmry/privoxy

privoxy: upstart to systemd conversion, actions file editing
Merge pull request #3857 from Fuuzetsu/lzo

lzo: update from 2.06 to 2.08
Adding gulp and git-run to node-packages.json — failed to regenerate node-packages-generated.nix, though; but the next succesful regeneration will actually add these packages