Firstly a short apology for the lack of blogs recently. With summertime and other commitments, Mageia has sadly had less time from some contributors recently.
Cauldron
Since it has been 8 weeks since the last update, there have been massive changes to Cauldron. I won’t discuss a of them here, instead, here are a few of the more recent larger changes:
- Updated Ruby stack
- Update Perl stack
- kernel 4.12.14
- llvm 4.0.1
- flatpak 0.9.12
- vim 8.0.1097
- mesa 17.2.1
There is also the update to the base toolchain, which is requiring large scale rebuilds and will likely cause some issues until everything has settled.
Feature proposals for Mageia 7 are well underway, so if you have anything you would like to see included. or have thoughts on the ideas put forward, now is the time to shape what Mageia 7 will become.
Mageia 6
Since the last roundup, there have been countless updates for Mageia 6, here are a few of the more critical fixes that have gone through QA:
- tor-0.2.9.12 – CVE fix
- tomcat-8.0.46 – CVE fixes
- bluez-5.45-2.1 – CVE fix
- ffmpeg-3.3.4 – security update
- kernel-4.9.50 – multiple CVE fixes
- flash-player-plugin-27.0.0.130 – CVE fixes
- tcpdump-4.9.2 – multiple CVE fixes
Mageia 5
Like Mageia 6, there have been many updates, again, here is a selection of the more critical fixes:
- tor-0.2.8.15 – CVE fix
- tomcat-7.0.81 – CVE fixes
- bluez-5.28 – CVE fix
- kernel-4.4.88 – multiple CVE fixes
- flash-player-plugin-27.0.0.130 – CVE fixes
- tcpdump-4.9.2 – multiple CVE fixes
Community
The recent campaign from the Free Software Foundation Europe, Public Money, Public Code, that is aiming to have code written with public funding for the public sector released under open licensing is something that Mageia is more than happy to get behind. Such goals that share so many of the principles that Mageia was founded on and that aim to help Open Source deserve all of the support that we can offer – more details available in the blog about our support.
There has also been issues with spam from fresh accounts on the wiki, so sadly we have had to restrict write access until a full solution can be found, in the meantime, if you wish to edit, please contact the doc-discuss mailing list.









