From: David Brown <david@davidwbrown.name>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Unable to install latest git version. Claims git process pid running
Date: Fri, 21 Dec 2018 14:19:12 -0600 [thread overview]
Message-ID: <7b41b16c39632660c48bffc90e171ab9@davidwbrown.name> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1812211652150.41@tvgsbejvaqbjf.bet>
Howdy Johannes, thanks for the speedy reply.
Unfortunately I have hit refresh many times in previous attempts.
Notwithstanding, the dialog maintains the error condition claiming pid
10128 must be closed prior to install.
I'm a big fan of Git but not a Windows fan in the least.
I have downloaded the latest Windows git and killing as many apps and
pids possible after Windows restart the installation goes south
nonetheless.
Please advise.
On 2018-12-21 09:55, Johannes Schindelin wrote:
> Hi,
>
> On Thu, 20 Dec 2018, David Brown wrote:
>
>> - [ ] I was not able to find an
>> [open](https://github.com/git-for-windows/git/issues?q=is%3Aopen) or
>> [closed](https://github.com/git-for-windows/git/issues?q=is%3Aclosed)
>> issue
>> matching what I'm seeing
>
> That's a new one. I saw many bug reporters simply deleting the issue
> reporting template at https://github.com/git-for-windows/git/issues/new
> (and usually then filing only very little information, definitely not
> enough to make sense of the bug report), but I never saw this bug
> reporting template being used to report a Git for Windows bug to the
> Git
> mailing list yet ;-)
>
>> ### Setup
>>
>> - Which version of Git for Windows are you using? Is it 32-bit or
>> 64-bit?
>>
>> $ git --version --build-options
>>
>> git version 2.20.0.windows.1 cpu: x86_64 built from commit:
>> 95155834166f64fe9666f2c0a4909f076080893a
>> sizeof-long: 4
>> sizeof-size_t: 8 **
>>
>> - Which version of Windows are you running? Vista, 7, 8, 10? Is it
>> 32-bit or
>> 64-bit?
>>
>> $ cmd.exe /c ver
>>
>> ** Microsoft Windows [Version 6.1.7601] **
>>
>> - What options did you set as part of the installation? Or did you
>> choose the
>> defaults?
>>
>> # One of the following:
>>
>> $ cat /etc/install-options.txt Editor Option: VIM Custom Editor Path:
>> Path Option: BashOnly
>> SSH Option: OpenSSH
>> CURL Option: WinSSL
>> CRLF Option: CRLFAlways
>> Bash Terminal Option: MinTTY
>> Performance Tweaks
>> FSCache: Enabled
>> Use Credential Manager: Enabled
>> Enable Symlinks: Disabled
>>
>> - Any other interesting things about your environment that might be
>> related
>> to the issue you're seeing?
>>
>> ** A so-called VDI running on a Dell WYSE **
>>
>> ### Details
>>
>> - Which terminal/shell are you running Git from? e.g
>> Bash/CMD/PowerShell/other
>>
>> ** Bash **
>>
>> - What commands did you run to trigger this issue? If you can provide
>> a
>> [Minimal, Complete, and Verifiable
>> example](http://stackoverflow.com/help/mcve)
>> this will help us understand the issue.
>>
>> ** Windows git upgrade dialog **
>>
>> - What did you expect to occur after running these commands?
>>
>> ** latest version of git installed **
>>
>> - What actually happened instead?
>>
>> ** No such pid 10128 to close therefore cancel install **
>
> This typically means that that process existed *at the time the
> installer
> checked*. If it was a short-lived process, you can check again by
> clicking
> that "Refresh" button on the lower left.
>
> Ciao,
> Johannes
>
>>
>> - If the probleminsert URL herey, can you provide the
>> URL to that repository to help us with testing?
>>
>> ** Internal company url. Windows git install dialog is issue **
>>
next prev parent reply other threads:[~2018-12-21 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 20:03 Unable to install latest git version. Claims git process pid running David Brown
2018-12-21 15:55 ` Johannes Schindelin
2018-12-21 20:19 ` David Brown [this message]
2018-12-24 19:08 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b41b16c39632660c48bffc90e171ab9@davidwbrown.name \
--to=david@davidwbrown.name \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).