-
tor (0.4.2.7-1) unstable; urgency=medium
* New upstream version.
-- Peter Palfrader <email address hidden> Wed, 18 Mar 2020 21:33:26 +0100
-
tor (0.4.2.6-1) unstable; urgency=medium
* New upstream version.
-- Peter Palfrader <email address hidden> Fri, 31 Jan 2020 10:15:07 +0100
-
tor (0.4.2.5-1) unstable; urgency=medium
* Upload 0.4.2.x tree to unstable.
* New upstream version.
-- Peter Palfrader <email address hidden> Mon, 16 Dec 2019 10:24:22 +0100
-
tor (0.4.1.6-1) unstable; urgency=medium
* New upstream version.
* logrotate snippet: call invoke-rc.d instead of service for
service status and reload since this seems to be more in line
with Debian policy.
-- Peter Palfrader <email address hidden> Sun, 22 Sep 2019 22:27:48 +0200
-
tor (0.4.1.5-1build1) focal; urgency=medium
* No-change rebuild for libevent soname changes.
-- Matthias Klose <email address hidden> Sat, 19 Oct 2019 19:58:46 +0000
-
tor (0.4.1.5-1) unstable; urgency=medium
* New upstream version; upload 0.4.1.x to unstable.
* Fix three typos in README.Debian.
* Avoid setting DEB_HOST_ARCH_OS in debian/rules as that should be
pre-initialized nowadays.
* tor-geoipdb: change from priority extra to optional as the former is
obsolete.
* Set Standards-Version to 4.4.0.
* The fix for #930113, runit support, added an /etc/tor/conf to
set the ulimit -n when run under runit. That directory is a bad place.
It confuses users, nowhere is it apparent that only runit cares about that
directory and that e.g. sysV or systemd don't. Get rid of that
directory and the MAX_FILEDESCRIPTORS file in it and set a reasonable
default in the runit script if MAX_FILEDESCRIPTORS is not already set.
-- Peter Palfrader <email address hidden> Wed, 21 Aug 2019 09:59:54 +0200
