As the upgrade path from Mageia 5 to Mageia 6 is harder than anticipated, many users are still on Mageia 5 today. We\u00a0have\u00a0therefore decided to prolong the support of Mageia 5 until\u00a0December 31st, 2017\u00a0(instead of October 31st, 2017 as announced until now).<\/p>\n
This extended support will be limited to critical security fixes for components found in most systems, such as the kernel, glibc, firefox, flash-player-plugin, etc. The exact scope will be decided for each package by the packager maintainers and security teams, based on the severity of the issue and the resources that we have in terms of packaging and quality assurance.<\/p>\n
So,\u00a0in\u00a0summary: your Mageia 5 system will not be exposed to known critical vulnerabilities until its EOL in 2 months, but the support will still be much more limited than that of Mageia 6 systems. We encourage the remaining Mageia 5 users to use this time to upgrade to Mageia 6 as soon as possible.<\/p>\n
Many users reported critical issues when upgrading complex systems to Mageia 6, especially using KDE4, NVIDIA proprietary drivers, and\/or third-party packages. Such issues can be package conflicts that prevent the upgrade from finishing properly, leaving the system in a hybrid state that may not properly survive a reboot, or they can be drivers issues that lead to the graphical X.org server failing to initialize itself, landing users on a terminal instead of the desktop environment.<\/p>\n
For this reason, we disabled the system that prompts users to upgrade via\u00a0our GUI tool\u00a0mgaonline, so only manual upgrades can be done using\u00a0our CLI tool\u00a0urpmi. We are still working on solving the main issues mentioned above to allow us to re-enable the\u00a0mgaonline upgrade path, but we want to warn users that there might still be caveats to this specific upgrade.<\/p>\n
When possible, we recommend that Mageia 5 users do a clean install of Mageia 6 on a different partition (thus keeping both systems next to each other), and copy the relevant parts of their Mageia 5 configuration (typically the hidden folders in your \/home) onto\u00a0the new system. It should also work fine to reuse the same \/home partition if it’s separate from the root partition. You can even use the same username and UID (user identifier), but keep in mind that systems upgraded from older Mageia releases might still have user IDs starting at 500, while Mageia 6 requires user IDs to start at 1000.\u00a0There’s a wiki page with some more instructions for upgrade<\/a>.<\/p>\n When in doubt, please get in touch with other community members on the forums, mailing lists or IRC, there will always be helpful people ready to help you.<\/p>\n We are sorry for the inconvenience and will work hard to provide a\u00a0more\u00a0stable upgrade path from Mageia 6 to Mageia 7.<\/p>\n","protected":false},"excerpt":{"rendered":" As the upgrade path from Mageia 5 to Mageia 6 is harder than anticipated, many users are still on Mageia 5 today. We\u00a0have\u00a0therefore decided to prolong the support of Mageia 5 until\u00a0December 31st, 2017\u00a0(instead of October 31st, 2017 as announced … Continue reading