From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32226@debbugs.gnu.org
Subject: bug#32226: shadowfile test failures
Date: Wed, 25 Jul 2018 12:48:50 +0200 [thread overview]
Message-ID: <87sh477fql.fsf@gmx.de> (raw)
In-Reply-To: <83bmayvt7f.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Jul 2018 18:59:32 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
> I ran that in batch mode. It ran for a while, and then seemed to
> hang. I interrupted it; what ended up in the log file is attached.
I could reproduce it with Emacs 26 on MS Windows.
> Let me know how can I assist you in debugging this.
> (equal
> (tramp-file-name "cluster" nil nil "c" nil "/DOCUME~1/Zaretzky/LOCALS~1/Temp/shadowfile-testsSe3Hgz" nil)
> (tramp-file-name nil nil nil "HOME-C4E4A596F7" nil "c:/DOCUME~1/Zaretzky/LOCALS~1/Temp/shadowfile-testsSe3Hgz" nil))
Well, the problem is the syntax of local file names on MS Windows, like
"c:/DOCUME~1/Zaretzky/LOCALS~1/Temp/shadowfile-testsSe3Hgz". shadowfile
uses cluster file names with syntax "/<cluster name>:<local file name>".
If the <local file name> starts with a volume letter, the resulting
string looks like a remote file name, and shadowfile is confused.
Fixing this is not trivial. Is it worth to do it? Again, I doubt that
shadowfile has worked ever on MS Windows; I believe it would be
sufficient to document this restriction.
Best regards, Michael.
next prev parent reply other threads:[~2018-07-25 10:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 17:22 bug#32226: shadowfile test failures Glenn Morris
2018-07-20 19:08 ` Eli Zaretskii
2018-07-21 10:36 ` Michael Albinus
2018-07-21 12:03 ` Eli Zaretskii
2018-07-21 12:13 ` Michael Albinus
2018-07-21 12:25 ` Eli Zaretskii
2018-07-21 12:48 ` Michael Albinus
2018-07-21 13:37 ` Eli Zaretskii
2018-07-21 13:56 ` Eli Zaretskii
2018-07-21 13:59 ` Michael Albinus
2018-07-21 14:21 ` Eli Zaretskii
2018-07-21 14:41 ` Michael Albinus
2018-07-23 9:55 ` Michael Albinus
2018-07-23 15:59 ` Eli Zaretskii
2018-07-23 16:18 ` Michael Albinus
2018-07-23 16:39 ` Eli Zaretskii
2018-07-23 16:52 ` Michael Albinus
2018-07-25 10:48 ` Michael Albinus [this message]
2018-07-25 14:47 ` Eli Zaretskii
2018-07-25 15:19 ` Michael Albinus
2018-07-21 10:33 ` Michael Albinus
2018-07-24 17:44 ` Glenn Morris
2018-07-25 11:22 ` Michael Albinus
2018-08-12 16:19 ` Michael Albinus
2018-08-12 23:46 ` Glenn Morris
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh477fql.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=32226@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).