X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org BECBD388F063
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=SystematicSw.ab.ca
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis:	v=2.3 cv=OubUNx3t c=1 sm=1 tr=0
	a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
	a=IkcTkHD0fZMA:10 a=AifuHw4_AAAA:8 a=Xbfor-7nAAAA:20 a=N54-gffFAAAA:8
	a=69wJf7TsAAAA:8 a=XMCtWQvVAAAA:8 a=UFgd5DnJ6zzt9FFDMS4A:9 a=QEXdDO2ut3YA:10
	a=wRqL2Z6UYI4A:10 a=TQfQvzNPeSgA:10 a=Ca-psUq8YRMQnqB1-2QN:22
	a=6l0D2HzqY3Epnrm8mE3f:22 a=Fg1AiH1G6rFz08G2ETeA:22 a=FVAcOTB4J8JjUTCw8RSC:22
Subject:	Re: Update request for rdiff-backup
To:	cygwin AT cygwin DOT com
References:	<eaed8841-276f-302d-e2ac-f9ecbd9401ad AT acm DOT org>
	<03bafa60-d782-ca7e-2df6-fb727cdacd66 AT snkmail DOT com>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Autocrypt:	addr=Brian DOT Inglis AT SystematicSw DOT ab DOT ca; prefer-encrypt=mutual;
	keydata=
	mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0
	LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA
	PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW
	AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO
	WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB
	BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5
	/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF
	IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5
	RSyTY8X+AQ==
Organization:	Systematic Software
Message-ID:	<75c835b1-8cad-e71f-59d5-651f78ffbf2b@SystematicSw.ab.ca>
Date:	Tue, 5 May 2020 09:16:36 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.7.0
MIME-Version:	1.0
In-Reply-To:	<03bafa60-d782-ca7e-2df6-fb727cdacd66@snkmail.com>
X-CMAE-Envelope:	MS4wfIVRKgh8ltSJdRhcHMD+7jJmMK2klDhXD2O2DxLC4uLNbxbcM71ZLxck0Dz/IprHWJxzYEcsB9GQ39Buc48/6fc32yyFduFvenK6/FT7AihG8cB6WeSs
	0KKDOIwCJuuPsLJhohdzdmnt3mvqaXUlKIl+35B2GbkO6hj3S1CXjjm4hY5NEnJRWyKzj1Jj8pBGzQ==
X-Spam-Status:	No, score=-15.5 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 045FHG2T029350

On 2020-05-04 22:17, Cygwin wrote:
>> On 4/28/2020 11:43 PM,qrasmfu8f4 AT snkmail DOT com  <mailto:qrasmfu8f4 AT snkmail DOT com> 
>> wrote:
>> >/Cygwin currently contains version 1.2.8-6 of rdiff-backup. Based on what I
>> see at https://github.com/rdiff-backup/rdiff-backup/releases, 1.2.8 is about
>> 11 years old (you'll have to click "Show 7 other tags), although it appears
>> there were no releases for 10 years. There has, however been some recent
>> activity, and version 2.0,0 was released on March 15th. Would it be possible
>> to update cygwin to version 2.0.0 of rdiff-update? /
>> I have updated rdiff-backup to 2.0.0 and pushed the new package as a
>> TEST release (since I don't use rdiff-backup anymore). Please test and
>> report back if you find any problems. I'll plan to promote it to
>> official status in a couple weeks unless you have problems.
>>
>>
>> -- 
>> David Rothenberger  ----daveroth AT acm DOT org  <mailto:daveroth AT acm DOT org>
> 
> Thanks for doing the update David.  I upgraded to rdiff-backup-2.0.0-1 and found
> that running "rdiff-backup --help" produced
> 
>    Exception 'name 'local' is not defined' raised of class '<class
>    'NameError'>':
>       File "/usr/lib/python3.6/site-packages/rdiff_backup/Main.py",
>    line 391, in error_check_Main
>         Main(arglist)
>       File "/usr/lib/python3.6/site-packages/rdiff_backup/Main.py",
>    line 406, in Main
>         local.setlocale(locale.LC_ALL, '')
> 
>    Traceback (most recent call last):
>       File "/usr/bin/rdiff-backup", line 32, in <module>
>         rdiff_backup.Main.error_check_Main(sys.argv[1:])
>       File "/usr/lib/python3.6/site-packages/rdiff_backup/Main.py",
>    line 391, in error_check_Main
>         Main(arglist)
>       File "/usr/lib/python3.6/site-packages/rdiff_backup/Main.py",
>    line 406, in Main
>         local.setlocale(locale.LC_ALL, '')
>    NameError: name 'local' is not defined
> 
> Attempting a real use of rdiff-backup gave a similar result. Looking at the
> rdiff-backup source in github as well as the python 3.6 docs, it looks you added
> line 406 in Main.py and I think it has a typo.  "local" should be "locale".
> 
> BTW, I was playing around with rdiff-backup 1.2.8-6 a couple days ago, and while
> it seemed to work fine when the destination was on a local drive, I couldn't
> figure out how to get it to work when the destination is a network share If I
> specify the destination as '//192.168.1.250/finance-backup/finance.rdiff-backup'
> I get:
> 
>      Fatal Error: Unable to create directory
>    /192.168.1.250/finance-backup/finance.rdiff-backup
> 
> but "mkdir //192.168.1.250/finance-backup/finance.rdiff-backup" works fine.
> 
> If I specify the destination as
> '\\192.168.1.250\finance-backup\finance.rdiff-backup' I get:

> Would you have any suggestions about how to put the output on a network share?

The ssh, rsync, and most Unix remote access utilities use [[user@]host:]path;
and rsync daemon processes and rdiff-backup use [[user]@host::]path specs or
URIs; see:

	http://rdiff-backup.nongnu.org/rdiff-backup.1.html

	https://rdiff-backup.net/docs/examples.html

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -