Wiki de Mageia

corrigido de 'traduzir' para 'atualizar'

← Older revision Revision as of 00:35, 29 August 2025 Line 1: Line 1:  [[Category: Documentation-pt-BR]] [[Category: Documentation-pt-BR]]    −{{multi language banner-pt-BR|[[Wie_man_die_richtige_Upgrade-Methode_auswählt-de|Deutsch]] ; [[How_to_choose_the_right_Mageia_upgrade_method|English]] ; [[Como elegir el Método correcto para Actualizar a una nueva versión|Español]] ; [[Comment_choisir_la_meilleure_méthode_de_mise_à_niveau-fr|français]] ;  [[Hoe kies ik de juiste methode om Mageia te upgraden-nl|Nederlands]] ; [[Como escolher o método certo para traduzir o Mageia-pt-BR|português (brasil)]] ; }}+{{multi language banner-pt-BR|[[Wie_man_die_richtige_Upgrade-Methode_auswählt-de|Deutsch]] ; [[How_to_choose_the_right_Mageia_upgrade_method|English]] ; [[Como elegir el Método correcto para Actualizar a una nueva versión|Español]] ; [[Comment_choisir_la_meilleure_méthode_de_mise_à_niveau-fr|français]] ;  [[Hoe kies ik de juiste methode om Mageia te upgraden-nl|Nederlands]] ; [[Como escolher o método certo para atualizar o Mageia-pt-BR|português (brasil)]] ; }}  +      {{introduction-pt-BR|Esta página lida com as diferentes maneiras de '''atualizar''' um sistema operacional {{prog-pt-BR|Mageia}} versão '''n para n+1''' (Não é possível atualizar para uma versão '''n''' além de '''n+1'''). O procedimento de atualização é diferente de uma atualização de pacotes simples.}} {{introduction-pt-BR|Esta página lida com as diferentes maneiras de '''atualizar''' um sistema operacional {{prog-pt-BR|Mageia}} versão '''n para n+1''' (Não é possível atualizar para uma versão '''n''' além de '''n+1'''). O procedimento de atualização é diferente de uma atualização de pacotes simples.}} Xgrind

tradução de introdução e requisitos

New page

[[Category: Documentation-pt-BR]]

{{multi language banner-pt-BR|[[Wie_man_die_richtige_Upgrade-Methode_auswählt-de|Deutsch]] ; [[How_to_choose_the_right_Mageia_upgrade_method|English]] ; [[Como elegir el Método correcto para Actualizar a una nueva versión|Español]] ; [[Comment_choisir_la_meilleure_méthode_de_mise_à_niveau-fr|français]] ; [[Hoe kies ik de juiste methode om Mageia te upgraden-nl|Nederlands]] ; [[Como escolher o método certo para traduzir o Mageia-pt-BR|português (brasil)]] ; }}

{{introduction-pt-BR|Esta página lida com as diferentes maneiras de '''atualizar''' um sistema operacional {{prog-pt-BR|Mageia}} versão '''n para n+1''' (Não é possível atualizar para uma versão '''n''' além de '''n+1'''). O procedimento de atualização é diferente de uma atualização de pacotes simples.}}

== Requisitos ==

