Package: opentracker-ipv6 Version: 0.0~git20210823.110868e-5 Severity: important
Dear Maintainer, I upgraded from my own build of opentracker to the Debian package (thanks for packaging!) recently, and when I tried to start the ipv6 service I got the error `V6 Tracker is V6 only!`. This stemmed from a `listen.tcp_udp = SOME-IPv4` entry that I had in there, as in my self-build the IPv4 and IPv6 daemons each used a separated configuration file, so it wasn't a issue. As listening on all is fine for this setup anyway, I commented that line out and everything worked fine. Slightly noteworthy may also be that I have `access.stats` entries with IPv4 addresses that do not cause any issues with the IPv6 daemon build, so it really seems to be limited to V6 only. Not sure what the best option to improve this would be. Having two different config files would be the least amount of packaging work, but having to manage two such files might be not so ideal for users. Maybe we could patch opentracker to not fail on listen IPs that do not match the compiled IP version, but rather just log and skip those? This would IMO provide the best user experience (besides avoiding this a bit odd dual daemon system in the first place, but "fixing" that surely is more involved), but is slightly more packaging work I guess. In anyway, this seems like a serious foot gun that user may run into if the current opentracker package from experimental enters Debian proper via unstable, so I wanted to at least report it here. cheers, Thomas
