DO NOT REPLY [Bug 6067] New: IPv6 literal addresses broken

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=6067

           Summary: IPv6 literal addresses broken
           Product: rsync
           Version: 3.0.4
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: arekm at maven.pl
         QAContact: rsync-qa at samba.org


[arekm at tarm ~]$ rsync --version
rsync  version 3.0.5  protocol version 30
Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, symtimes

rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
are welcome to redistribute it under certain conditions.  See the GNU
General Public Licence for details.


[arekm at tarm ~]$ rsync -avP "arekm@[2001:6a0:13f:1::1]:ble" .
ssh: Could not resolve hostname [2001: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(600)
[receiver=3.0.5]


[arekm at tarm ~]$ rsync -avP -e ssh "arekm@[2001:6a0:13f:1::1]:ble" .
ssh: Could not resolve hostname [2001: Name or service not known
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at
io.c(600)[receiver=3.0.5]


[arekm at tarm ~]$ rsync -avP rsync://arekm@[2001:6a0:13f:1::1]:ble .
rsync: getaddrinfo: [2001 6: Name or service not known
rsync error: error in socket IO (code 10) at clientserver.c(124)
[receiver=3.0.5]


ps. version form in bugzilla doesn't contain released 3.0.5 version


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.