severity 779825 normal thanks The initial report here was about Nginx failing to install. We've now determined this is because the user disabled IPv6 support on their system. This isn't simply a non-standard case, it's a nonsensical one. Accommodating this use case would cause headaches for pretty much every single other person that uses Nginx.
For those reasons, we won't be making any changes to accommodate this particular situation. It's worth noting that the decision to disable IPv6 support broke multiple other packages as well. This has nothing to do with Nginx. Additionally, there was mention of not failing an install/upgrade when the init script fails. I've looked into this and feel that would be a poor choice. I have managed to discover multiple cases where this can wreak havoc on large deployments. Failing an install or upgrade if the init script fails is the best option. Is there any reason to keep this open? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
