intrigeri authored Sep 21, 2016 and bertagaz committed Oct 30, 2016

This reverts commit e4c35183,
i.e. it reintroduces:

  * ab562fd4
  * c0bc655c
  * 80d0667a

refs: #11818

This reverts commit e4c35183,
i.e. it reintroduces:

  * ab562fd4
  * c0bc655c
  * 80d0667a

refs: #11818

This reverts commits:

* ab562fd4
* c0bc655c
* 80d0667a

The last minute attempt to include it in Tails 2.6 was a bad (too hasty)
idea, e.g. USB installations don't boot (pre-init results in
"FAT-fs (sdb1): IO charset ascii not found"). Also it seems that the
backport of Linux 4.7 hasn't gone through the proper Debian QA process.

While preparing Tails 2.6 it was discovered that our previous last
minute bump of the 'debian' snapshot (to get Jessie 8.6) caused
linux-compiler-gcc-4.9-x86 to be updated to a version from another Linux
source version (4.7) than what we planned to install (4.6), resulting in
the tagged snapshot being impossible to create since it would require
two different linux source packages which we do not support.

Note that this includes bumping the aufs4-standalone Git submodule to
the latest branch for Linux 4.7.

On the master branch we only want stuff that we have *really* released.

This reverts commit b142360a.

On the master branch we only want stuff that we have *really* released.

This workarounds #11517 for branches based on devel, and will be
needed anyway.

At this stage, there's no tagged snapshot for 2.4 so building the
'testing' branch will fail with:

    E: Failed getting release file http://tagged.snapshots.deb.tails.boum.org/2.4/debian/dists/jessie/Release

In order to build the 'testing' branch to record the .build-manifest
and SquashFS sort file, I'll have to make it UNRELEASED, temporarily.