ncurses-6.2-1-mingw32-bin.tar.xz: upgrade failed
Hmm. Every one of the files, itemized from line 4, through to line 23 of your log, should have been removed by the step at line 2. The extra directory name separator, between C:\MinGW\, and /bin/... should have no effect whatsoever, so I don't know why removal would have failed ... the usual cause is that the files were not originally installed by mingw-get; another possibility is that the original installation record has been deleted, or corrupted. However, I'm not convinced that either cause is the explanation, in this case, because, having just installed ncurses-6.0-2-bin on to a Win7 VM, using mingw-get, and then upgraded to ncurses-6.2-1-bin, I see the same sequence of failures.
I will need to investigate this further, but to complete your upgrade, you may wish to manually delete each of the conflicting executables, as identified in your log, and then force a re-installation, (from the command line, noting that $ represents the prompt):
$ mingw-get install --reinstall ncurses-bin
Reply To keith
but to complete your upgrade, you may wish to manually delete each of the conflicting executables, as identified in your log, and then force a re-installation
Thanks for the quick reply. Manually removing the conflicted executables and then reinstalling the package (using the package manager gui) did the trick.
BTW: As a first attempt I tried to remove the package using the package manager gui with no effect wrt to the conflicted executables: they were still in the bin folder. Then I did as you advised.
Reply To jannick
Manually removing the conflicted executables and then reinstalling the package (using the package manager gui) did the trick.
Pleased to learn that you got it working, but I'm puzzled: how did you "reinstall" using the GUI, given that the "Mark for reinstallation" option is disabled? I guess that you must have first performed a "remove", followed by a fresh "install". I can't remember who it was, who said that "a GUI is a contrivance for making the simple difficult, and the difficult well-nigh impossible"; sometimes, the CLI really is more capable.
Reply To keith
I'm puzzled: how did you "reinstall" using the GUI, given that the "Mark for reinstallation" option is disabled? I guess that you must have first performed a "remove", followed by a fresh "install".
Correct, as I was trying to allude to in my BTW comment above.
Thanks again.
Here the log copied straight from the 'Details' window of the installation manager showing information of the only package to be upgraded. It appears that an additional path seperator in the paths breaks things.
Thanks.