Bug #91953 | MySQL Installer, Workbench 8.0.12 wont find Visual C++ 2017 Redist | ||
---|---|---|---|
Submitted: | 9 Aug 2018 12:46 | Modified: | 10 Aug 2018 23:03 |
Reporter: | stefan auckland | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL for Windows: Installer | Severity: | S2 (Serious) |
Version: | 1.4.26 | OS: | Windows (8.1 pro) |
Assigned to: | CPU Architecture: | Any |
[9 Aug 2018 12:46]
stefan auckland
[9 Aug 2018 12:47]
stefan auckland
MySQL Installer log with errors for MySQL for Visual C++ Redistributable 2017
Attachment: MySQL_Visual_CPP_2017_Redist_installerr.PNG (image/png, text), 34.91 KiB.
[9 Aug 2018 12:48]
stefan auckland
versions of Visual C++ installed
Attachment: Visual_CPP_Redist_Versions_installed.PNG (image/png, text), 37.03 KiB.
[9 Aug 2018 13:02]
stefan auckland
Similar Bugs appear to be; 85908, 89935, 89708. In "Suggested fix" the missing text should have read: "likely required for component installation, path variables or registry keys may be different or conflicting. check that this functions for having both 2015, and 2017 installed or one or the other. may need to set 2017 as primary if both are installed"
[9 Aug 2018 13:11]
MySQL Verification Team
Thank you for the bug report. Duplicate of https://bugs.mysql.com/bug.php?id=85908.
[9 Aug 2018 14:54]
stefan auckland
The bug Report #85908, is for a different version, different software and different incompatibility, not to mention appears to be closed, as solved, with no fix, and non-serious. If it was fixed prior to the release of 8.0.12, why does the issue persist?
[10 Aug 2018 16:16]
stefan auckland
Non duplicate of 85906 Could you clarify where the duplication is? Because I marked as a similar bug doesn't mean you can cop out and be lazy?
[10 Aug 2018 19:20]
MySQL Verification Team
The bug https://bugs.mysql.com/bug.php?id=85908 is in Verified status where you see it was fixed? I changed the severity to serious and I commented this bug is duplicate which means will be checked too for the developer which will do the fix and not to have several related bugs in status verified. Thanks.
[10 Aug 2018 20:23]
stefan auckland
Please forgive my tone, I may have misunderstood the definition of verified, and felt that this was being shunned ignored as the duplicate bug was closed. This is my mistake. However I am not having any rollback issues and it does appear to be a new unrelated but in its own right still. Despite having a similar root cause and work around. Again please forgive my poor tone. Thanks for your work
[10 Aug 2018 23:03]
MySQL Verification Team
Thank you for the feedback and understanding.