On 2020-05-04 22:17, Cygwin wrote:
>> On 4/28/2020 11:43 PM,qrasmfu...@snkmail.com
>> <mailto:qrasmfu...@snkmail.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 ----daver...@acm.org <mailto:daver...@acm.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
