Add a couple of default I2P IRC channels to Pidgin
Tails specific settings/configs for I2P

* Disable IPv6 support
* Disable i2cp (allows java clients to communicate from outside the JVM). If
  this is unset an exception for port 7654 would need to be added to ferm.
* Disable "in-network" updates (this is also done in the regular I2P packages)
* Disable the outproxies. Access to the Internet is already routed through Tor
  so these are unnecessary. If end-users have a good reason to go through one of the
  I2P outproxies they can turn them back on.
* relaxed permissions so that both the i2psvc user and the i2psvc group have access
* Boostrap through 127.0.0.1:8118
Add the amnesia user to the i2psvc group

This will allow the standard Tails user to access the I2P config directory.
Add a Tails specific initial news file

Many of the things in the default initialNews file don't apply when I2P is run
under Tails. The text can be expanded on later.
Allow access to the local 'eepsite' through FoxyProxy
Add exceptions to ferm for the standard I2P ports
Allow I2P to be installed on more than just i386

Currently packages for amd64, i386, powerpc, armel, armhf, and kfreebsd are
built/available.
I2P documentation updates
I2P: Document ferm exceptions
Restore set -e to its own line
Remove obsolete comment
typo fixes
Note that I2P packages will be added to Tails' apt repos
Remove mention of http://localhost:765[78]/*

(Changing based on revision 6a50ff18433015e0ef5bf9f97b591cd78c98e672)
Revert "Add the amnesia user to the i2psvc group"

This reverts commit f0a989226ca1b736234ab410e29e0201b5b177f4.

It was suggested that the desired access could be done with ACLs.
don't reseed (bootstrap) via Tor
don't loosen permissions on ~i2p
document the need for admin password
remove custom I2P news file
More update->upgrade.