public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Cygwin <qrasmfu8f4@snkmail.com>
To: cygwin@cygwin.com
Subject: Re: Re: Update request for rdiff-backup
Date: Thu, 7 May 2020 23:15:34 -0700	[thread overview]
Message-ID: <85169023-ce4b-2526-b9f4-24bfa7270327@snkmail.com> (raw)
In-Reply-To: <1086641428.20200505123737@yandex.ru>

> >/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 /
> Note the single leading slash.
> Most likely, the program performs manual "normalization" of the path, which is
> not POSIX-compatible.
> POSIX explicitly declare that double leading slash is a special case, and its
> behavior is defined by the underlying system.
> If 2.0 would exhibit the same behavior, it is worth reporting upstream.

Based on my limited testing, 2.0.0-2 works fine with local directories.  
As far as i can tell it works at least as well as version 1.2.8-6.

2.0.0-2 does exhibit the same behavior for network shares.  I 
discovered, however, that there is a "native" windows version of 
rdiff-backup 
(https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.0.0), so I 
downloaded, installed, tried it.  It also exhibits the same behavior for 
network shares, so the issue is clearly not introduced by the cygwin port.

I created an issue upstream 
(https://github.com/rdiff-backup/rdiff-backup/issues/353).

Thanks to everyone for your assistance.


  reply	other threads:[~2020-05-08  6:15 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 [this message]
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

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=85169023-ce4b-2526-b9f4-24bfa7270327@snkmail.com \
    --to=qrasmfu8f4@snkmail.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).