Hello,
On Sun, 20 Mar 2016 13:47:59 +0100 Michael Meskes wrote:
> I doubt it will make it into 8, although somebody might create a
> backport. You may have to wait for the next release I'm afraid.
I'm wondering - does this mean that quotas are now unusable in jessie and we
have to wait until a
We are having a similar problem with Puppet 3.7.1 (running as a puppet-apply
provisioner under Vagrant 1.6.3).
When Puppet installs packages using apt-get, the package installation sometimes
hangs when running the mandb postinst trigger (it does not look like it is
always the same package which
Oops, looks like I missed all the previous messages (never used the Debian bug
tracker before, bear with me).
> I just discovered that this error only occurs when one disables SSL v2 [...]
Sorry about the redundant message, I see you already noticed that behaviour --
I guess I should have provid
I just discovered that this error only occurs when one disables SSL v2 using:
ssl.use-sslv2 = "disable"
Of course, this only applies if SSL is enabled with:
ssl.engine = "enable"
In other words, (re-)enabling SSL v2 is a temporary workaround if disabling
SSL completely is not feasible. Pleas
Actually, bug #572031
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572031) *has* indeed
been fixed in Debian, but only for the testing distribution (reading the
report more carefully helps...). So the solution is to backport the
patch attached to the lighttpd bug report to stable, I think.
Package: lighttpd
Version: 1.4.19-5+lenny1
Severity: important
The recent upgrade of openssl (to 0.9.8g-15+lenny11, see DSA-2141-1)
breaks lighttpd (most likely only if SSL support is enabled).
When trying to start lighttpd using /etc/init.d/lighttpd, the
following error occurrs:
2011-01-06 14
6 matches
Mail list logo