Para escolher o método de atualização correto, talvez seja necessário conhecer vários recursos do seu sistema existente:
* Se ele tem uma partição separada para {{folder-pt-BR|/home}}. Você pode descobrir olhando em {{menu-pt-BR|CCM-> Discos locais -> Gerenciar partições de disco}}, veja a [https://doc.mageia.org/mcc/9/pt_br/content/mcc-localdisks.html#drakdisk documentação do drakdisk].
* Sua arquitetura, seja 32 ou 64 bits. Você pode usar o comando {{cmd-pt-BR|uname -m}} em um terminal. O resultado será x86_64 para 64 bits e i586 para 32 bits.
* O modo do firmware: BIOS ou UEFI. A resposta está na configuração do firmware. Pode ser mais simples ver se há um subdiretório {{folder-pt-BR|/EFI}} (para UEFI) em {{folder-pt-BR|/boot}} ou olhar em {{menu-pt-BR|CCM-> Boot -> Configurar sistema de boot}}. Veja a [https://doc.mageia.org/mcc/9/pt_br/content/mcc-boot.html#drakboot documentação do drakboot].
* O modo de particionamento de discos: MS-DOS (também chamado MBR) ou GPT. Como um usuário ''root'' (administrador), você pode usar o comando {{cmd-pt-BR|parted -l}} no terminal para ver a '''tabela de partição''' para seu disco de boot.
* O(s) ambiente(s) de desktop instalado(s).
* A lista de nomes de usuários com seus UIDs e GIDs. Veja [[#Como preservar o ID do usuário em uma instalação limpa|abaixo]]
* O bootloader em uso. Dê uma olhada em {{menu-pt-BR|CCM-> Boot -> Configurar sistema de boot}}. Veja [https://doc.mageia.org/mcc/9/pt_br/content/mcc-boot.html#drakboot o drakboot novamente].

Você também precisa saber qual dos recursos acima você deseja alterar no novo sistema - se houver.<br>

Por fim, qualquer que seja a sua decisão, sempre:
* leia a errata e as notas de lançamento. Cada lançamento tem suas próprias páginas de errata e uma seção dedicada a atualizações.
* faça backup de seus dados
* atualize a versão atual do seu {{prog-pt-BR|Mageia}}

== Vocabulary ==

For the purposes of this guide, the different upgrade scenarios (as shown in the following table) are named according to which partitions you choose to retain or format during the upgrade:

{|{{UsualTable}}
! scope="col"| Situation
| No formatting of partitions
| only {{folder|/}} is formatted
|{{folder|/}} and {{folder|/home}} are formatted
|-
! scope="col"|Name
|Simple upgrade
|Clean install
|New install
|}

If you have more than one bootable OS available on your system, we call that '''"dual-boot"''' if there are two OSes and '''"multi-boot"''' for more than two (though often simplified to '''"dual-boot"''' whatever their number is). e.g.: A clean installation in dual-boot.
{{note|You can't do a clean install if you don't have a separate {{folder|/home}} partition.}}

== Upgrade choice ==

=== Media possibilities ===

You need to choose the relevant upgrade media according to your upgrade plan.

{|{{UsualTable}}
! Media !! Simple upgrade !! Clean installation !! New installation
|-
|Live
|{{no}}
|{{yes}}
|{{yes}}
|-
|Classical
|{{yes}}
|{{yes}}
|{{yes}}
|-
|CLI (changing the repositories)
|{{yes}}
|{{no}}
|{{no}}
|}
<br />
{{note|[[Mageia_Netinstall_Iso_(Boot.iso)|{{file|Netinstall.iso}}]] is not really a media in itself, but a way to boot – and then load a media that is present locally or via a network. Consider it in terms of Classical media.}}

=== Advantages, drawbacks and special considerations ===

; Simple upgrade
: '''Advantages:''' Quick (no post-configuration), easy (no questions from the installer).
: '''Drawbacks:''' Any currently existing problems, instabilities, useless data, etc. might possibly be retained. Some upgrades can be risky if major changes are involved (e.g. KDE4 > Plasma5)
: '''Special considerations:'''
::* In cases of important graphic evolutions (e.g. KDE4 -> Plasma5) it is safer to do the upgrade in text mode. See the [[#How to do a simple upgrade in text mode|HowTo]] below.
::* It is impossible to change any of the characteristics listed [[#Requirements|above]].
::* Third-party applications are not updated. It may be safer to uninstall them along with any third party repositories prior to the upgrade.
::* The bootloader configuration is updated and in cases of dual-boot, manual configuration may be required.
::* When the installer asks you to choose between [https://doc.mageia.org/installer/7/en/content/selectInstallClass.html "Upgrade" or "Installation"], you will choose "Upgrade".
{{note|If you want to change the architecture from 32-bit to 64-bit, an upgrade is not possible as the root partition {{folder|/}} must be formatted.}}

; Clean installation
: '''Advantages:''' Clean the system (see Simple upgrade drawbacks), the minor configuration required (icons, widgets, wallpapers, bookmarks, data ... are preserved), low risk of failure.
: '''Drawbacks:''' Needs some skills (to choose the partitions and the desktop, to create the users, ...). Some configuration to redo (e.g. networks, some devices not fully supported), and all manual configurations done in {{folder|/etc}} are erased.
: '''Special considerations:'''
::* Take care that the installation preserves the same user UID's and GID's. See the [[#How to preserve user ID's in a clean install|HowTo]] below.
::* Needs a separate {{folder|/home}} partition.
::* Third-party applications are not updated. It may be safer to uninstall them along with any third party repositories prior to the upgrade.
::* Allows moving from 32-bit to 64-bit architecture and vice-versa.
::* Bootloader configuration is updated and in cases of dual boot, manual configuration may be required.
::* When the installer asks you to choose between [https://doc.mageia.org/installer/7/en/content/selectInstallClass.html "Upgrade" or "Installation"], you will choose "Installation". See the [https://doc.mageia.org/installer/7/en/content/index.html Installation manual].

; New installation
: '''Advantages:''' Everything is clean, including {{folder|/home}}.
: '''Drawbacks:''' Longer process and more skills required. It is like an initial installation - the whole configuration must be re-done.
: '''Special considerations:'''
::* It is an opportunity to change the disk partitioning.
::* Bootloader configuration is updated and in cases of dual-boot, manual configuration may be required.
::* If no dual-boot, it is also an opportunity to move from BIOS to UEFI mode.
::* When the installer asks you to choose between [https://doc.mageia.org/installer/7/en/content/selectInstallClass.html "Upgrade" or "Installation"], you will choose "Installation". See the [https://doc.mageia.org/installer/7/en/content/index.html Installation manual].
{{note|Although it is technically possible (using {{prog|Gparted}} for example) to manually convert an MS-DOS (MBR) disk to GPT without losing the data, it is easier to let the installer do this for you automatically.}}

; Whatever in dual-boot
: '''Advantages:''' Add the possibility to use two or more OSes on the same computer and, if wanted, to share the data.
: '''Drawbacks:''' The bootloader is rewritten and skills are needed to re-configure it if necessary.
: '''Special considerations:'''
::* If you don't want the {{prog|Mageia}} bootloader to be installed by default, take the necessary steps during the installation in order to keep your preferred bootloader. See the [https://doc.mageia.org/installer/7/en/content/index.html Installation manual].

== Preparations ==

* Carefully '''read''' the current '''Release Notes''' and '''Errata''', linked from [[Main_Page|Main Page]], to see if there is something you need to prepare for.
* '''Back up''' any important data.
* '''''Advanced users''' may have done changes that need to be reverted for problem free upgrade:''
** If '''third party repositories''' have been added, be sure to make a backup/copy of {{file|/etc/urpmi/urpmi.cfg}}. The info in that backup can be used if you later need to re-add them. DO NOT just restore the third party repo lines in urpmi.cfg. The file contents and the matching files in /var/lib/urpmi will be created when the repo is re-added.
** If any package names have been added to {{file|/etc/urpmi/'''skip.list'''}}, remove them.
** '''Disable''' or remove all '''debug and third party repositories''' shown by {{prog|drakrpm-edit-media}} ({{menu|MCC -> Software Management -> Configure media sources for install and update}}).
** A '''64 bit system''' must have any '''32 bit development libraries uninstalled'''. You can identify these by the word "devel" in the name. To know if your system houses such libraries you can use the command: <p> {{cmd|<nowiki>rpm -qa --queryformat "%{NVRA}\n" |grep i586 |grep devel</nowiki>}}
** '''Remove packages''' now not in configured repositories, shown by {{cmd|urpmq --not-available}}. They may be re-installed after the upgrade if needed.
* Perform a normal full '''system update''' ''(most importantly rpm and urpmi)''.
* It is good to '''free some space''', particularly uninstall old kernels, fat games...
* Make sure you have a '''task-* package for your favourite desktop''' installed. This ensures no needed packages for the desktop will be missing after the upgrade. Example: {{prog|task-plasma5}}. If you don't need full Plasma set it is {{prog|task-plasma5-minimal}}. Other desktops follow the same scheme, like {{prog|task-gnome, task-xfce}}, etc, some have the "-minimal" variant too.

<span style="color:red">'''Not supported:'''</span>
* Upgrading directly from earlier than previous release.
* Using any of the Live images - due to the Live system being copied "as is" to the target system.
* Upgrading a Mageia installation which was '''NOT''' in UEFI, towards a UEFI-mode.
- In these cases, you have to do a fresh installation. (Possibly keeping the {{folder|/home}} directory.)

== Help ==

Also see the [[Mageia_8_Release_Notes#Upgrading_from_Mageia_7|procedures described in current Release Notes]] which currently is more detailed. There you also find descriptions for [[Using_DNF|DNF.]]

=== How to do a simple upgrade in text mode ===

After having started and updated your system:

Open a console and enter the root mode
{{output|/usr/bin/sudo -i}}[sudo] password for user:{{stop}}

Stop the graphic interface
{{command|systemctl isolate multi-user|prompt=#}}

Delete the current repositories
{{command|urpmi.removemedia -a|prompt=#}}

Add the new repositories
{{command|urpmi.addmedia --distrib --mirrorlist <nowiki> http://mirrors.mageia.org/api/mageia.<n+1>.$ARCH.list</nowiki>|prompt=#}}

Test the upgrade, all the packages are downloaded and the upgrade simulated
{{command|urpmi --replacefiles --auto-update --auto --download-all --test|prompt=#}}
Note, if there isn't enough room in the file system containing /var/cache/urpmi/rpms to hold all of the rpm packages and there is enough space in another file system, then replace the directory /var/cache/urpmi/rpms with a symlink to a directory on that other file system. Once the upgrade has completed, replace the symlink with a normal directory, if desired. It there isn't enough space on any of the file systems, you can with some risk of it failing, skip this test and proceed with starting the upgrade.

For example, assuming /home is on a file system with enough room
{{command|mkdir /home/rpms|prompt=#}}
{{command|rmdir /var/cache/urpmi/rpms|prompt=#}}
{{command|ln -s /home/rpms /var/cache/urpmi/|prompt=#}}
<br>
After the upgrade has finished, if desired
{{command|rm -f /var/cache/urpmi/rpms|prompt=#}}
{{command|mkdir /var/cache/urpmi/rpms|prompt=#}}

If the test is OK, start the upgrade
{{command| urpmi --replacefiles --auto-update --auto --download-all|prompt=#}}

When it is complete reboot the system
{{command|shutdown -r now|prompt=#}}
<br>
{{dragons|To be extra careful, you can at the very beginning enter the command {{cmd|script upgrade_log.txt}} to fetch the error messages during the upgrade. At the end, enter the command {{cmd|exit}} to stop the record. You will find the backtraces in the file {{file|/root/upgrade_log.txt}} }}

=== How to preserve user IDs in a clean install ===

When doing a clean installation, you have to re-create the users and their already existing respective IDs. By default, {{prog|Mageia}} 5 and above will attribute user UIDs and GIDs beginning at 1000 (previous to Mageia 5, they began at 500). If these IDs are not correct, you have to change them. To do that, first fetch the IDs via the MCC of your current system: {{menu|MCC -> System -> Administration tools -> Manage users on system}}. Write down all the user IDs and don't forget to check the group IDs for those users, too, because it does occasionally happen that they're not the same as the user IDs. See the [https://doc.mageia.org/mcc/9/en/content/mcc-system.html#userdrake MCC userdrake documentation]. When doing the upgrade, and the installer arrives at the "User management" step, click on "Advanced":<br><br>
[[image:wikiUpgrade1en.png|800px]]

Then, you can add the correct IDs here: <br><br>
[[image:wikiUpgrade2en.png|800px]]

You have a further opportunity to modify the IDs in the "Summary" stage at the end of the installation.<br>In the "System" section, click on "Configure" next to "User management": <br><br>
[[image:wikiUpgrade3en.png|800px]] Xgrind

correção do link mídias de instalação

← Older revision Revision as of 22:55, 28 August 2025 Line 80: Line 80:  |- |-  |} |} −*[[Mídias de instalação]]+*[[Mídias de instalação-pt-BR|Mídias de instalação]]  *[[How_to_choose_the_right_Mageia_upgrade_method|Como escolher o método correto de atualização do Mageia]] *[[How_to_choose_the_right_Mageia_upgrade_method|Como escolher o método correto de atualização do Mageia]]  *[[Mageia Netinstall Iso (Boot.iso)]] *[[Mageia Netinstall Iso (Boot.iso)]] Xgrind

‎Backport kernels: kvm blacklist tip

← Older revision Revision as of 17:04, 28 August 2025 Line 83: Line 83:  '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source    −'''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br>+'''If running VirtualBox''': Currently, before launching guests, you need to <br>  $ sudo rmmod kvm_intel  ''(When using Intel CPU; If you have AMD CPU then instead execute rmmod kvm_amd.)'' <br> $ sudo rmmod kvm_intel  ''(When using Intel CPU; If you have AMD CPU then instead execute rmmod kvm_amd.)'' <br> −$ sudo rmmod kvm+$ sudo rmmod kvm <br>  +- or blacklist them, see {Bug|34408#c7}}.     == Kernel series in Cauldron == == Kernel series in Cauldron == Morgano

‎Boomaga virtual printer

← Older revision Revision as of 16:58, 28 August 2025 (2 intermediate revisions by the same user not shown)Line 496: Line 496:     This only affects some NAS devices. Check the settings of your NAS which protocol versions are supported and setup the highest possible protocol version as example NFSv4. See {{bug|31725}} This only affects some NAS devices. Check the settings of your NAS which protocol versions are supported and setup the highest possible protocol version as example NFSv4. See {{bug|31725}} −  −==== DAVFS crashes subsequent to files being refused ====  −  −{{bug|31702}} With DAVFS, files refused by the remote host are saved in 'lost+found'. Subsequent access to that directory crashes DAVFS. The solution is to to remove them from the cache folder when davfs is UNmounted. Upstream.      ==== Network sharing ==== ==== Network sharing ==== Line 507: Line 503:  ==== Samba ==== ==== Samba ====    −{{Bug|30090}} - '''Samba folder sharing''' not working. '''Manual fix''' see bug.+{{Bug|30090}} - '''Samba folder sharing''' in GNOME not working. '''Manual fix''' see bug.     ==== Firewall ==== ==== Firewall ==== Line 536: Line 532:     {{bug|31980}} - Sometimes not working at all. Really need upstream update, but is stalled since years.  When it works, which it most often do, be happy :)  '''Workaround:''' System reboot is known to have effect.  Seems to have got worse on some systems in spring 2025, but still works on other. {{bug|31980}} - Sometimes not working at all. Really need upstream update, but is stalled since years.  When it works, which it most often do, be happy :)  '''Workaround:''' System reboot is known to have effect.  Seems to have got worse on some systems in spring 2025, but still works on other.  +  +'' '''Suggestion:''' Another way to preview an alter pages before printing: print to pdf files, then open them in {{prog|PDF Arranger}}, see, alter, then print or save.''     ==== Printer duplicate - not a bug ==== ==== Printer duplicate - not a bug ==== Morgano

Standardising notation/spelling

← Older revision Revision as of 16:43, 28 August 2025 Line 56: Line 56:  This kernel is proposed with the same version as kernel-desktop. This kernel is proposed with the same version as kernel-desktop.    −This package will not be available in Mageia 10 and later. With the transition from i586 to i686+SSE2, this architecture now supports PAE (Physical Address Extension), enabling support for up to 64 GB of memory as in standard -desktop flavor.+This package will not be available in Mageia 10 and later. With the transition from i586 to i686+SSE2, this architecture now supports PAE (Physical Address Extension), enabling support for up to 64 GB of memory as in standard -desktop flavour.     == Other kernels == == Other kernels == Line 89: Line 89:  == Kernel series in Cauldron == == Kernel series in Cauldron ==    −In cauldron we now have -mainline, -stable-testing, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).+In Cauldron we now have -mainline, -stable-testing, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).    −The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.+The -stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.     The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels.    −Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3).+Note that it is not guaranteed that all series cover all architectures and flavours. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavour (e.g., desktop), or new flavours may emerge (e.g., desktop-tunedv3 for x86_64-v3).     As an example, on August 28 2025 we had the following kernels in Cauldron: As an example, on August 28 2025 we had the following kernels in Cauldron: Morgano

‎Kernel series in Cauldron: s/stablenew/stable-testing/ in the first line

← Older revision Revision as of 16:33, 28 August 2025 Line 89: Line 89:  == Kernel series in Cauldron == == Kernel series in Cauldron ==    −In cauldron we now have -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).+In cauldron we now have -mainline, -stable-testing, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).     The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often. The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often. Marja

‎Backport kernels: Bug 34563 solved.

← Older revision Revision as of 16:03, 28 August 2025 (4 intermediate revisions by the same user not shown)Line 79: Line 79:  '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''    −'''Boot menu do not update''' ({{Bug|34563}}), getting fixed in 6.12.43+. If you install a kernel and do not find it in boot menu, run {{cmd|update-grub2}} as root.+'''Regarding kernel-stable-userspace-headers''' contra ''kernel-userspace-headers'' for 6.6 kernels: The packages are used for building applications; use the one for the current kernel you build for. For the package managers to work correctly, you need to update mageia-repos and meta-task packages to 9.4 versions, at time of writing found in updates_testing.  ''(Note that they conflict each other but currently there is a bug that kernel-stable-userspace-headers can not be uninstalled because a conflict/dependency problem.)'' −   −'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.''       '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source     '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> −$ sudo rmmod kvm_intel<br>+$ sudo rmmod kvm_intel ''(When using Intel CPU; If you have AMD CPU then instead execute rmmod kvm_amd.)'' <br>  $ sudo rmmod kvm $ sudo rmmod kvm    Line 93: Line 91:  In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.). In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).    −The -stablenew series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.+The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.     The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. Line 99: Line 97:  Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3). Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3).    −As an example, on August 13 2025 we had the following kernels in Cauldron:+As an example, on August 28 2025 we had the following kernels in Cauldron: −* kernel-mainline -> 6.16.0 (x86_64, desktop only)+* kernel-mainline -> 6.17.0-rc3 (x86_64, desktop only) −* kernel-stablenew -> 6.15.7 (x86_64, desktop only)+* kernel-stable-testing -> 6.16.2 (x86_64, desktop only) −* kernel-stable -> 6.14.11 (x86_64, desktop only)+** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)'' −* kernel -> 6.12.41 (all arches, all flavours)+* kernel-stable -> 6.15.11 (x86_64, desktop only)  +* kernel -> 6.12.43 (all arches, all flavours)  * kernel-lts -> 6.6.100 (all arches, all flavours) * kernel-lts -> 6.6.100 (all arches, all flavours) Morgano

‎Backport kernels: Bug 34563 solved.

← Older revision Revision as of 16:03, 28 August 2025 (5 intermediate revisions by the same user not shown)Line 79: Line 79:  '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''    −'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.'' +'''Regarding kernel-stable-userspace-headers''' contra ''kernel-userspace-headers'' for 6.6 kernels: The packages are used for building applications; use the one for the current kernel you build for. For the package managers to work correctly, you need to update mageia-repos and meta-task packages to 9.4 versions, at time of writing found in updates_testing.  ''(Note that they conflict each other but currently there is a bug that kernel-stable-userspace-headers can not be uninstalled because a conflict/dependency problem.)''     '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.  Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source     '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> −$ sudo rmmod kvm_intel<br>+$ sudo rmmod kvm_intel ''(When using Intel CPU; If you have AMD CPU then instead execute rmmod kvm_amd.)'' <br>  $ sudo rmmod kvm $ sudo rmmod kvm    Line 91: Line 91:  In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.). In cauldron we now have  -mainline, -stablenew, -stable and -lts kernel series. These series are (at least for now) intended for Cauldron only and provide opportunities to test newer hardware, as well as aligning the packages required for building stable kernels (e.g.: newer Rust, newer LLVM, missing libraries, etc.).    −The -stablenew series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.+The stable-testing (formerly -stablenew) series is (in theory) the newest stable after -mainline, resembling [https://www.kernel.org upstream] though not matching one-to-one, as those might change more often.     The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. The -lts series also allows testing compatibility with the "previous" latest working LTS series, which could be useful in many cases, e.g. for proprietary drivers (e.g., NVIDIA) when they won't build anymore on newer kernels or for verifying different hardware behavior of older hardware with respect to newer kernels. Line 97: Line 97:  Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3). Note that it is not guaranteed that all series cover all architectures and flavors. For some series, the build may be limited to a single architecture (e.g., x86_64) and single flavor (e.g., desktop), or new flavors may emerge (e.g., desktop-tunedv3 for x86_64-v3).    −As an example, on August 13 2025 we had the following kernels in Cauldron:+As an example, on August 28 2025 we had the following kernels in Cauldron: −* kernel-mainline -> 6.16.0 (x86_64, desktop only)+* kernel-mainline -> 6.17.0-rc3 (x86_64, desktop only) −* kernel-stablenew -> 6.15.7 (x86_64, desktop only)+* kernel-stable-testing -> 6.16.2 (x86_64, desktop only) −* kernel-stable -> 6.14.11 (x86_64, desktop only)+** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)'' −* kernel -> 6.12.41 (all arches, all flavours)+* kernel-stable -> 6.15.11 (x86_64, desktop only)  +* kernel -> 6.12.43 (all arches, all flavours)  * kernel-lts -> 6.6.100 (all arches, all flavours) * kernel-lts -> 6.6.100 (all arches, all flavours) Morgano

‎Backport kernels: Bug 34563 boot menu

← Older revision Revision as of 17:14, 27 August 2025 Line 78: Line 78:     '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''  +  +'''Boot menu do not update''' ({{Bug|34563}}), getting fixed in 6.12.43+. If you install a kernel and do not find it in boot menu, run {{cmd|update-grub2}} as root.     '''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.''    '''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.''    Morgano

‎Package Ordering: order.rb limitations

← Older revision Revision as of 05:38, 26 August 2025 Line 17: Line 17:  ruby order.rb <UpgradedPackageName> ruby order.rb <UpgradedPackageName>  </pre> </pre> −''Todo: where is this script located and what are its dependencies?''+This script is only available on duvel to sysadmins, as it looks at autobuild logs directly to get the list of packages that need to be installed while building each package (including basesystem). It is also not that smart as it works at src.rpm level and may find too many loops, for example if something needs a noarch subpackage and not the binary one needing a rebuild, there is no need to wait until it was rebuilt.     == See Also == == See Also == Danf

Adding myself in the packaging candidate section.

← Older revision Revision as of 14:06, 23 August 2025 Line 127: Line 127:  |- |-  {{Pkg:appr-cand| kooltrade | Zane Edminstin | kowhaitek@protonmail.com | UTC+12 | en | 2025-06-19 | Teaching myself C programming, limited knowledge of Linux systems, interested in package maintenance plenty of free time to learn I want to master this}} {{Pkg:appr-cand| kooltrade | Zane Edminstin | kowhaitek@protonmail.com | UTC+12 | en | 2025-06-19 | Teaching myself C programming, limited knowledge of Linux systems, interested in package maintenance plenty of free time to learn I want to master this}}  +|-  +{{Pkg:appr-cand| moufinure | Pierre Gnaedig | pierre.gnaedig@mailoo.org | UTC+2 | en,fr | 2025-08-23 | Professional software developer, linux and FOSS enthusiast with quite some free time, interested in Mageia as its ancestor was my first linux in 1999.  +}}  |} |}    Moufinure

‎Zurückportierte Kernel (Backport)

← Older revision Revision as of 08:22, 20 August 2025 (One intermediate revision by the same user not shown)Line 61: Line 61:     Die Veröffentlichung folgt den aktuellen "Veröffentlichungskandidaten" von kernel.org und kann Unterstützung für aktuelle Eigenschaften enthalten, welche nicht in den Standard-Kernel vorhanden sind. Die Veröffentlichung folgt den aktuellen "Veröffentlichungskandidaten" von kernel.org und kann Unterstützung für aktuelle Eigenschaften enthalten, welche nicht in den Standard-Kernel vorhanden sind.  +  +== Zurückportierte Kernel (Backport) ==  +Es ist möglich, dass ein Kernel für zuvor veröffentlichte Mageia Ausgaben zurückportiert werden, zum Beispiel von Cauldron zur offiziellen, aktuell verfügbaren, Mageia Version.  +  +'''Für Mageia 9, wird Kernel 6.12''' in den Backport Repositorien als '''x86_64 Desktop Variante''' angeboten ''- ansonsten für keine weitere Version.''<br>  +  +''('''In Bearbeitung''' {{Bug|34545}} August 2025; kernel befindet sich aktuell im backport_testing Repositorium)''<br>  +'''<br>  +Es werden nur zwei Pakete installiert''' (aus Backport): <br>  +kernel-stable-desktop-6.12... <br>  +kernel-stable-desktop-devel-6.12... ''(Falls Sie dieses Paket benötigen, zum Beispiel, wenn für Ihre anderen Kernel entsprechende -devel - Pakete installiert sind.)''  +  +'''Lassen Sie die aktuellste nicht-backport Version von''' lib64bpf1, cpupower, kernel-userspace-headers installiert, und halten Sie diese aktuell.  ''- wir bieten keine Rückportierung von lib64bpf1 und cpupower an, um nicht die Kompatibilität mit Kernel, welche nicht aus dem Backport Repository sind, zu brechen.''  +  +'''Versuchen Sie nicht''' 'kernel-stable-userspace-headers' zu installieren. '''Noch.''' ''- Es sollte möglich sein das eine oder kernel-userspace-headers installiert zu haben, jedoch nicht beides gleichzeitig, jedoch ist dies aktuell nicht einfach möglich (siehe {{Bug|34545}}). Diese Pakete werden zum paketieren von Anwendungen benötigt.''  '  +  +'''Remove-Old-Kernels''', {{prog|rok}}, kann werder den Kernel 6.12 erkennen, noch mit diesem umgehen, weshalb Sie nicht mehr benötigte Kernel händisch desintallieren müssen, um Speicherplatz zu sparen - genauso, wie Sie es mit den Kerneln getan haben, bevor rok in Mageia 9 eingeführt wurde. Oder Sie '''machen es nutzbar''', indem Sie in der Konfigurationsdatei {{file|/etc/remove-old-kernels.cfg}} etwas einfügen: Fügen Sie in der Liste unter der Zeile "LISTK=\" folgendes hinzu <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source  +  +'''Falls VirtualBox ausgeführt wird''': Aktuell {{Bug|34408}} müssen Sie vor dem Starten des Gasts folgendes ausführen <br>  +$ sudo rmmod kvm_intel<br>  +$ sudo rmmod kvm     == Kernelserien in Cauldron == == Kernelserien in Cauldron == Line 71: Line 92:  Beachten Sie, dass es nicht garantiert ist, dass alle Serien für alle Architekturen und Kernel-Arten verfügbar sind. Einige Serien sind möglicherweise auf einzelne Architekturen (zum Beispiel x86_64) und einzelne Arten (zum Beispiel desktop) beschränkt oder neuere Arten werden veröffentlicht (zum Beispiel desktop-tunedv3 für x86_64-v3). Beachten Sie, dass es nicht garantiert ist, dass alle Serien für alle Architekturen und Kernel-Arten verfügbar sind. Einige Serien sind möglicherweise auf einzelne Architekturen (zum Beispiel x86_64) und einzelne Arten (zum Beispiel desktop) beschränkt oder neuere Arten werden veröffentlicht (zum Beispiel desktop-tunedv3 für x86_64-v3).    −Als Beispiel, mit Stand vom 29. Mai 2025, boten wir folgende Kernel in Cauldron an:+Als Beispiel, mit Stand vom 13. August 2025, boten wir folgende Kernel in Cauldron an: −* kernel-mainline -> 6.15.0 (x86_64, nur Desktop)+* kernel-mainline -> 6.16.0 (x86_64, nur Desktop) −* kernel-stablenew -> 6.14.8 (x86_64, nur Desktop)+* kernel-stablenew -> 6.15.7 (x86_64, nur Desktop) −* kernel-stable -> 6.12.30 (x86_64, nur Desktop)+* kernel-stable -> 6.14.11 (x86_64, nur Desktop) −* kernel -> 6.12.30 (all arches, alle Arten)+* kernel -> 6.12.41 (all arches, alle Arten) −* kernel-lts -> 6.6.92 (all arches, alle Arten)+* kernel-lts -> 6.6.100 (all arches, alle Arten) Psyca

← Older revision Revision as of 07:19, 20 August 2025 Line 321: Line 321:     * Unter GNOME muss die [[#GNOME|Applet Sichtbarkeit]] aktiviert werden. * Unter GNOME muss die [[#GNOME|Applet Sichtbarkeit]] aktiviert werden.  +  +=== Backport Kernel ===  +Kernel 6.12 ist seit August 2025 verfügbar. Beachten Sie, dass dieser etwas [[Kernel-Arten-de#Zurückportierte Kernel (Backport)|Aufmerksamkeit benötigt]].     == Sicherheit == == Sicherheit == Psyca

‎Upgrade von der letzten stabilen Version zu Cauldron mittels DNF: Hinweis zum Entfernen der Stable Repos

← Older revision Revision as of 09:42, 19 August 2025 Line 89: Line 89:  Installation des system-upgrade Plugins: Installation des system-upgrade Plugins:  {{command-de|dnf install 'dnf-command(system-upgrade)'|prompt=#}} {{command-de|dnf install 'dnf-command(system-upgrade)'|prompt=#}}  +  +{{note-de|Vergessen Sie nicht, die verbleibenden Repositorys aus der neuesten stabilen Version (z. B. Mageia 9) zu entfernen/deaktivieren, da Sie sonst später Repository-Fehler erhalten.}}     Starten des Plugins: Starten des Plugins: Sturmvogel

‎Upgrade from the latest stable release to Cauldron using DNF: minor rephrasing

← Older revision Revision as of 16:45, 18 August 2025 (One intermediate revision by the same user not shown)Line 90: Line 90:  Install system-upgrade plugin: Install system-upgrade plugin:  {{command|dnf install 'dnf-command(system-upgrade)'|prompt=#}} {{command|dnf install 'dnf-command(system-upgrade)'|prompt=#}}  +  +{{note|Do not forget to remove/disable remaining repositories from the latest stable release (e.g. Mageia 9) or you will get repository errors later on.}}     Start download of Cauldron packages and check of possible conflicts: Start download of Cauldron packages and check of possible conflicts: Sturmvogel

added more prominent warning

← Older revision Revision as of 15:33, 18 August 2025 Line 7: Line 7:     {{draft}} {{draft}}  +{{warning|This page is a draft for the upcoming release Mageia 10. Do not follow any instructions yet until Mageia 10 got finally released.}}     {{introduction|Presentation of the evolution, new features, known issues, and the recent changes of the Mageia distribution.}} {{introduction|Presentation of the evolution, new features, known issues, and the recent changes of the Mageia distribution.}} Sturmvogel

Undo revision 64059 by Sturmvogel (talk) wrong page

← Older revision Revision as of 15:32, 18 August 2025 (One intermediate revision by the same user not shown)(No difference) Sturmvogel

‎Backport kernels: comment

← Older revision Revision as of 16:06, 17 August 2025 (3 intermediate revisions by the same user not shown)Line 75: Line 75:  Only two packages to install''' (from Backport): <br> Only two packages to install''' (from Backport): <br>  kernel-stable-desktop-6.12... <br> kernel-stable-desktop-6.12... <br> −kernel-stable-desktop-devel-6.12...+kernel-stable-desktop-devel-6.12... ''(If you need it, i.e if your other kernels also have corresponding -devel- packages installed.)''     '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''    −'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have in parallel with non backport kernel-userspace-headers, but currently is not (See {{Bug|34545}}).+'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.'' −''     −'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.+'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9. Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source     '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> Morgano

‎Backport kernels: comment

← Older revision Revision as of 08:42, 17 August 2025 (2 intermediate revisions by the same user not shown)Line 79: Line 79:  '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.'' '''Keep having latest non-backport''' lib64bpf1, cpupower, kernel-userspace-headers installed, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels.''    −'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have in parallel with non backport kernel-userspace-headers, but currently is not (See {{Bug|34545}}).+'''Do not try to install''' 'kernel-stable-userspace-headers'. '''Yet.''' ''- It should be possible to have either that or kernel-userspace-headers installed, one at a time, but currently is not easy (See {{Bug|34545}}). The packages are used for building applications.'' −''     −'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9.+'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle 6.12 kernels, so you need to manually uninstall excess kernels when needed to save space - like you did for any kernels before rok was introduced with Mageia 9. Or, '''make it work''' by adding to {{file|/etc/remove-old-kernels.cfg}}: In the list under the line "LISTK=\", add <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source     '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> '''If running VirtualBox''': Currently {{Bug|34408}}, before launching guests, you need to <br> Morgano