Change log for spkproxy package in Ubuntu
1 → 11 of 11 results | First • Previous • Next • Last |
Deleted in focal-release (Reason: Debian #935208, py2 removal, no rdeps) |
Deleted in focal-proposed (Reason: moved to Release) |
spkproxy (1.4.8-4.4build1) focal; urgency=medium * No-change rebuild to generate dependencies on python2. -- Matthias Klose <email address hidden> Tue, 17 Dec 2019 12:46:22 +0000
Available diffs
Superseded in focal-release |
Obsolete in eoan-release |
Obsolete in disco-release |
Obsolete in cosmic-release |
Published in bionic-release |
Obsolete in artful-release |
Obsolete in zesty-release |
Deleted in zesty-proposed (Reason: moved to release) |
spkproxy (1.4.8-4.4) unstable; urgency=medium * Non-maintainer upload. * Update DH level to 10. * debian/compat: updated to 10. * debian/control: - Bumped Standards-Version to 3.9.8. * debian/rules: - Fix FTBFS about a binary-indep target. Thanks to Santiago Vila for patch. (Closes: #831930) -- Giovani Augusto Ferreira <email address hidden> Sun, 25 Dec 2016 19:10:13 -0200
Available diffs
- diff from 1.4.8-4.3 to 1.4.8-4.4 (817 bytes)
Superseded in zesty-release |
Obsolete in yakkety-release |
Published in xenial-release |
Obsolete in wily-release |
Deleted in wily-proposed (Reason: moved to release) |
spkproxy (1.4.8-4.3) unstable; urgency=medium * Non-maintainer upload. * Build using dh-python. -- Matthias Klose <email address hidden> Tue, 18 Aug 2015 18:32:35 +0200
Available diffs
- diff from 1.4.8-4.2 to 1.4.8-4.3 (556 bytes)
Superseded in wily-release |
Obsolete in vivid-release |
Obsolete in utopic-release |
Published in trusty-release |
Obsolete in saucy-release |
Deleted in saucy-proposed (Reason: moved to release) |
spkproxy (1.4.8-4.2) unstable; urgency=low * Non-maintainer upload. * Drop useless dh_python call (Closes: #715309). -- Luca Falavigna <email address hidden> Sun, 14 Jul 2013 10:21:18 +0200
Available diffs
- diff from 1.4.8-4.1 (in Ubuntu) to 1.4.8-4.2 (466 bytes)
Superseded in saucy-release |
Obsolete in raring-release |
Obsolete in quantal-release |
Published in precise-release |
Obsolete in oneiric-release |
Obsolete in natty-release |
Obsolete in maverick-release |
Obsolete in lucid-release |
Obsolete in karmic-release |
spkproxy (1.4.8-4.1) unstable; urgency=low * Non-maintainer upload. * Change dependency from python-pyopenssl to python-openssl (Closes: #494902) -- Ubuntu Archive Auto-Sync <email address hidden> Sat, 09 May 2009 22:59:23 +0100
Available diffs
- diff from 1.4.8-4 to 1.4.8-4.1 (540 bytes)
Superseded in karmic-release |
Obsolete in jaunty-release |
Obsolete in intrepid-release |
Obsolete in hardy-release |
Obsolete in gutsy-release |
Obsolete in feisty-release |
spkproxy (1.4.8-4) unstable; urgency=low * Acknowledge NMU, thanks Ana for the patch. (Closes: #380960) * Package rebuild makes it depend on python version 2.4 (Closes: #385390) * Add a new -c option to define the proxy's cache for users, this makes it easier to define an alternate location for cachedir so that administrators do not have to fiddle with the permissions of /var/cache/spikeproxy * Introduce all the options into the manpage, including the new -c option. (it previously said there was only one option, which is no longer true) * Introduce a new function in spikeProxyUI.py to setCache() that checks if the cache directory exists and is writable. Previously it will only check if it existed and would not complain about it not being writable until you browsed through the proxy. This makes the error message of the cachedir not being useful for the user appear as soon as the program startups. * Remove all compile Python files under ntlm/. This makes it possible to rebuild the package after running spikeproxy locally (within package sources)
spkproxy (1.4.8-3) unstable; urgency=low * Do some error interception with respect of the cache dir. Also, add a symlink from /usr/share/spikeproxy/cache to /var/cache/spikeproxy/. I'm doing this after Ubuntu improperly fixed a bug (Malone: #3397) which nobody forwarded to me. And still the reporter said that I'm not responding, go figure. * Have spikeproxy intercept the error when trying to create cache directories under /var/cache/spikeproxy/ and print some additional information (point users to README.Debian!) * Add some more information in README.Debian on how to setup spikeproxy and why the default is the way it is. -- Steve Kowalik <email address hidden> Mon, 10 Jul 2006 10:21:22 +0100
spkproxy (1.4.8-2ubuntu2) dapper; urgency=low * Set self.cachedir="/usr/share/spikeproxy/cache". (Malone: #3397) -- Steve Kowalik <email address hidden> Mon, 30 Jan 2006 00:47:48 +1100
Superseded in dapper-release |
spkproxy (1.4.8-2ubuntu1) dapper; urgency=low * Resynchronise with Debian. -- Daniel T Chen <email address hidden> Tue, 08 Nov 2005 10:27:51 +0000
spkproxy (1.4.7-8ubuntu1) hoary; urgency=low * Rebuild against python2.4 * Ctandards Version 3.5.6 -> 3.6.1.1 -- Charles Majola <email address hidden> Thu, 17 Mar 2005 15:06:22 +0200
spkproxy (1.4.7-7) unstable; urgency=low * Added python-pyopenssl dependencies (Closes: #222409, #222211) -- Javier Fernandez-Sanguino Pen~a <email address hidden> Fri, 28 Nov 2003 22:39:44 +0100
1 → 11 of 11 results | First • Previous • Next • Last |