pam: Add logFailures option for adding pam_tally to su
Fixes to make basic builds on Cygwin work again + additions to support x86_64-cygwin
Fix perl compilation
Add namecoin cryptocurrency
Added Sphinx Search package
Google hangouts: Bump to 5.4.2.0

Verified working with Firefox, however it still doesn't work with
Chromium because of the NPAPI vs PPAPI thing.

Chrome's Pepper Plugin API doesn't seem to look for
plugins in the MOZ_PLUGIN_PATH, anyway I left them there for others to
find the solution :-)
Remove non-cpufreq_* modules since they are loaded by udev.
rsync: sha256 for the patch was updated
liquidfun: added google liquidfun (a box2d fork)
liquidfun: updated url and license
my-env: Preserve http_proxy and ftp_proxy variables

There are few build scripts which set them to `nodtd.invalid` to disable
downloading files by buildscript. But for user environment we should
restore original values
prevent usage of binutils on darwin
Added gmock (Google Mock) package to complement gtest package.
systemd: Apply backport fixes

In particular, added a few patches that improve systemd-nspawn
container behaviour.
Containers: Fix reboot and poweroff

Previously "machinectl reboot/poweroff" brutally killed the container,
as did "systemctl stop/restart". And reboot didn't actually work. Now
everything is fine.
Containers: Don't remount /
Containers: Clean up veth interfaces
systemd: Apply a patch that improves systemd-nspawn startup notification

Systemd-nspawn now sends startup notification *after* it has forked
the container init process and performed initialisation (such as
creating veth network interfaces).
Containers: Use systemd-nspawn startup notification

This prevents the container unit startup from hanging until timeout if
systemd-nspawn fails.
Enable parallel building for GCC.

Even if using profiledbootstrap.  This was unsafe before 4.8, and
then the documentation was not fixed on time.

The documentation got fixed here:
  https://github.com/gcc-mirror/gcc/commit/c763997f340ec1fab37ad538b57afdad4f4bf747

But the actual code was already fixed here:
  https://github.com/gcc-mirror/gcc/commit/5d2fca09d543d4b42b99fe20f412efb78cc50ec3

So this is safe both for GCC 4.8 and GCC 4.9.