From: Markus Hoenicka <markus.hoenicka@mhoenicka.de>
To: cygwin@cygwin.com
Subject: Re: updating TeXLive packages exceeds Windows path length limit
Date: Thu, 14 Nov 2013 13:31:00 -0000 [thread overview]
Message-ID: <f65a813758d64fbcf0e7806bb9bda208@mhoenicka.de> (raw)
In-Reply-To: <20131114100654.GE526@calimero.vinschen.de>
Am 2013-11-14 11:06, schrieb Corinna Vinschen:
> On Nov 14 10:25, Markus Hoenicka wrote:
>> Hi,
>>
>> I've just downloaded the latest setup-x86.exe to update my Cygwin
>> installation on a Windows XP box. While setup downloads the required
>> packages, it stops with a message saying:
>>
>> Can't open
>> \\servername\path\to\Downloads\[url_of_mirror]\path\to\texlive-collection-documentation-base-20130529-1.tar.bz2.tmp
>> for writing: No such file or directory
>>
>> Problem is, if I try to create a file with the same name manually in
>> Windows Explorer, I apparently hit the maximum allowed path length
>> just after the 't' in 'tmp'. In other words, the package filename is
>> exactly two characters too long on my system and using my closest
>> mirror. Setup exits without updating the system.
>>
>> Is there a way to fix this? I know that I can try and find a mirror
>> with a shorter URL, but I expect others to bump into the same
>> problem sooner or later.
>
> You could create a symlink in \\servername\path pointing to
> \\servername\path\to\Downloads\[url_of_mirror] to workaround this
> I guess.
>
> The only other way to fix this is to fix setup. A long time ago I
> tweaked setup to get rid of the MAX_PATH path length restriction, but
> apparently this only worked for the files to install, not for the
> archive files. I'm just looking through the setup code for downloading
> files, and it still calls the OS ANSI file API exclusively, rather then
> the UNICODE API, which is the culprit for this problem.
>
> Sigh. This is a lot of work still to do.
>
>
> Corinna
Just to close this issue gracefully: I received a patched setup from
Corinna off-list which no longer caused this problem. The problem may
thus be fixed in the next setup version.
regards,
Markus
--
Markus Hoenicka
http://www.mhoenicka.de
AQ score 38
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-11-14 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 9:26 Markus Hoenicka
2013-11-14 10:07 ` Corinna Vinschen
2013-11-14 13:31 ` Markus Hoenicka [this message]
2013-11-14 19:38 ` Christopher Faylor
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=f65a813758d64fbcf0e7806bb9bda208@mhoenicka.de \
--to=markus.hoenicka@mhoenicka.de \
--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).