public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: ca-certificates postinstall permission denied error
Date: Fri, 26 Aug 2022 13:10:46 +1000	[thread overview]
Message-ID: <f2524a10-4cfa-6747-4623-860e0163b985@tpg.com.au> (raw)

Hi, Getting consistent permission denied errors on postinstall of 
ca-certificate. It appears to be oversight, out of a well-intentioned 
attempt to protect script generated reference files. There error as it 
appears in setup.log.full: 2022/08/26 11:39:07 running: 
e:\cygwin-x86_64\bin\bash.exe --norc --noprofile 
"/etc/postinstall/ca-certificates.sh" /usr/bin/ln: failed to create 
symbolic link 
'/etc/pki/ca-trust/extracted/pem/directory-hash/ca-certificates.crt': 
Permission denied /usr/bin/ln: failed to create symbolic link 
'/etc/pki/ca-trust/extracted/pem/directory-hash/ca-bundle.crt': 
Permission denied 2022/08/26 11:39:21 abnormal exit: exit code=1 The 
directory permissions are: $ ls -ld 
/etc/pki/ca-trust/extracted/pem/directory-hash/ dr-xr-xr-x 1 joebloggs 
Domain Users 0 Aug 26 11:39 
/etc/pki/ca-trust/extracted/pem/directory-hash/ I've experienced this on 
two installs, both where I run setup exe with -B, no privelege 
elevation). Both installs have had an manual manipulation of the 
directory, or its parents up to /etc. -- Regards, Shaddy


             reply	other threads:[~2022-08-26  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  3:10 Shaddy Baddah [this message]
     [not found] <0deb131e-26bd-7180-b23f-caf03387a5ea@aussiebb.com.au>
2022-08-26  3:22 ` Resend: " Shaddy Baddah
2022-08-26  6:28   ` ASSI
2022-08-29  9:36     ` Markus Hansmair

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=f2524a10-4cfa-6747-4623-860e0163b985@tpg.com.au \
    --to=lithium-cygwin@shaddybaddah.name \
    --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).