X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org EF81B3858408
Authentication-Results:	sourceware.org;
	dmarc=fail (p=none dis=none) header.from=cl.cam.ac.uk
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=return.smtpservice.net
DKIM-Signature:	v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=smtpservice.net; s=md6hz0.a1-4.dyn; x=1641488393; h=Feedback-ID:
	X-Smtpcorp-Track:Message-ID:Date:Subject:To:From:Reply-To:Sender:
	List-Unsubscribe; bh=Xu6PRuMyqwkf/KJRnLjeo0GxaCu7Mc4PTZxOAADSVR0=; b=nhCQE9Ew
	j6qSxe0HaYMQgzkmvALsk2QiUxx08vgY1pucZA0O3Q3vZLD0PKUOvfhvAn8RJmDAB68bHQfXt+WWX
	YLPXfGGmUzXBVjvAen9NVdLIciCk5re+o2p8bUGCmMHvE8XzSdeREIj9WOBD1atqeDo7qh4do6Ph9
	2WGCwDkJcP2b/8S+utfpiBavuiadcmbs9RJlpGZlQDN3RuWY4ONt1LGvKB18sXYlgAo2JeBjNjNH5
	YuPRXO9UKF4PEs5uGH/SPhyO+frmA1prD4RayVrupHZsoCr4mPpEBccvBnROsqkacaNkorr/wYbuy
	rbzMvlZItyxBy+++3Ucf1wGV5w==;
From:	David Allsopp <David DOT Allsopp AT cl DOT cam DOT ac DOT uk>
To:	The Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	RE: Cygwin setup writing incorrect symlinks for native
Thread-Topic:	Cygwin setup writing incorrect symlinks for native
Thread-Index:	AdgC6QhEcjWCNf+4QROdOTByZUljCgALkAMAAAE1U0A=
Date:	Thu, 6 Jan 2022 16:45:18 +0000
Message-ID:	<53ca12d5a17d43089bc38ef67e4cc858@metastack.com>
References:	<000201d802ea$e13fd790$a3bf86b0$@cl.cam.ac.uk>
	<e445bd39-b4cb-5d12-1182-b142ff4efe3e AT dronecode DOT org DOT uk>
In-Reply-To:	<e445bd39-b4cb-5d12-1182-b142ff4efe3e@dronecode.org.uk>
Accept-Language:	en-GB, en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip:	[172.16.0.127]
MIME-Version:	1.0
X-Scanned-By:	MIMEDefang 2.65 on 62.31.23.242
X-Smtpcorp-Track:	1n5Vsg9EFLHUm-.16yD3n6_6ORTA
Feedback-ID:	614951m:614951apMmpqs:614951sAnFcgr92W
X-Report-Abuse:	Please forward a copy of this message, including all headers,
	to <abuse-report AT smtp2go DOT com>
X-Spam-Status:	No, score=-1.3 required=5.0 tests=BAYES_00, DKIMWL_WL_MED,
	DKIM_SIGNED, DKIM_VALID, DKIM_VALID_EF, HEADER_FROM_DIFFERENT_DOMAINS,
	KAM_EXEURI, SPF_HELO_PASS, SPF_PASS,
	TXREP autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Jon Turney wrote:
> On 06/01/2022 10:46, David Allsopp wrote:
> > Running Cygwin setup 2.912 with --symlink-type native (or
> > CYGWIN=winsymlinks:native) is not correctly translating all symlinks.
> > A default install has these faulty ones:
> >
> > /etc/pki/tls/cert.pem ->
> > \??\/etc\pki\ca-trust\extracted\pem\tls-ca-bundle.pem
> > /etc/pki/tls/certs/ca-bundle.crt ->
> > \??\/etc\pki\ca-trust\extracted\pem\tls-ca-bundle.pem
> > /etc/pki/tls/certs/ca-bundle.trust.crt ->
> > \??\/etc\pki\ca-trust\extracted\openssl\ca-bundle.trust.crt
> > /etc/ssl/certs -> \??\/etc\pki\tls\certs /lib/security/cacerts ->
> > \??\/etc\pki\ca-trust\extracted\java\cacerts
> > /usr/share/doc/groff-1.22.4/pdf/mom-pdf.pdf ->
> > \??\/usr\share\doc\groff-1.22.4\examples\mom\mom-pdf.pdf
> 
> 
> Thanks for reporting this.
> 
> Yes, it seems this is messed up where the target of the symlink is an
> absolute path.
> 
> I've uploaded setup 2.913 with an attempted fix.
> 
>    https://cygwin.com/setup/setup-2.913.x86_64.exe
>    https://cygwin.com/setup/setup-2.913.x86.exe
> 
> Please try that (you'll have to reinstall the effected packages), and see
> if it improves things for you?

Thank you! This fixes it for the Cygwin side, although the symlinks are still technically not right from the Windows side. They're still showing up prefixed \??\.

It's an age since I mucked around with those functions - IIRC the API function for writing them adds the \??\ itself and doesn't expect it to have been supplied? However, when you read the reparse point you have to remember to remove it yourself because who needs consistency :o)

C:\cygwin64>dir /s | findstr ??
01/06/2022  04:30 PM    <SYMLINK>      cert.pem [\??\C:\cygwin64\etc\pki\ca-trust\extracted\pem\tls-ca-bundle.pem]
01/06/2022  04:30 PM    <SYMLINK>      ca-bundle.crt [\??\C:\cygwin64\etc\pki\ca-trust\extracted\pem\tls-ca-bundle.pem]
01/06/2022  04:30 PM    <SYMLINK>      ca-bundle.trust.crt [\??\C:\cygwin64\etc\pki\ca-trust\extracted\openssl\ca-bundle.trust.crt]
01/06/2022  04:30 PM    <SYMLINKD>     certs [\??\C:\cygwin64\etc\pki\tls\certs]
01/06/2022  04:30 PM    <SYMLINK>      cacerts [\??\C:\cygwin64\etc\pki\ca-trust\extracted\java\cacerts]
01/06/2022  04:30 PM    <SYMLINK>      mom-pdf.pdf [\??\C:\cygwin64\usr\share\doc\groff-1.22.4\examples\mom\mom-pdf.pdf]

All best,


David

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -