Mageia 5 EOL postponed

As the upgrade path from Mageia 5 to Mageia 6 is harder than anticipated, many users are still on Mageia 5 today. We have therefore decided to prolong the support of Mageia 5 until December 31st, 2017 (instead of October 31st, 2017 as announced until now).

“Best effort” support limited to critical security fixes

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.

So, in summary: 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.

Upgrade advice

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 server failing to initialize itself, landing users on a terminal instead of the desktop environment.

For this reason, we disabled the system that prompts users to upgrade via our GUI tool mgaonline, so only manual upgrades can be done using our CLI tool urpmi. We are still working on solving the main issues mentioned above to allow us to re-enable the mgaonline upgrade path, but we want to warn users that there might still be caveats to this specific upgrade.

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 the 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. There’s a wiki page with some more instructions for upgrade.

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.

We are sorry for the inconvenience and will work hard to provide a more stable upgrade path from Mageia 6 to Mageia 7.

This entry was posted in Mageia, QA, release. Bookmark the permalink.

Curious about Mageia? Download it, give it a try and tell us how you feel about it.

Want to bring something to it? Learn how you can contribute and donate.

18 Responses to Mageia 5 EOL postponed

  1. Pingback: Дату завершення підтримки Mageia 5 відкладено | Mageia Blog (Україна)

  2. Pingback: Se Prolonga el Soporte para Mageia 5 | Mageia Blog (Español)

  3. Jan says:

    This is what I call responsible maintainers 😉

  4. Dim says:

    Excellent! Thanks for that!

  5. Pingback: Mageia 5: Ende des Supports verschoben | Mageia Blog (Deutsch)

  6. Pingback: Mageia five GNU/Linux Working Machine to Succeed in Finish of Lifestyles on New Yr's Eve | Today Torrents

  7. Pingback: Mageia 5 EOL adiada | Mageia Blog (Português)

  8. “while Mageia 6 requires user IDs to start at 1000”.
    However the provided link says : “while Mageia 6 will work better when user IDs starts at 1000”.

    What are the real implications?

  9. Keith says:

    You mean I upgraded to Mageia 6 on Nov 1, though Mageia 5 wasn’t EOL? 🙁

    The only problems I have had with Megeia 6 are with GRUB2 (missing files cause errors on boot, resolved by using the text version rather than the graphical version) and GTK+ 3 (third-party theme problems, Wayland incompatibilities, etc.).

    • Barry says:

      In mcc ->boot -> set up boot system
      Go through the steps of setting up grub2 again and this will resolve it. This happens when you use urpmi to upgrade.

  10. Pingback: Fin de vida de Mageia 5 – Maslinux

  11. Pingback: Mageia 5’in ömrü doluyor | get GNU

  12. Pingback: O Sistema Operacional GNU/Linux Mageia 5 está para alcançar o fim da vida na véspera de Ano Novo - PortaldoSaber

  13. Thank you for a sensible approach….

  14. Pingback: Weekly roundup 2017 – week 45 | Mageia Blog (English)

  15. Pingback: Ronda Semanal 2017 – Semana 45 | Mageia Blog (Español)

  16. Pingback: Dapatkan Perbaikan Celah Keamanan Kritis, Masa EOL Mageia 5 Ditunda Hingga Akhir Tahun 2017

  17. cipha says:

    Sorry, won’t accept this.

    I already trashed a desktop system because of this mess. Even a new install messed the same PC.

    If you’re not able to provide updates for Mageia 5 after 31st of December OR can provide me an update possibility without trashing my other systems until then, I’m gone.

    There are enough distributions out there.