Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

2019-02-06 Thread W. Martin Borgert
Control: reassign -1 libloudmouth1-0 Control: retitle -1 libloudmouth1-0: does not support IPv6 (fails Squeeze release goal) Control: tag -1 + patch On 2019-02-03 09:32, W. Martin Borgert wrote: > I'm in the same network, and mcabber works for me. After testing again, I believe, that my

Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

2019-02-03 Thread Thorsten Glaser
Andreas Metzler dixit: >commu.teckids.org offers TLS 1.3, so I a suspect the TLS code is not up >to date for TLS 1.3. No, I can normally connect. mcabber is my primary client because it works inside GNU screen. It just didn’t work at FOSDEM in the IPv6-only network there (the FOSDEM-legacy had

Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

2019-02-03 Thread W. Martin Borgert
On 2019-02-02 21:23, Thorsten Glaser wrote: I’m currently in the FOSDEM WLAN (IPv6-only, not FOSDEM-legacy), and I can neither connect to the Jabber server with SRV RRs nor when hardcoding commu.teckids.org in mcabberrc. I'm in the same network, and mcabber works for me.

Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

2019-02-02 Thread Andreas Metzler
On 2019-02-02 Thorsten Glaser wrote: > Package: mcabber > Version: 1.1.0-1.1 > Severity: serious > Tags: ipv6 > Justification: fails release goal > I’m currently in the FOSDEM WLAN (IPv6-only, not FOSDEM-legacy), > and I can neither connect to the Jabber server with SRV RRs nor > when hardcoding

Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

2019-02-02 Thread Thorsten Glaser
Package: mcabber Version: 1.1.0-1.1 Severity: serious Tags: ipv6 Justification: fails release goal I’m currently in the FOSDEM WLAN (IPv6-only, not FOSDEM-legacy), and I can neither connect to the Jabber server with SRV RRs nor when hardcoding commu.teckids.org in mcabberrc. A netcat on