From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Future setup regression caused by 'mkdir: always check-for-existence' commit
Date: Mon, 26 Aug 2019 17:04:00 -0000 [thread overview]
Message-ID: <9ac88ab3-ec12-59ac-aad7-8d6ed7d0f5aa@redhat.com> (raw)
In-Reply-To: <MWHPR21MB08452B51987E8A239851F7BEB9A10@MWHPR21MB0845.namprd21.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]
On 8/26/19 10:25 AM, Stephen Provine via cygwin wrote:
> After this change (commit b0c033bf3fae810b9e5a5c69f17bd4de63725691), the Git for Windows setup (and future Cygwin setups) do not correctly configure bash features because the post-install step for configuring the /dev directory does not work any more. It used to be that "mkdir -m 755 /dev" would succeed,
What's wrong with 'mkdir -p -m 755 /dev'? And if so, which package
needs to be patched to use that? It was unclear from your message if
this is git's postinstall or bash's postinstall or some other script
that is using mkdir without -p.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-26 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:41 Stephen Provine via cygwin
2019-08-26 17:04 ` Eric Blake [this message]
2019-08-26 17:33 ` Ken Brown
2019-08-26 18:24 ` Stephen Provine via cygwin
2019-08-26 18:24 ` Ken Brown
[not found] ` <MWHPR21MB0845123AD4012BC4D100BE47B9A10@MWHPR21MB0845.namprd21.prod.outlook.com>
2019-08-27 12:51 ` Stephen Provine via cygwin
2019-08-27 17:54 ` Achim Gratz
2019-08-26 22:13 ` Achim Gratz
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=9ac88ab3-ec12-59ac-aad7-8d6ed7d0f5aa@redhat.com \
--to=eblake@redhat.com \
--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).