From: David Rothenberger <daveroth@acm.org>
To: cygwin@cygwin.com
Subject: Re: Update request for rdiff-backup
Date: Tue, 5 May 2020 11:38:01 -0700 [thread overview]
Message-ID: <930828f3-e65a-5ba1-1509-885e06d20905@acm.org> (raw)
In-Reply-To: <03bafa60-d782-ca7e-2df6-fb727cdacd66@snkmail.com>
On 5/4/2020 9:17 PM, Cygwin wrote:
> 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
I've fixed this and uploaded 2.0.0-2 with the fix. Please test.
> 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.
I'm don't have time to investigate this. If you think it's a bug and
have a patch you'd like me to include in the package, please let me know.
> Would you have any suggestions about how to put the output on a network
> share?
You could try mounting the network share to a local patch using /etc/fstab.
> Also, if you don't use rdiff-backup any more, have you found something
> you like better?
I don't remember why I stopped using it. It was a long time ago. I think
I just use rsync now.
--
David Rothenberger ---- daveroth@acm.org
disbar, n:
As distinguished from some other bar.
prev parent reply other threads:[~2020-05-05 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 6:43 qrasmfu8f4
2020-05-04 17:44 ` David Rothenberger
2020-05-05 4:17 ` Cygwin
2020-05-05 9:37 ` Andrey Repin
2020-05-08 6:15 ` Cygwin
2020-05-08 15:09 ` David Rothenberger
2020-05-05 15:16 ` Brian Inglis
2020-05-06 5:23 ` Cygwin
2020-05-06 13:22 ` Brian Inglis
2020-05-05 18:38 ` David Rothenberger [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=930828f3-e65a-5ba1-1509-885e06d20905@acm.org \
--to=daveroth@acm.org \
--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).