From Mageia wiki
(Redirected from Mageia 5 Release Notes)
Jump to: navigation, search


Drakconf multiflag.png
Other languages
Deutsch ; English ; Español ; Français ; Polski ; Türkçe


Introduction

Available installation media

Mageia has two distinct installation media types:

  • Classical ISOs (DVD 32bit, DVD 64bit, dual arch DVD), which use the DrakX traditional installer. Only the 32bit and 64bit DVD ISOs contain all non-free drivers. The dual arch ISO is intended for advanced users who need a small installation medium, therefore only network proprietary drivers are included. You will have to add remote non-free media if you need more drivers.
  • Live ISOs, which can be used to preview the distribution and (optionally) install Mageia on your hard drive. Live media come with either the KDE or GNOME desktop environments. The Live DVDs contain all supported locales and many packages, while the Live CDs are only in English and 32bit.

All ISO images can be either burned to a CD/DVD or dumped on a USB flash drive.

For more information, please have a look at our installation media wiki page.

You will find the different download options on the Mageia 5 download page: direct (FTP and HTTP) and BitTorrent downloads are available.

The Mageia online repositories

The Mageia software sits in three different repositories/media, depending on the type of license applied to each package. Here's an overview of those repositories:

  • Core: The Core repository includes packages with free-open-source software, i.e. packages licensed under a free-open-source license, the set of the "Core" media along with "Core Release" and "Core Updates" are available by default.
  • Nonfree: The Nonfree repository includes packages that are free-of-charge, i.e. Mageia may redistribute them, but they contain closed-source software (hence the name - Nonfree). For example this repository includes NVIDIA and AMD/ATI graphics card proprietary drivers, firmware for various WiFi cards, etc.
    The Nonfree media set is added by default but not enabled by default.
  • Tainted: The Tainted repository includes packages released under a free license. The main criteria for placing packages in this repository is that they may infringe on patents and copyright laws in some countries, e.g. multimedia codecs needed to play various audio/video files; packages needed to play commercial video DVD, etc.
    The Tainted media set is added by default but not enabled by default, i.e. it's completely opt-in; so check your local laws before using packages from this repository.
    This repository is only added for the convenience of the users. This repository is to Mageia what PLF was to Mandriva users or RPM Fusion is to Fedora users.

Please also note, that on a 64 bit system, the 32 bit repositories are also added. If the nonfree or tainted 64 bit repositories are enabled, the corresponding 32 bit repositories should also be enabled, as they are needed by some packages, such as skype or playonlinux.

Major new features

  • Installation on UEFI machines is now supported out of the box.
  • grub2 (optional and not the default) should now work better out of the box, detect other installed operating systems and add them to grub2 boot menu.
  • Lots of bug fixes in the installer and the control center, including bugs dating back from before the Mageia fork that the work on UEFI support made prominent.
  • Btrfs is now supported as a primary filesystem, though ext4 remains the default - when selecting it for /boot (or / without a separate /boot partition) grub2 will be automatically chosen and configured.
  • We now use the standard Adwaita theme instead of Oxygen-gtk, as the latter is broken with gtk+-3.14.
  • Packaging:
    • We now use the new standard for weak dependencies.
    • Our packages’ spec files use the new standard for dependencies exclusion (making them more similar to Fedora/Suse/etc. packages).

Installation

Support for Alpha/IA64/PPC/SPARC was dropped from the installer, but this is invisible to the users since Mageia never offered those architectures to install to.

Stage 1

  • Include the paravirtual network driver for Hyper-V.
  • We now automatically load the platform driver.

