Lector de Feeds

‎Backport kernels: userspace-headers are now handled correctly

← Older revision Revision as of 09:50, 29 August 2025 Line 70: Line 70:  It happens that a kernel get backported to previous Mageia release, i.e from Cauldron to latest official Mageia. It happens that a kernel get backported to previous Mageia release, i.e from Cauldron to latest official Mageia.    −'''In Mageia 9, Kernel 6.12''' is provided in Backport repository for '''x86_64 in desktop flavour''' ''- no other version.''<br>+'''In Mageia 9, Kernel 6.12.44+''' is provided in Backport repository for '''x86_64 in desktop flavour''' ''- no other version.''<br>  ''('''In progress''' {{Bug|34545}} August 2025; kernel is currently in backport_testing repo)''<br> ''('''In progress''' {{Bug|34545}} August 2025; kernel is currently in backport_testing repo)''<br>  '''<br> '''<br>  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... ''(If you need it, i.e if your other kernels also have corresponding -devel- packages installed.)''+kernel-stable-desktop-devel-6.12... ''(If you need it, i.e if your other kernels also have corresponding -devel- packages installed.)'' <br>  +- Also note you need the suggested relevant -latest packages too for easy future updating. (In contrast to mga9 6.6 kernels that do not ''need'' them, due to a different naming scheme.)     '''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.''    −'''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.)''+'''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. They conflict each other and are handled correctly by urpmi & drakrpm - when you have '''updated mageia-repos and meta-task packages''' to 9.4 versions (at time of writing found in updates_testing) - and using kernel versions 6.6.103+ and 6.12.44+.     '''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 Morgano

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

Escrito por Aguador.

El final se acerca, el final se acerca… el final del soporte para Windows 10… y como parte de la comunidad Linux podemos ayudar a los afectados.

El 14 de octubre, termina el soporte de Windows 10, dejando a los usuarios de equipos antiguos o poco potentes tres opciones:

• Sufrir un bajo desempeño (SI es que el equipo cumple los requisitos mínimos para Windows 11)
• Pagar por soporte y continuar usando Windows 10
• .Comprar un equipo nuevo y más potente.

Como usuarios de Linux, sabemos que no son las únicas opciones, Linux ofrece un rango de opciones que cubre virtualmente cualquier gusto personal y equipo. KDE, fuente de uno del los escritorios principales1 de Mageia, tiene un atractivo sitio multimedia2 para aquellos que estan por ser abandonados por Windows.

Expone los argumentos para pasarse a Linux, con Plasma y el universo de software KDE como alternativa. El sitio presenta las modernas características de KDE-Plasma, las ventajas del Software Libre y de Fuentes Abiertas, y compatibilidad con archivos creados por software propietario. Es un gran recurso que los miembros de la comunidad Mageia pueden presentar a sus amigos y colegas que enfrentan «el fin». Y desde luego como mageitas, podemos proporcionar el enlace junto con ayuda para configurar Mageia.

Si no usa Plasma o no cree que es lo adecuado para sus amigos o los equipos de sus amigos; El sitio también ofrece enlaces a otros escritorios populares y, al final, un enlace al sitio Endof10, que también es hospedado por KDE. No solo ofrece argumentos para cambiar a Linux, también proporciona una guía para la selección de sistema y, lo más importante, sitios al rededor del mundo donde se puede encontrar ayuda con el cambio.

Como usuarios de Mageia sabemos que ofrece toda la belleza y potencia de Plasma y el conjunto de programas KDE. Hágale a sus amigos, familiares, colegas y vecinos un favor, no solo compartiéndoles estos sitios (y desde luego el de Mageia), muéstreles Plasma u otros escritorios en acción en su equipo. Oh, y si quiere volcar una imagen Live en una memoria USB, puede incluso enseñarles Mageia en acción EN SUS equipos.

Para nosotros es obvio que ¡Mageia 9 > Win10, no es un error!

1. ¡Sorpresa!: ¡Tratamos a todos los escritorios como principales! ︎
2. Note que los videos de KDE requieren habilitar DRM ︎

Traducido por katnatek de la publicación original en Inglés.

By Aguador.

