Thomas Goirand <z...@debian.org> writes: > Without looking too much, this looks like the lack of support for some > socket options websockify is using. I don't really see how I could fix > that. Would you be able to provide a patch?
I propose downgrading exceptions here (and for tcp_keepidle and tcp_keepintvl) to warnings, as python-oslo.utils already does: https://sources.debian.net/src/python-oslo.utils/3.16.0-2/oslo_utils/netutils.py/#L389 > Also, I maintain websockify for OpenStack. Is there other fields were it > would be useful? If no, then websockify isn't interesting for these > platforms, and we shouldn't care. Your thoughts? I see the package as having at least a somewhat broader scope -- AFAICT, it remains a reverse dependency of NoVNC, which is used beyond OpenStack. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
