On Fri, Nov 15, 2013 at 04:15:41PM +0100, Guus Sliepen wrote: > On Sun, 27 Jan 2013 11:47:09 +0000, Dominic Hargreaves wrote: > > > > Can i recommend/request making ircd-hybrid 8 a separate package (such > > > as ircd-hybrid8)? Given that apparently version 7 and version 8 > > > servers are incompatible when peering. > > > > Only where cryptlinks are in use. > > Not so, I just upgraded one IRC daemon to version 8, and when connecting to > another server I get this message: > > 16:03 Meuk-sliepen.org- *** Notice -- Connection to > irc.uvt.nl[fec0::32:202:a5ff:feaa:f4b7] activated. > 16:03 Meuk-sliepen.org- *** Notice -- Link with > irc.uvt.nl[[email protected]] established: (Capabilities: TS KNOCK > UNKLN KLN ENCAP TBURST GLN CHW IE EX HOPS CLUSTER EOB QS) > 16:03 Meuk-sliepen.org- *** Notice -- Dropping server irc.uvt.nl due to > (invalid) command 'TBURST' with only 5 arguments (expecting 6). > > If it isn't backwards compatible, I agree with Mark that the should've been > renamed.
I am pretty sure that when I tested this, I was able to link a Hybrid-7 server to a Hybrid-8 server. However I don't have that test infrastructure about any more: my production Hybrid-7 servers use cryptlinks, which *is* known to be incompatible (see #714573). What software version is/was irc.uvt.nl running? I'm not sure that this issue, if confirmed, is sufficient to give the new server package a new name, since Hybrid-7 is no longer maintained upstream; but I'm willing to be persuaded otherwise. Cheers, Dominic. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
