On Sat, Feb 20, 2010 at 10:53 PM, Charles Lepple <[email protected]> wrote: > On Feb 20, 2010, at 5:47 PM, Alexander Gordeev wrote: > >> Arjen de Korte <[email protected]> пишет: >> >>> Citeren Charles Lepple <[email protected]>: >>> >>>> the NUT_CHECK_IPV6 macro sets "nut_have_ipv6", but then references >>>> "nut_with_ipv6" which is not assigned until after NUT_CHECK_IPV6 >>>> is called. >>> >>> Ouch! Sorry about that. Fixed in the trunk. I think we want to >>> re-release nut-2.4.2, because this probably is going to hit a great >>> number of people. >> >> Why not do 2.4.3 release? This is just numbers :) > > Or 2.4.2.1, or... > > I would like to try running the IPv6 code on my test machines before we > re-release (since IPv6 was broken for a while on FreeBSD without the ports > tree patches). That will probably be Sunday evening at the earliest.
I did some testing from OS X to FreeBSD 8, and also from Ubuntu 8.04 to the same FreeBSD box which was only listening on an IPv6 link-local address, and I think r2365 (Arjen's commit after the 2.4.2 tag) results in a working IPv6 setup (both at build time and runtime). Arnaud, any opposition to releasing 2.4.2.1 (or whatever we end up calling it) with Arjen's IPv6 detection patch? -- - Charles Lepple _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
