Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)
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 computer just re-connected to the other (IPv4-capable) network. With this commit (patch applies), IPv6 seems to work: https://github.com/mcabber/loudmouth/commit/95078ef12ab30735b4280675837c64686cf9faaa
Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)
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 IPv4, but I didn’t test it, ssh to another Debian sid box with v4+v6 was quicker). bye, //m.
Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)
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)
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 commu.teckids.org in mcabberrc. > A netcat on commu.teckids.org port 5223 works, so it’s the client. commu.teckids.org offers TLS 1.3, so I a suspect the TLS code is not up to date for TLS 1.3. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)
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 commu.teckids.org port 5223 works, so it’s the client. -- System Information: Debian Release: buster/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/lksh Init: sysvinit (via /sbin/init) Versions of packages mcabber depends on: ii libaspell15 0.60.7~20110707-5 ii libassuan0 2.5.2-1 ii libc62.28-5 ii libglib2.0-0 2.58.2-4 ii libgpg-error01.33-3 ii libgpgme11 1.12.0-6 ii libidn11 1.33-2.2 ii libloudmouth1-0 1.5.3-4 ii libncursesw6 6.1+20181013-1 ii libotr5 4.1.1-3 ii libtinfo66.1+20181013-1 mcabber recommends no packages. mcabber suggests no packages. -- no debconf information