Comment 40 for bug 328442

I have tested tor on hardy (using hardy-proposed) and everything works just fine.

Preparing to replace tor 0.1.2.19-2 (using .../tor_0.2.0.34-1~hardy+1_i386.deb) ...
Stopping tor daemon: ..............................tor.
Unpacking replacement tor ...
Selecting previously deselected package tor-geoipdb.
Unpacking tor-geoipdb (from .../tor-geoipdb_0.2.0.34-1~hardy+1_all.deb) ...
Setting up tor (0.2.0.34-1~hardy+1) ...

Configuration file `/etc/tor/torrc'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ? Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
      D : show the differences between the versions
      Z : background this process to examine the situation
 The default action is to keep your current version.
*** torrc (Y/I/N/O/D/Z) [default=N] ?
Installing new version of config file /etc/logrotate.d/tor ...
Installing new version of config file /etc/default/tor ...
Installing new version of config file /etc/init.d/tor ...
Raising maximum number of filedescriptors (ulimit -n) to 16384.
Starting tor daemon: tor...
May 04 13:36:20.017 [notice] Tor v0.2.0.34 (r18423). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
May 04 13:36:20.019 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
May 04 13:36:20.020 [notice] Initialized libevent version 1.3e using method epoll. Good.
May 04 13:36:20.021 [notice] Opening OR listener on 0.0.0.0:9090
May 04 13:36:20.021 [notice] Opening Directory listener on 0.0.0.0:9030
done.