2.6.39 has been uploaded to sid and deprecates -686 in favour of -486 and
-686-pae; the world is not ready for -pae yet, so we now ship -486.

Note that sid's 2.6.39 depends on sid's initramfs-tools. This situation will
probably get easier to deal with for us once this kernel reaches Debian backports.

It compresses the same as LZMA that was previously used and is now deprecated.
This needs a 2.6.38+ Debian kernel to work, which this branch will anyway need.

sid's aircrack-ng needs it.

Closes https://tails.boum.org/todo/DuckDuckGo/

This reverts commit d3ee66bb.

I was confused, which is not surprising considering the shape of the Broadcom
drivers landscape (http://wiki.debian.org/bcm43xx#Drivers).

The broadcom-sta (wl.ko) driver indeed brings support for some recent WiFi
adapters, but it doesn't content itself with conflicting with the module that
supports the same hardware (brcm80211, brcmsmac): it also conflicts with the ssb
module that is itself needed by a few other modules such as b43, b44. In short,
it seems like wl.ko breaks more hardware support than it brings.

It would previously never compile anything :/

Background info:
  http://wiki.debian.org/brcm80211
  http://wiki.debian.org/wl

User reports concur to indicate that the free brcm80211 / brcmsmac module are
not on par with Broadcom's one, unfortunately.

Installing from unstable for compatibility with newer kernels.

Additionally, the package from unstable automatically blacklists the conflicting
brcm80211 and brcmsmac modules. See Debian bugs #597786, #601009 and #611539 for
details.

It was required by onBoard which we don't ship anymore.

It seems ttdnsd needs to be poked, for some unknown reason, when Tor is
restarted. Else it's non functional, at least for some time.

Torbutton 1.4 now displays its icon in the toolbar.
No need for two redundant status displays.

These files did open a static copy of our website in a web browser.
We cannot do this anymore since that static copy is now installed in a place
that is unreachable by Windows.

Rationale: our static website cannot be copied to a FAT32 filesystem
due to filenames being too long. Changing this would be a pain.
Hence building and installing it into the chroot (-> filesystem.squashfs)
rather than into the binary_local-includes (-> iso9660 / FAT32 filesystem).

This means the documentation cannot be browsed offline from outside Tails.
However, our installer creates GPT hidden partitions, so the doc would not be
browseable from outside Tails anyway. The only usecase we really break by doing
so is browsing the documentation while running a non-Tails system, from a Tails
CD.

This is needed to make Florence work without displaying an error message on
startup.

Conflicts:
	ikiwiki-cgi.setup