And I filled
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780403 just in case.
I wonder, what would happen if the config just says "listen 80" or
"listen *:80"? It will listen in both IPv4 and IPv6 and if IPv6 isn't
available fall back gracefully to only IPv4?
Can someone test? That could be the fix for this bug.
Thanks!!!
El 13/03/15 a las 02:16, Kartik Mistry escibió:
severity 779825 important
thanks
Setting severity to important as per discussion above.
On Wed, Mar 11, 2015 at 12:28 AM, Michael Lustfield
<mich...@lustfield.net> wrote:
I've seen this in other packages such as mysql. Admittedly, it can be a bit
frustrating that an inability to cleanly update/install a package can cause
issues during an upgrade.
However, it is possible that something else may depend on a package cleanly
upgrading before it can proceed. I can think of a few cases where this could
happen.
To be perfectly honest, I'd like to make an inability to start not prevent a
clean upgrade as well. We'll definitely need to discuss it a bit. I do wish
there was a Debian policy about this because we've really just stuck with
how most packages behave.
--
Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/
From Montevideo, Uruguay, at the south of South America.
Freelance programmer and GNU/Linux system administrator, hire me!
Alternatives: iba...@codigolibre.net - http://go.to/ibaldo
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
