From: David Sastre <d.sastre.medina@gmail.com>
To: cygwin@cygwin.com
Subject: Re: iconv capability removed from rsync 3.0.8
Date: Tue, 31 May 2011 21:03:00 -0000 [thread overview]
Message-ID: <20110531210229.GA14628@jethro.local.lan> (raw)
In-Reply-To: <4DE4AECA.3000009@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On Tue, May 31, 2011 at 11:03:06AM +0200, Fernando Molina Ortiz wrote:
> I have noticed that the iconv capability is not activated anymore in
> rsync 3.0.8, while in rsync 3.0.7 it is. When cally rsync --version,
> in 3.0.7 iconv is listed in the capabilities section, while in 3.0.8
> it appears as 'no iconv'. I use it, so I had to downgrade. Does
> anybody know why it's beed removed?
It could be a packaging issue, FWIW building from the sources enables
iconv support.
Rsync from the repo:
$ rsync --help | head
rsync version 3.0.8 protocol version 30
Copyright (C) 1996-2011 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, no iconv, symtimes
Rsync rebuild from sources:
$ ./rsync-3.0.8-1/inst/usr/bin/rsync.exe --help | head
rsync version 3.0.8 protocol version 30
Copyright (C) 1996-2011 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
--
Huella de clave primaria: AD8F BDC0 5A2C FD5F A179 60E7 F79B AB04 5299 EC56
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
prev parent reply other threads:[~2011-05-31 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1306831965.19764.ezmlm@cygwin.com>
2011-05-31 9:03 ` Fernando Molina Ortiz
2011-05-31 21:03 ` David Sastre [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110531210229.GA14628@jethro.local.lan \
--to=d.sastre.medina@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).