public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Update request for rdiff-backup
Date: Tue, 5 May 2020 09:16:36 -0600	[thread overview]
Message-ID: <75c835b1-8cad-e71f-59d5-651f78ffbf2b@SystematicSw.ab.ca> (raw)
In-Reply-To: <03bafa60-d782-ca7e-2df6-fb727cdacd66@snkmail.com>

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

  parent reply	other threads:[~2020-05-05 15:16 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 [this message]
2020-05-06  5:23       ` Cygwin
2020-05-06 13:22         ` Brian Inglis
2020-05-05 18:38     ` David Rothenberger

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=75c835b1-8cad-e71f-59d5-651f78ffbf2b@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).