Raring now open for development

[Matthias Klose]

Raring is now open for development, with syncs from unstable currently running.
The development version starts with updated versions of eglibc and python3, and 
some upload rearrangements.

  - GCC 4.7 did see some updates from the upstream branches, and supports
    x32 multilibs on amd64 and i386.

  - eglibc is updated to 2.16.1 [1]. Known issues are
    + a new macro TIME_UTC which conflicts with a macro of the same name
      in boost.
    + exposing a warning for building without any optimization, but defining
      _FORTIFY_SOURCE (currently disabled in the Ubuntu package). A check
      for _FORTIFY_SOURCE using the preprocessor without optimization now
      doesn't show the fortify support anymore.

  - Python 3.3 [2] is now the default python3 version. Packages are now
    rebuilt to use the new python version. It's the plan to drop python3.2
    support before the first raring beta release.

  - Toolchain source packages are now setup to support an aarch64 cross
    toolchain.

  - For Raring, all uploads will go to raring-proposed, and a modified
    instance of "britney" (the software that handles migration from Debian
    unstable to testing) will copy them to raring when they've been built
    everywhere and do not reduce the count of installable packages in the
    archive [3].

Please check your uploads in a raring chroot, don't just test in a quantal
environment. See [4] how to setup such a development chroot.

[1] http://sourceware.org/ml/libc-alpha/2012-06/msg00807.html
[2] http://docs.python.org/3.3/whatsnew/3.3.html
[3] https://lists.ubuntu.com/archives/ubuntu-devel/2012-October/036043.html
[4] https://wiki.ubuntu.com/DebootstrapChroot