[Bug 50770] Unable to create symlinks to files in a nonexistent directory

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50770

--- Comment #15 from Martin Storsjö <martin at martin.st> ---
(In reply to Erich E. Hoover from comment #14)
> Created attachment 70074 [details]
> Fix relative path issue
> 
> (In reply to Martin Storsjö from comment #13)
> > (In reply to Erich E. Hoover from comment #12)
> > > This should now (hopefully) be fully fixed by staging commit
> > > 8e5c8cc63b57dbe9b2cf2ff075c12648845b22fa.
> > 
> > Thanks! I can confirm that those cases are fixed now - however a different
> > case has broken: Now creating a symlink with a target path like "../file"
> > fails (even though it should succeed, regardless of whether the file
> > "../file" relative to the link exists or not).
> 
> After investigating this a little bit, this relative symlink issue is
> actually a new issue due to an upstream change in commit
> 405666b736f7e471e301f051cfbe68bcbef7e0f6.  This commit changes the way that
> lookup_unix_name converts NT names to unix names and it now fails on
> relative paths.  I'm looking into the best way to fix this (not sure if I
> should be using another routine or adding a flag, but either way I'll try to
> get a fix out in short order.  I've attached one way to fix it (flag for
> lookup_unix_name), if you would like to give it a try.

Thanks; the attached patch does seem to fix that particular issue!

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.