Bug #81243 | Windows mysql-installer-community file missing for version 5.6.30 | ||
---|---|---|---|
Submitted: | 29 Apr 2016 14:51 | Modified: | 11 May 2022 21:35 |
Reporter: | Michael Menefee | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL for Windows: Installer | Severity: | S3 (Non-critical) |
Version: | 5.6.30 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[29 Apr 2016 14:51]
Michael Menefee
[30 Apr 2016 7:40]
MySQL Verification Team
Hello Michael, Thank you for the report and feedback! Observed that "MySQL Installer 5.6.28" installer is available. Thanks, Umesh
[1 May 2016 11:16]
Jon Stephens
Note that if you go to https://dev.mysql.com/downloads/mysql/, selecting 5.6 and Windows shows listings for the 5.6.30 zipfiles only, plus a banner which points to https://dev.mysql.com/downloads/windows/installer/5.6.html--and on this latter page, only the 5.6.28 MSIs are listed, and only 5.549 and 5.6.28 are listed in the versions dropdown.
[14 May 2016 9:30]
Christoph Christoph
Please note that also the mysql-installer as standalone download in version 5.6.30 lists the mysql database versions x86 and 64 for 5.6.30 correctly in the update catalogue, but does not offer it as an update. It simply reports 'the newly downloaded product catalog was not applied because it does not contain any updates for the current product catalog'.
[16 May 2016 21:01]
Michael Menefee
The 5.6.30 Windows Installer is still not posted. Is there an ETA for this issue?
[23 May 2016 17:00]
stefan jodar
Am also waiting for this in order to update Oracle versions with security fixes. Been open a while guys, do we just give up and hope the next version comes out posted correctly?
[3 Oct 2017 16:15]
Javier Treviño
Posted by developer: I can see in https://dev.mysql.com/downloads/windows/installer/5.7.html that when looking for previous GA releases only the very last version for the 5.5 and 5.6 series are available. Should more GA versions be available besides the very last one in that section?
[11 May 2022 21:35]
Javier Treviño
This was reported as fixed by the MySQL Release Engineering team.