Stage 2

  • We now use the Adwaita theme instead of the Oxygen-gtk theme.
  • UEFI integration now works out of the box (see below).
  • The installer does not crash when running inside Virtual PC (it always worked fine under Hyper-V).
  • Input devices:
    • We now rely on the modern evdev driver (+udev) for input devices instead of the old mouse & keyboard drivers.
    • Wacom tablets should work better (we now use the proper Wacom driver again).
    • Synaptics touchpads should now work during install (mga#11524).
  • Users are now created with User-IDs (= UIDs) starting at 1000 instead of the previous 500.
  • Partitioning:
    • New default "simple" partitioning scheme with more space for the root partition (see "Automatic partitioning" below)
    • Allow btrfs for / without separate /boot with grub2 (mga#15374)
    • Add "nofail" option to "foreign" mountpoints to avoid unwanted recovery mode (mga#10179)
    • Many improvements were done for GPT partitioning (see below)
    • Don't guess a drive letter for ESP partitions & recovery partitions (mga#15636)
    • Use the Windows partition with the most available space on selected disk, not the last one across all disks (mga#15589)
    • Ignore special partitions:
      • on mmc (mga#15759)
      • ESP & Recovery on GPT
      • Detect Lenovo recovery & 'SYSTEM_DRV' as such (mga#1371)
    • GUI improvements:
    • Suggest up to 20GB/20% of the Windows partition (whichever is larger) vs previously 6GB/10% (mga#15589)
    • Fix creating RAID devices (mga#15400)
  • Ensure we install kernel-firmware-nonfree and/or radeon-firmware if needed (mga#15203)
  • Fix upgrade when packages are provided in several media (mga#15350)

UEFI

UEFI is now supported for 64 bits installations. Note that if you want to upgrade a previous Mageia installation which is not in UEFI, you have to do a complete installation. Direct upgrade is not supported. Moreover, running mixed UEFI and non-UEFI systems from the same bootloader is not supported (mga#16030).

A lot of work has been done in order for Mageia to install smoothly under UEFI:

  • We reuse the existing ESP or create one if needed
  • We ignore special recovery GPT partitions
  • Fix kernel booting in blind mode (mga#15291)
  • Fix taking screenshots on UEFI 24bpp framebuffer (mga#13684)
  • The rescue mode can repair UEFI installs
  • Fix installing grub2 on UEFI
  • ISO images can be dumped to a USB flash drive and booted in UEFI mode
  • It is now possible to create a custom boot.iso that performs an automatic installation (previously this was only supported on non-UEFI)

For further details on UEFI installation please refer to the wiki page Installing on systems with UEFI firmware.

GPT partitioning

Various fixes were done regarding GPT partitioning:

  • We now default to use GPT partitioning instead of full disk LVM on disks bigger than 4 TB
  • Set the proper GUID for ESP, swap, NTFS, LVM, RAID
  • We properly detect special partitions

Hardware support

  • The installer now configures the boot with "noiswmd" so that Intel soft raid works (mga#11105)
  • We manage isw_ bios fakeraids with dmraid for now (instead of mdadm) (mga#11289, mga#14330)

Automatic partitioning

Automatic partitioning of free available space now assigns much more space to the root partition. Mageia 4 and earlier used to assign up to 12 GB to the root partition, which could be confusing for some end users (as 12 GB can be quickly filled after you've installed some games or several desktop environments).

Mageia 5 now allocates up to 50 GB for the root partition when using the automatic partitioning. The ratio is about 1/3rd of the available disk space, 50 GB being the upper threshold; the rest is allocated to the /home partition (and swap up to 4 GB). If the available disk space is less than 50 GB, the partitioner will allocate everything to the root partition and will not create a separate /home partition.

Some examples:

  • 40 GB disk: 38 GB for root and 2 GB for swap
  • 64 GB disk: 20 GB for root, 41 GB for /home and 3 GB for swap
  • 128 GB disk: 40 GB for root, 84 GB for /home and 4 GB for swap
  • 256 GB disk: 50 GB for root, 202 GB for /home and 4 GB for swap

If you perform an install on a small harddisk (less than 200 GB), you might prefer manual partitioning to allocate more space for your user data (the /home partition).

Grub2 Integration

Grub2 Integration was completed:

  • We now generate a /boot/grub2/install.sh script like we do for grub-legacy (/boot/grub/install.sh)
  • It is now possible to repair a bogus grub2 installation with the rescue mode
  • A failsafe entry is added like for other bootloaders (mga#15675)
  • Log grub2 config in report.bug like for grub/lilo
  • Keep vga= parameter when switching to grub2 (mga#9888)
  • Check that there is still some place on /boot with grub2 too
  • UEFI:
    • Fix detecting grub2 on UEFI
    • Generate core.efi for UEFI

See also various things to know about it in our Errata page (some of which we could have written directly in the Release Notes, but heh, sometimes it's hard to decide where to write things).

Debugging

The installer was improved:

  • More logs regarding GPT/Grub2, e.g. partition layout before/after partitioning, mkinitrd & grub2-install failures (mga#9201, mga#15439)
  • Support loading patches from NTFS USB drives

Localisation (l10n) / Internationalisation (i18n)

  • Mageia now uses /etc/locale.conf for locale variables reference (previous releases used /etc/sysconfig/i18n)
  • Installing Mageia from a live DVD with a language setting that does not match the timezone is now better supported, both locales will be installed (mga#3723)
  • Chinese, Japanese, and Korean locales now use Source Han Sans as default font
  • Firefox and Thunderbird now automatically require the proper -l10n-xx language pack according to the installed locales-xx package. If multiple locales-xx packages are installed, the proper one should be selected to match the primary language that is configured for the system
  • The man-pages-de package has been fixed: it now contains more than 530 man pages

Manuals

  • The manuals for traditional installer and for the Mageia Control Center have been (partially) translated in many more languages, see our official documentation
  • For each missing localised screenshot in a HTML manual, the English screenshot is now used instead of no screenshot.
  • PDF and EPUB manuals will only be created when more than half of the needed localised screenshots for that manual are available

Software translations

New translations have been added, while others were improved. Thanks to our dedicated community of translators for their reliable work.

Package management

New RPM

RPM has been upgraded to 4.12.0.1. See http://rpm.org/wiki/Releases/4.12.0 for details.

New weak dependencies management

rpm-4.12 brings official support for suggests/recommends/enhances/... tags, which differs from the previous implementation we used

As it's a new implementation, old tags were renamed (eg: RPMTAG_SUGGESTS => RPMTAG_OLDSUGGESTS) and new tags were introduced (eg: RPMTAG_SUGGEST)

Our packages now use the (new) Recommends: tag instead of the (old) Suggests: one. Accordingly urpmi options have been renamed (eg: --no-suggests -> --no-recommends.

Urpmi will handle both old Suggests (as inserted by rpm < 4.12) & new Recommends tags (as inserted by rpm-4.12+). However, packages built with "Suggests:" with rpm-4.12 would use the new suggests tag which will be ignored by urpmi.

Mapping table:
rpm < 4.12.0 (old names) rpm >= 4.12.0 (new names)
RPMTAG_RECOMMENDSNAME RPMTAG_OLDRECOMMENDS​NAME
RPMTAG_SUGGESTSNAME RPMTAG_OLDSUGGESTSNAME
n/a RPMTAG_RECOMMENDNAME
n/a RPMTAG_SUGGESTNAME
  • The first column shows tags inserted by the older RPM when the spec files contain a "Suggests: " line.
  • The second column shows tags inserted by new rpm-4.12 when the spec files contain a "Suggests: " line.
  • The tags in italic are not supported by urpmi. It only supports the old "suggests" tags (second line) and the new "recommends" tags (third line).

The format of the synthesis files in media has been slightly changed. For mga5+, there are now "@recommends@" lines instead of "@suggests" ones.

New dependencies generators

For some time, RPM has supported two ways to generate dependencies when building packages:

  • the old so-called "external" generators
  • the new so-called "internal" generators

Most distributions have switched to the new "internal" generators but Mageia 4 and earlier used the old 'external' generators.

Mageia 5 uses the new "internal" generators. This brings many advantages, e.g.:

  • Building packages is faster.
  • Ability to use newer and current technologies.
  • Old, forked, rotting scripts can be replaced with newer.
  • Our specs are more compatible with Fedora/Suse ones.
  • Automatic dependencies for OCaml, and for other technologies.

For further details read:

As a side effect, the dependencies excluding mechanism has been changed. It's extensively documented here

perl-URPM & urpmi

A hard-coded limit was fixed which prevented updating mga4 to mga5 due to some packages having a provides list longer than 64k characters.

Gurpmi will now run drakbug when it crashes or segfaults, in order for us to get meaningful bug reports.

Tools

Authentication

ManaTools preview

ManaTools is a generic launcher application that can run internal or external modules, such as system configuration tools.
ManaTools is also a collection of configuration tools that allows users to configure most of their system components in a very simple, intuitive and attractive interface. It consists of some modules that can be also run as autonomous applications.
ManaTools started as a port of MCC (Mageia/Mandriva Control Center) to libYui (Suse widget abstraction library), but its aim is to give an easy and common interface to develop and add new modules based on libYui.
Every module, as well as ManaTools itself, can be run using a QT, Gtk or ncurses interface.

Available tools are:

  • manaclock as date/time manager
  • manadm as login manager configuration
  • manahost as hosts manager
  • manalog as journalct log reader
  • manaproxy as proxy manager
  • rpmdragora as rpm install manager
  • manaservice as service manager
  • dragoraUpdate as rpm update manager
  • manauser as user manager
  • manawall as firewall manager

Other

389-Directory Server

The 389 Directory Server is a high end LDAP server

  • Install the meta-package 389-ds. It will pull in the following sub-packages:
 389-ds-base 389-ds-console 389-admin 389-admin-console-doc 389-dsgw 389-admin-console 389-ds-console-doc 389-console 389-adminutil

Kolab Groupware Server

Kolab is a secure, scalable and reliable groupware server. It is formed by a number of well-known and proven components and adds intelligent interaction among them. There's a web administration interface, management of free-busy lists and resources, synchronization for several devices and more. Various clients can access Kolab, among them "Kontact" (KDE), Outlook (Windows) and Roundcube (Webmail). Best of all, Kolab is Free Software, so you are free to use, study, share and improve it. http://www.kolab.org/about

  • The version we provide meets kolab-3.3 except cyrus-imapd (needed version 2.5)
  • Install the meta-package kolab, it will pull in all requirements, including the abovementioned LDAP directory server 389-ds.

Base system

Kernel & hardware support

  • Mageia 5 ships with kernel 3.19, including the long awaited DMA-BUF + fences support (something that is needed as a base for proper upstream optimus & powerplay support).

All hardware managed by kernel-3.19 is enabled.

Wacom tablets should work better during installation. Moreover, Synaptics touchpads should now work during install bug 11524.

Proprietary Nvidia drivers

Recently, NVIDIA dropped support in their latest driver for the following range of chips: GeForce 8xxx, 9xxx and 100 to 415.
As a result, a new nvidia package had to be split out for those cards; it is now called nvidia340. Integration for this has been added to drakx11/XFdrake so the usual auto-detection for the correct driver should work again.

This means there are now three Nvidia proprietary drivers:
nvidia304 for Geforce 6xxx and 7xxx cards
nvidia340 for Geforce 8xxx, 9xxx and 100 to 415 cards
nvidia-current for Geforce 420 and later cards

If you perform an upgrade, the X.org config will be automatically fixed by the harddrake service on first boot.

Partial support for NVIDIA Optimus

Although not handled yet in the installer (see Errata for more information) and the Mageia Control Center, we have added support for NVIDIA Optimus, using the bumblebee package.

More information and known issues are described in the Errata.

init system

  • The remaining sysvinit legacy tools have been dropped.

Graphical environments

MageiaWelcome

X Window System (X11)

Mageia 5 ships with X.Org 1.16.4.

KDE

KDE 4.14.3 & Plasma 5.1.2 are provided.

It has a specific Live-DVD or can be installed from the DVD ISO (Traditional installer).

Note: see our Errata about plasma 5.

GNOME

GNOME 3.14 is provided.

It has a specific Live-DVD or can be installed from the DVD ISO (Traditional installer).

For those prefering good old GNOME2, GNOME3 also provides a "Gnome Classic" session.

LXDE

It can be installed from the DVD ISO (Traditional installer).

XFCE

It can be installed from the DVD ISO (Traditional installer) or the Dual-arch DVD ISO.

LXQT (replacing RazorQt)

LXQt is the successor of RazorQt. Upgrading from Mageia 4 to Mageia 5 will replace RazorQt with LXQT. For more details also check the Errata entry
It cannot be installed from the DVD ISO (Traditional installer) as there is simply not enough space to include all desktop environments and the packages they depend upon.
Online media need to be added to enable selection during initial installation - this is explained in installer documentation

Mate

It can be installed from the DVD ISO (Traditional installer).

Cinnamon

It can be installed from the DVD ISO (Traditional installer).

Enlightenment

It comes in its E18 latest version based on the Enlightenment Foundation Libraries.

Light window managers

Mageia 5 also provides a plethora of small and efficient window managers such as afterstep, awesome, dwm, fluxbox, fvwm2, fvwm-crystal, i3, icewm, jwm, lightdm, matchbox, openbox, pekwm, sugar, swm, windowmaker.

Office apps

Libreoffice has been updated to 4.4. See official release notes for details.

Games

In the Mageia community, our love for free software extends to open source games. A huge effort has been made during the Mageia 5 release cycle to package many new games, making Mageia 5 a very good platform for intensive and casual gamers alike. You can check Mageia App DB to see a list of all the new and updated games in Mageia 5. The following section will only give some cherry-picked examples for each game category.

New in Mageia 5

The following list is non-exhaustive.

  • Adventure/Role-playing: Arx Libertatis, Freedink, HyperRogue, Summoning Wars
  • Arcade: Bitfighter, C-Dogs SDL, Duck Marines, Knights, OpenClonk, Plee the Bear
  • Boards/Cards: Auale, DreamChess, OpenYahtzee
  • Puzzles: Beret, Chroma, Hex a Hop, KrossWordPuzzle, Simon Tatham's Puzzles (sgt-puzzles)
  • Shooter: Astro Menace, Lierolibre, Red Eclipse
  • Simulation: Freeminer, MicropolisJ, The Powder Toy, Voxelands
  • Sports: Dust Racing, Stunt Rally, Ultimate Stunts
  • Strategy: Seven Kingdoms, Colobot, OpenDungeons, OpenXcom, Pioneer

Updates spotlight

The following list is non-exhaustive.

  • Adventure/Role-playing: Crawl, Tales of Maj'Eyal, Valyria Tear
  • Arcade: Neverball, StepMania, SuperTuxKart
  • Boards/Cards: Pioneers, TuxMathScrabble, TuxWordSmith
  • Puzzles: Berusky 1 & 2, Connectagram, Cuyo
  • Shooter: Urban Terror, Warsow, Xonotic
  • Simulation: FlightGear, Minetest
  • Strategy: 0 A.D., Battle for Wesnoth, Freeciv, MegaGlest, OpenTTD

Gaming platforms and tools

Mageia comes with a set of nice gaming platforms and tools, among which:

  • Lutris, a free and open source gaming platform for Linux. It lets you install and manage your games in a unified interface, e.g. Linux games from Desura or Steam, Windows games in Wine, open source games statically compiled, etc.
  • Vapor, a free and open source distribution platform for games developed with the free LÖVE 2D game engine
  • Steam, the well-known (non-free) distribution platform for commercial games
  • New emulators: DeSmuME, FCEUX, PCSX-Reloaded, PPSSPP, Zsnes (was dropped in Mageia 3)

Education

Mageia 5 still comes with gcompris which is based on the GTK+ toolkit. We were [1] among the donors in February, 2015, to improve the graphical interface. So stay tuned; we may have some really cool stuff coming together with a Qt based version.

Software Development

GCC has been updated to 4.9.2, GDB to 7.8.1 and Valgrind to 3.10.1. Most libraries were updated to recent stable versions, such as Qt 5.4.0 and GTK+ 3.14.8. An important work has been done to simplify the Java stack which was hard to maintain in Mageia 4.

Python3 has been updated to 3.4.3, and when possible, all Python modules are provided for Python 2 and Python 3.

KDE Frameworks 5

Mageia 5 brings KDE Frameworks 5 version 5.5.

Miscellaneous

  • HandBrake - an open source video trans-coder has finally been added back into Mageia. This is possible as it no longer includes faac and fdk-aac encoders. It now also supports x265 encoding.
  • The Transmageddon video converter now supports VAAPI hardware acceleration.
  • Phototonic has been added. It is a fast, lightweight, clean looking Qt/C++ photo viewer and organizer.
  • freshplayerplugin has been added - it is a wrapper that enables firefox to use the latest pepperflash flash player plugin that comes with Google Chrome. Latest pepperflash plugin still has to be downloaded manually, as it only comes with Google Chrome and Mageia cannot ship it by default. For more details see this forum thread , which offers a script that can automatically download the latest pepperflash plugin. (It is only needed if you do not want to install the latest Google Chrome and only want to use it in firefox.)
  • The mailcap package has been completely updated and synced with Fedora
  • Amateur Radio - Additions to the selection of radio related software in this release are: xdx, freedv, chirp and splat.
  • SDR - gqrx has been added to complement gnuradio, and offers an easy entry to the world of Software Defined Radio. Support for a wide range of SDR hardware is included.
  • Thanks to Juan Luis Baptiste, official docker images for Mageia are now available at the official docker site. For more details see this mailing list post on the Mageia developer mailing list. Docker and Docker Registry are now also packaged for Mageia 5, allowing you to use and manage your containers.

Upgrading from Mageia 4

Please also read the known issues page.

Upgrading from Mageia 4 is supported, and has been fine-tuned over the past few months, so it should work. But as always, it is very advisable to back up any important data before upgrading and make sure you have made all updates of Mageia 4 (such as rpm and urpmi). Upgrading from Mageia 3 or another distribution is not supported.

If 3rd party repositories, such as Google, have been added during the use of Mageia 4, be sure to make a backup/copy of /etc/urpmi/urpmi.cfg.

There are several ways to upgrade from Mageia 4:


Warning: Upgrading an existing install using a LiveCD is NOT supported due to the LiveCD’s image being copied "as is" to the target system.

If you want to upgrade a previous Mageia installation which was NOT in UEFI, towards an UEFI-mode Mageia 5, you have to do a complete installation. Direct upgrade is not supported.


Upgrading via the Internet

The Mageia Update notification applet, Mageia Online, will notify you that a new Mageia release is available, and ask if you wish to upgrade. If you agree, the upgrade will be carried out from within your Mageia installation without any further steps being necessary.

If you have disabled the applet or it is not automatically running for some reason, you can upgrade manually either using the GUI (mgaonline) or the CLI (urpmi). Both methods are outlined below.

Fully update your system and check you have enough free space (at least 2 GB, depending of your configuration) before starting upgrade.

Upgrading online, using mgaonline (GUI)

If Mageia Online does not display a blue icon in the system tray offering you the option to upgrade to the new Mageia release:

1. Make sure that your system is fully up-to-date by applying all available updates. http://doc.mageia.org/mcc/5/en/content/MageiaUpdate.html

2. In Mageia Control Centre - Software Management - Configure Updates Frequency, make sure that the option "Check for newer default releases" is selected. http://doc.mageia.org/mcc/5/en/content/mgaapplet-config.html

3. Look in your home folder for a hidden directory, /.MgaOnline. If there is a file mgaonline in that directory, then delete that file.

After a re-boot, the blue upgrade icon should appear when Mageia Online next checks for updates.


Alternatively, you can launch the upgrade process by entering in a terminal:

su
mgaapplet-upgrade-helper --new_distro_version=5


It will notify you of the availability of the new Mageia 5 distribution, configure Mageia media sources and start migration.

Upgrading online, using urpmi (CLI)

This method is useful when the root partition is encrypted as the booted system is already decrypting the partition.

There are multiple ways of getting a Command Line Interface (CLI).

The best method for performing an upgrade is to use run-level 3 so that the X server and graphical environment is not running.

Therefore, the upgrade should be cleaner using run-level 3 than using a terminal application as fewer programs are running which could potentially mess-up the upgrade.

Run-level 3 can be enabled by appending "3" to the kernel command line in grub's menu.lst file and then rebooting the system to get a login prompt.

It is wise to run "script upgrade_log.txt" to capture the upgrade messages just in case a failure occurs. Use "exit" to quit out of "script".

Here are the general upgrade steps:

  • Remove all of the existing media sources on your system by executing this command as root in terminal:
su
urpmi.removemedia -a
  • Add the Mageia 5 online sources, either:
    • Using the MIRRORLIST method (which will select a mirror automatically based on your geographical location):
    su
    urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.5.$ARCH.list'
    (urpmi knows what to substitute for $ARCH)
    • Using a specific media mirror:
    su
    urpmi.addmedia --distrib <mirror_url>
    You can get the mirror_url using the Mageia mirrors web application.
  • Finally start upgrading:
su
urpmi --replacefiles --auto-update --auto
  • It's best to run the above command twice because in the first run some packages may be downloaded but not installed.
Note:
It is sometimes a good idea to test the upgrade before carrying it on.

With this command: urpmi --replacefiles --auto-update --auto --download-all --test all the packages are downloaded and the upgrade simulated only.
If the result is good, then upgrade for real with the command urpmi --replacefiles --auto-update --auto --download-all

Using the traditional Mageia 5 DVD to Upgrade

You can use the traditional (so non-Live) Mageia 5 DVD to do clean installs but also to upgrade from Mageia 4.

To upgrade:

It is recommended that the online repositories be set up during the upgrade as the DVD only includes a subset of the complete set of Mageia online repositories. This is especially important if you use important 32bits packages in an otherwise 64bits install, because the 64bits iso will only contain the 64bits packages, so the upgrade is likely to fail if you do not add online repositories.

Moreover, it is possible that Mageia 4 may have received an update to a later version of software than that available on the ISO. When this happens, the upgrade may fail to complete. Since, at the time the ISOs are tested, it is impossible to anticipate which Mageia 4 packages may be updated in the future, offline upgrades (i.e. upgrades attempted without setting up the online repositories) are not supported.

On the first reboot use the command 'urpmi --auto-update' to make sure all packages were updated.

Known issues

See the Errata page.

Bug reporting

We have a bug tracker, but please read the Errata before reporting any bugs. If you don't already have a Mageia account, you can create one on https://identity.mageia.org/. If you don't know, see how to report a bug.

Obsoleted packages

  • postgresql9.0, postgresql9.1, and postgresql9.2 have been dropped. Mageia 5 ships with postgresql9.3 and postgresql9.4. If you use one of the former on Mageia 4, make sure to dump your database before the upgrade, so that you can restore it once your system has been updated to postgresql9.4.
  • gwibber and couchdb packages have been dropped as they were unmaintained and not usable. The GNOME friends service should be a fine replacement for gwibber.
  • openstack has been dropped as it was unmaintained with a lot of open security issues.
  • ruby-rails has been dropped as it was unmaintained.
  • wings3d has been dropped as it does not work under Mageia 5 and the required erlang packages are missing.
  • zarafa has been dropped as there has been no feedback from upstream on required security fixes see bug 14993.
  • Unused standard C libraries have been dropped: musl, klibc, uClibc (only glibc & dietlibc are now provided).
  • django 1.4 has been dropped. Mageia 5 ships with Django 1.8.2, the actual long-term support (LTS) release for Python 2 and Python 3.

For more details on other packages that have been dropped since Mageia 4 release, please have a look at logs or details of the task-obsolete package in our Subversion repository.