The end is coming, the end is coming…the end of Windows 10 support, that is…and as part of the Linux community we can help those affected.

As of 14 October support for Windows 10 will end, leaving its users of older, less powerful machines three choices:

• Suffer slower performance (IF their machine does at least meet the minimum requirements for Win 11)
• Pay for support to continue with Win 10
• Buy new, more powerful equipment

As Linux users we know that these are not the only choices, Linux offers a range of options to suit virtually any personal taste and computer. KDE, source of one of Mageia’s flagship1 desktops, has an attractive multimedia website2 for the about-to-be orphaned Windows users.

It lays out the case for switching to Linux, with Plasma and the KDE universe of software as the alternative. The site presents the modern features of KDE-Plasma, the advantages of Free and Open Source Software, and compatibility with files produced by proprietary software. It is a great resource which Mageia community members can offer friends and colleagues facing “the end”. And, of course, as mageians, we can provide that link along with an offer to help them in getting set up with Mageia.

You do not use Plasma or do not think it is right for your friends or friends’ machines? The site also offers links to other popular desktops and, at the end, a link to the more general Endof10 website, which is also hosted by KDE. It not only offers the arguments for switching to Linux, but provides guidance in choosing a system and, most importantly, places around the world where people can find hands-on help in making the switch.

As Mageia users we know it offers all the beauty and power of Plasma and the KDE suite of programs. So do your friends, family, colleagues and neighbours a favour by not only sharing these sites (and, of course, Mageia’s), but also showing Plasma and/or other desktops in action on your machine. Oh, and if you want to write a Live ISO to a USB stick, you can even show them the Mageia we use every day in action on THEIR machines.

To us mageians it is obvious, that Mageia 9 > Win10 is not a typo!

1. Surprise: we treat all of our desktops as flagships! ︎
2. Note that the KDE videos require having DRM enabled ︎

Esta es una nota inusual y diferente, como advertimos en actualizaciones previas (MGASA-2025-0195, MGASA-2025-0197 y MGASA-2025-0201), por mucho tiempo, no ha sido posible publicar las actualizaciones para Firefox y Thunderbird en la arquitectura armv7hl.

El problema tenía dos causas, La primera, notada durante el proceso de control de calidad de las notificaciones de seguridad enlazadas, fue producida por un fallo en las herramientas utilizadas para compilar Firefox en esa arquitectura.

La segunda fue más difícil de erradicar, y estábamos listos para informarles que no podíamos continuar actualizando estas aplicaciones en mageia 9 para la arquitectura armv7hl.

Pero, Pascal Terjan (uno de nuestros empaquetadores), encontró en la comunidad Debian, un parche justo para nuestro problema (un componente rust está utilizando el tipo fat para la optimización durante enlace -link time optimization-).

Firefox ahora está actualizado, en mageia 9 y cauldron, a la versión 128.12.0 ESR – un salto desde la versión 115.13.0 en armv7hl – y Thunderbird le seguirá una vez que la versión 128.12 este lista.

Traducido por katnatek de la publicación original en inglés.

Written by katnatek.

This is an unusual post… As we warned in the past updates MGASA-2025-01951, MGASA-2025-01972 and MGASA-2025-02013, the updates for Firefox and Thunderbird could not be delivered for armv7hl for a long time.

The issue had two causes. The first one, noticed during the QA process for the linked Security Advisories, was produced by a bug in the tools used to build Firefox for this architecture4.

The second one was harder to squash, and we were on the verge of informing you that we could not continue updating these software products in Mageia 9 for the armv7hl architecture.

But then, Pascal Terjan (one of our packagers), found a patch in the Debian community for exactly the same issue (a Rust component was using the fat link time optimization)

Firefox is now updated in all architectures, in both Mageia 9 and Cauldron, to the 128.12.0 ESR version – an upgrade from 115.13.0 on armv7hl – and Thunderbird will follow once version 128.12 is ready.

1. https://advisories.mageia.org/MGASA-2025-0195.html ︎
2. https://advisories.mageia.org/MGASA-2025-0197.html ︎
3. https://advisories.mageia.org/MGASA-2025-0201.html ︎
4. https://bugs.mageia.org/show_bug.cgi?id=34422 ︎