Lector de Feeds

fix link to MADb

← Older revision Revision as of 14:35, 5 November 2024 Line 19: Line 19:       −You can find ''update requests'' of [https://madb.mageia.org/tools/updates packages waiting for ''validation''].+You can find ''update requests'' of [https://madb.mageia.org/updates packages waiting for ''validation''].  <br/><br/><br/> <br/><br/><br/>    Line 103: Line 103:  All the actions described here relate to the Bugzilla entry. All the actions described here relate to the Bugzilla entry.    −# '''Check if the update candidate is ready for validation''' Ideally it is only ready for validating when it has been successfully tested on both architectures on all releases it covers. As some bugs contain updates for more than one Mageia release, each must be completed for both i586 and x86_64 before it can be validated. However, when QA is hard pressed, and the update is not major (like kernels, or a widespread application), an OK for just one architecture is permitted. You can most easily see this [https://madb.mageia.org/tools/updates on madb] where it will show a green circle next to each Mageia Version when it is ready to go.+# '''Check if the update candidate is ready for validation''' Ideally it is only ready for validating when it has been successfully tested on both architectures on all releases it covers. As some bugs contain updates for more than one Mageia release, each must be completed for both i586 and x86_64 before it can be validated. However, when QA is hard pressed, and the update is not major (like kernels, or a widespread application), an OK for just one architecture is permitted. You can most easily see this [https://madb.mageia.org/updates on madb] where it will show a green circle next to each Mageia Version when it is ready to go.  # '''Add a validation Comment''' to let people know the update has been properly tested on both architectures and, if necessary, all releases. # '''Add a validation Comment''' to let people know the update has been properly tested on both architectures and, if necessary, all releases.  # '''If necessary, add a list of the Source RPM's''' (SRPM's). Nowadays, this is usually already given in the bug with the packages involved. Also, the bug header field RPM Package may show it. For further information on finding the SRPM for a package, see the [[How to find a source RPM]] page.<br/> # '''If necessary, add a list of the Source RPM's''' (SRPM's). Nowadays, this is usually already given in the bug with the packages involved. Also, the bug header field RPM Package may show it. For further information on finding the SRPM for a package, see the [[How to find a source RPM]] page.<br/> Line 112: Line 112:  {{note|You will normally see that somebody mentions that the advisory has been uploaded. You need not worry about this. Team leaders and people with relevant permissions are now uploading the advisories [https://svnweb.mageia.org/advisories/ as yaml text files to svn] where they are then used, when the update is pushed, to update the [https://advisories.mageia.org/ advisories website] and [https://ml.mageia.org/l/info/updates-announce updates-announce] mailing list. {{note|You will normally see that somebody mentions that the advisory has been uploaded. You need not worry about this. Team leaders and people with relevant permissions are now uploading the advisories [https://svnweb.mageia.org/advisories/ as yaml text files to svn] where they are then used, when the update is pushed, to update the [https://advisories.mageia.org/ advisories website] and [https://ml.mageia.org/l/info/updates-announce updates-announce] mailing list.    −They are uploaded before sysadmin push the update and, once completed, denoted by a star (*) in the first field on [https://madb.mageia.org/tools/updates madb] and the 'advisory' tag in the whiteboard field of the update request on bugzilla.  +They are uploaded before sysadmin push the update and, once completed, denoted by a star (*) in the first field on [https://madb.mageia.org/updates madb] and the 'advisory' tag in the whiteboard field of the update request on bugzilla.       Only [https://people.mageia.org/g/mga-qa-committers.html some QA members] can [[How to create an update advisory|upload the advisories]] so if you see that one is needed you can also leave a comment to say so, to ensure that it isn't forgotten.<br/><br/> Only [https://people.mageia.org/g/mga-qa-committers.html some QA members] can [[How to create an update advisory|upload the advisories]] so if you see that one is needed you can also leave a comment to say so, to ensure that it isn't forgotten.<br/><br/> Line 163: Line 163:  * [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/qa-discuss QA-Discuss] mailing list: qa-discuss@ml.mageia.org * [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/qa-discuss QA-Discuss] mailing list: qa-discuss@ml.mageia.org  * [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/qa-bugs QA-Bugs] mailing list: qa-bugs@ml.mageia.org * [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/qa-bugs QA-Bugs] mailing list: qa-bugs@ml.mageia.org −* You can also use [https://madb.mageia.org/tools/updates Mageia App Db] to see pending update candidates and perform various useful comparisons.+* You can also use [https://madb.mageia.org/updates Mageia App Db] to see pending update candidates and perform various useful comparisons.  * [[Sophie]] is a bot on IRC providing much useful information on Mageia packages.<br/>Try typing ''':help''' in #mageia-qa or ''':more ''packagename''' * [[Sophie]] is a bot on IRC providing much useful information on Mageia packages.<br/>Try typing ''':help''' in #mageia-qa or ''':more ''packagename'''    Papoteur

fix link to MADb

← Older revision Revision as of 14:33, 5 November 2024 Line 34: Line 34:       −Of course, each package being updated is different. It is our responsibility to work out how best to test them all. Luckily though [http://advisories.mageia.org/ we have tested many packages before] and bugzilla can be searched to see how something was tested the last time it was updated. This search is made easy by clicking on the 'Bugzilla' link on the right-hand side of the [http://mageia.madb.org/tools/updates madb list page]. We also began documenting some of these procedures [[:Category:Testing procedures|here on the wiki]], although we've not made much progress in doing so. You can search those pages by clicking the 'Wiki' link on that same madb list page. There are also some [[QA Tips and Tricks|tips]] to help you along the way.+Of course, each package being updated is different. It is our responsibility to work out how best to test them all. Luckily though [http://advisories.mageia.org/ we have tested many packages before] and bugzilla can be searched to see how something was tested the last time it was updated. This search is made easy by clicking on the 'Bugzilla' link on the right-hand side of the [http://mageia.madb.org/updates madb list page]. We also began documenting some of these procedures [[:Category:Testing procedures|here on the wiki]], although we've not made much progress in doing so. You can search those pages by clicking the 'Wiki' link on that same madb list page. There are also some [[QA Tips and Tricks|tips]] to help you along the way.       Papoteur

fix link madb

← Older revision Revision as of 14:32, 5 November 2024 Line 34: Line 34:       −Of course, each package being updated is different. It is our responsibility to work out how best to test them all. Luckily though [http://advisories.mageia.org/ we have tested many packages before] and bugzilla can be searched to see how something was tested the last time it was updated. This search is made easy by clicking on the 'Bugzilla' link on the right-hand side of the [https://madb.mageia.org/tools/updates madb list page]. We also began documenting some of these procedures [[:Category:Testing procedures|here on the wiki]], although we've not made much progress in doing so. You can search those pages by clicking the 'Wiki' link on that same madb list page. There are also some [[QA Tips and Tricks|tips]] to help you along the way.+Of course, each package being updated is different. It is our responsibility to work out how best to test them all. Luckily though [http://advisories.mageia.org/ we have tested many packages before] and bugzilla can be searched to see how something was tested the last time it was updated. This search is made easy by clicking on the 'Bugzilla' link on the right-hand side of the [https://madb.mageia.org/updates madb list page]. We also began documenting some of these procedures [[:Category:Testing procedures|here on the wiki]], although we've not made much progress in doing so. You can search those pages by clicking the 'Wiki' link on that same madb list page. There are also some [[QA Tips and Tricks|tips]] to help you along the way.       Papoteur

remove scaleway, add MLO

← Older revision Revision as of 14:30, 5 November 2024 Line 1: Line 1:  +[[Category:Sysadmin]]  Add here each webservice we use, and who has the login and password : Add here each webservice we use, and who has the login and password :    Line 16: Line 17:  *  [https://matrix.to/#/#mageia-space:matrix.org matrix.org]: ngompa, neoclust, akien *  [https://matrix.to/#/#mageia-space:matrix.org matrix.org]: ngompa, neoclust, akien  *  [https://www.ovhcloud.com/ OVH DNS] ([http://bonjourmageia.fr  bonjourmageia.fr]):  ? *  [https://www.ovhcloud.com/ OVH DNS] ([http://bonjourmageia.fr  bonjourmageia.fr]):  ? −*  [https://www.scaleway.com/ Scaleway (madb)]: agallou (Adrien Gallou)+*  [https://www.mageialinux-online.com/ nFrance (madb)]: jybz/vouf  *  tumbler account (bonjourmageia): dams/boklm/ennael/rda/rtp *  tumbler account (bonjourmageia): dams/boklm/ennael/rda/rtp  *  [https://twitter.com/mageia_org X/Twitter]: dams/boklm/ennael/rda/rtp *  [https://twitter.com/mageia_org X/Twitter]: dams/boklm/ennael/rda/rtp Line 28: Line 29:     [[Who has power-rights-credentials?]] [[Who has power-rights-credentials?]] −  −[[Category:Sysadmin]]  Papoteur

new link for madb page

← Older revision Revision as of 14:22, 5 November 2024 Line 2: Line 2:  = Why we use the whiteboard = = Why we use the whiteboard =    −When update candidates or backport candidates are ready for QA to validate them the packager will create a bug on [[bugzilla]] and assign it to qa-bugs. At that point it appears on our qa-bugs mailing list and will also show on our [https://madb.mageia.org/tools/updates madb bugs list].+When update candidates or backport candidates are ready for QA to validate them the packager will create a bug on [[bugzilla]] and assign it to qa-bugs. At that point it appears on our qa-bugs mailing list and will also show on our [https://madb.mageia.org/updates madb bugs list].       Line 8: Line 8:       −You can see on the [https://madb.mageia.org/tools/updates madb bugs list] that this status information is neatly collated into a table, making it easy to view all bugs assigned to QA and see at a glance where our attention is most needed. It makes it easy to prioritise our work.+You can see on the [https://madb.mageia.org/updates madb bugs list] that this status information is neatly collated into a table, making it easy to view all bugs assigned to QA and see at a glance where our attention is most needed. It makes it easy to prioritise our work.       Papoteur

‎Also to be merged, possible extra replies in the forums: add "To be merged, private mail"

← Older revision Revision as of 12:53, 5 November 2024 Line 223: Line 223:     Maybe you should really care about the ones that are really interested in contributing to Mageia. I literally got tired of trying to find a new mentor, few years ago Zezinho(who passed away) was mentoring me, and then I wrote in the list since I wanted to continue my path in becoming a packager. Got no response from users. So I guess delegate the labour of recruiting people to this project might be a good start. Maybe you should really care about the ones that are really interested in contributing to Mageia. I literally got tired of trying to find a new mentor, few years ago Zezinho(who passed away) was mentoring me, and then I wrote in the list since I wanted to continue my path in becoming a packager. Got no response from users. So I guess delegate the labour of recruiting people to this project might be a good start.  +  +=To be merged, private mail=  +  +We should provide secure boot. Mageia lost users to other distro's because we don't offer it. In the USA, all corporations that process credit card data or personal date must have a secure workstation to protect sensitive data. This is why any hardware designated for business type use will not have the option to disable secure boot. Marja

Add Stephen Butler

← Older revision Revision as of 04:21, 5 November 2024 Line 161: Line 161:     User:zekemx User:zekemx  +  +User:Zeldas7777 Marja

Publication date: 05 Nov 2024
Type: bugfix
Affected Mageia releases : 9
Description A minimal install with grub2 installs graphical libraries, due to the inclusion of the grub2-mkfont binary in the core package. This update splits grub2-mkfont from the core package and make it an optional requirement helping to make more light installations. References

• https://bugs.mageia.org/show_bug.cgi?id=33695

SRPMS 9/core

• grub2-2.06-28.4.mga9

Publication date: 05 Nov 2024
Type: bugfix
Affected Mageia releases : 9
Description Use of SSE2 instructions even if not available for the processor makes digikam crash on some 32 bit systems. These updates fixes the issue. References

• https://bugs.mageia.org/show_bug.cgi?id=32102
• https://www.digikam.org/news/2023-07-09-8.1.0_release_announcement/
• https://www.digikam.org/news/2023-12-03-8.2.0_release_announcement/
• https://www.digikam.org/news/2024-03-17-8.3.0_release_announcement/
• https://www.digikam.org/news/2024-07-14-8.4.0_release_announcement/

SRPMS 9/core

• digikam-8.4.0-1.mga9

Escrito por el Equipo Atelier

Esto ha sido rápido, hace poco explicamos el motivo por el cual nuestra Base de Datos de Aplicaciones Mageia está fuera de servicio y ahora papoteur nos confirma que el nuevo MADb está listo.

Al abrir el sitio, la primera impresión será de que se ha conectado a la anterior versión del sitio, ya que la diferencias entre ambos son difíciles de notar (la primera imagen es del sitio anterior):

Pero eso solo es en apariencia, ya que las hojas de estilo (CSS) usadas tienen pocas modificaciones.

La herramienta anterior estaba escrita en PHP, ha sido completamente escrita desde cero utilizando Python, Flask, Jinja2 y DNF5. Papoteur mostró dos fragmentos de código como ejemplo de lo que ha cambiado (nuevamente el primero es de la versión anterior):

¡La diferencia es tanta como la de una página de un libro en Inglés comparada con una de un libro en Indonesio!

Se escribieron cerca de 3000 líneas de código para este nuevo MADb, que ahora está activo y listo para responder a sus búsquedas sobre aplicaciones de Mageia.

Les pedimos que mientras usen el sitio piensen sobre qué preguntas debería responder la función de ayuda integrada (aún no disponible), y también sobre lo que debería incluirse en la nueva página sobre MADb en el wiki. Por favor deje sus sugerencias en los comentarios en la versión en inglés del artículo, esta herramienta es para todos ustedes que hacen la comunidad de Mageia.

Un agradecimiento a la comunidad MLO por hospedar el nuevo MADb.

Traducido por katnatek de la publicación original de marja

Written by Atelier Team

That was fast: we have only just explained why our Mageia Application Database was offline and now papoteur tells us that new MADb is ready to be used.

Open the site and at first glance you might think you have somehow connected to the old site as the differences between it and the new one are hard to spot (the top one is the old site):

However, this is only the outward appearance, as the style sheets (CSS) were re-used with little modification.

The tool itself, previously written in PHP, has been completely rewritten from scratch, using Python, Flask, Jinja2 and DNF5, so the runtime code is entirely new. Papoteur showed two code snippets as an example of what really changed (again, the top one is old):

That is as different as a page from an English book compared to a page from its Indonesian translation!

About 3000 new lines of code were written for this new MADb, which is now live and ready to answer your queries about Mageia applications.

As you use the site, we ask you to think about what questions you feel an integrated help function (not yet available) should answer, and also what you feel we should include in a new wiki article about MADb. Please note your suggestions in the comments to this post, as you are all the Mageia community and this tool is for you.

Thanks to the MLO community for hosting new MADb.

I see sturmvogel fixed it like I suggested, thanks.

← Older revision Revision as of 23:53, 2 November 2024 Line 1: Line 1: −First time i followed this guide, wifi connection dropped when closing net_applet, so I had to connect cable to execute urpmi.     −Now second time, I executed the urpmi commands first, and that worked. (Plasma)  −  −So maybe the guide should be changed that way, or could there be a problem with that order, to start with installing packages before executing the rest (maybe I was lucky?)  −  −- Also, regarding disabling net_applet autostart, mention to do it for every desktop user.  −  −/Morgan  Morgano

‎Disable net_applet and enable networkmanger: fixed typo

← Older revision Revision as of 22:09, 2 November 2024 Line 24: Line 24:  {{command|urpmi plasma-applet-nm-openvpn|prompt=#}} {{command|urpmi plasma-applet-nm-openvpn|prompt=#}}    −== Disable net_applet and enable networkmanger ==+== Disable net_applet and enable networkmanager ==     It is recommended to disable {{prog|net_applet}} autostart. This can be achieved via right-click -> Settings or by running It is recommended to disable {{prog|net_applet}} autostart. This can be achieved via right-click -> Settings or by running Sturmvogel

‎Wie man Mageia Cauldron installiert: Warnung entfernt, da alle Anweisungen im weiteren enthalten. Falschen rpm Befehl korrigiert

← Older revision Revision as of 20:18, 2 November 2024 (2 intermediate revisions by the same user not shown)Line 32: Line 32:     ===  Wie man Mageia Cauldron installiert === ===  Wie man Mageia Cauldron installiert === −{{Warning-de|Am 10. Oktober 2024 wurde herausgefunden, dass die Crypto-Policies der rpm-sequoia Policy hinzugefügt werden muss, damit das Upgrade auf Cauldron funktioniert. '''Die Upgrade-Methode, welche unten beschrieben ist, funktioniert nicht. Gehen Sie stattdessen wie folgt vor:'''<br>  −* Ersetzen Sie die urpmi Repositorien mit denen von Cauldron (siehe hierzu weiter unten) und führen Sie 'urpmi.update -a' aus.  −* Entfernen Sie die alten rpm Schlüssel mit 'rpm -e gpg-pubkey-80420f66-4d4fe123'  −* Installieren Sie die 'aktualisierten' Schlüssel von Cauldron:  −** rpmkeys --import https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/media/core/release/media_info/pubkey  −* Installieren Sie crypto-policies-scripts  −* Führen Sie 'urpmi --auto-s --auto --force' aus um von MGA9 auf Cauldron zu aktualisieren}}      Es gibt zwei Möglichkeiten, Mageia Cauldron zu installieren. Beide Varianten haben Vorteile. Es gibt zwei Möglichkeiten, Mageia Cauldron zu installieren. Beide Varianten haben Vorteile. Line 55: Line 48:     Entfernen von Schlüsseln alter Pakete Entfernen von Schlüsseln alter Pakete −{{command|-derpm -e gpg-pubkey-80420f66-4d4fe123|prompt=#}}+{{command|rpm -e gpg-pubkey-80420f66-4d4fe123|prompt=#}}     Nun müssen die Cauldron Paketquellen hinzugefügt werden. Sie können entweder die Mirrorlist verwenden (diese wählt automatisch einen Spiegelserver für Sie aus) oder Sie verwenden einen bestimmten Spiegelserver. Nun müssen die Cauldron Paketquellen hinzugefügt werden. Sie können entweder die Mirrorlist verwenden (diese wählt automatisch einen Spiegelserver für Sie aus) oder Sie verwenden einen bestimmten Spiegelserver. Line 63: Line 56:     Wenn Sie die Mirrorlist verwenden wollen: Wenn Sie die Mirrorlist verwenden wollen: −{{command-de|urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.i686.list'|prompt=#}}+{{command-de|urpmi.addmedia --distrib --mirrorlist <nowiki>'http://mirrors.mageia.org/api/mageia.cauldron.i686.list'</nowiki>|prompt=#}}  oder: oder: −{{command-de|urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.x86_64.list'|prompt=#}}+{{command-de|urpmi.addmedia --distrib --mirrorlist <nowiki>'http://mirrors.mageia.org/api/mageia.cauldron.x86_64.list'</nowiki>|prompt=#}}     Wenn Sie einen spezifischen Spiegelserver verwenden wollen (Folgende URL ist ein Beispiel für einen Tier 1 Spiegelserver): Wenn Sie einen spezifischen Spiegelserver verwenden wollen (Folgende URL ist ein Beispiel für einen Tier 1 Spiegelserver): −{{command-de|urpmi.addmedia --distrib <nowiki>'https://mirror.accum.se/mirror/mageia/distrib/cauldron/i686/'</nowiki>|prompt=#}}+{{command-de|urpmi.addmedia --distrib <nowiki>'https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i686/'</nowiki>|prompt=#}}  oder: oder: −{{command-de|urpmi.addmedia --distrib 'https://mirror.accum.se/mirror/mageia/distrib/cauldron/x86_64/'</nowiki>|prompt=#}}+{{command-de|urpmi.addmedia --distrib <nowiki>'https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/'</nowiki>|prompt=#}}     Installiere die crypto-policies-scripts um sicherzustellen, dass die neusten Crypto-Policies verwendet werden: Installiere die crypto-policies-scripts um sicherzustellen, dass die neusten Crypto-Policies verwendet werden: Sturmvogel

‎Upgrade from the latest stable release to Cauldron using urpmi: reverted link to a broken mirror. check mirror status before pasting broken links...

← Older revision Revision as of 19:57, 2 November 2024 Line 62: Line 62:     If you want to use a specific server (the URL is an example tier 1 mirror): If you want to use a specific server (the URL is an example tier 1 mirror): −{{command|urpmi.addmedia --distrib <nowiki>'https://mirror.accum.se/mirror/mageia/distrib/cauldron/i686/'</nowiki>|prompt=#}}+{{command|urpmi.addmedia --distrib <nowiki>'https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i686/'</nowiki>|prompt=#}}  or: or: −{{command|urpmi.addmedia --distrib <nowiki>'https://mirror.accum.se/mirror/mageia/distrib/cauldron/x86_64/'</nowiki>|prompt=#}}+{{command|urpmi.addmedia --distrib <nowiki>'https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/'</nowiki>|prompt=#}}     Install crypto-policies-scripts to ensure latest crypto policies are applied: Install crypto-policies-scripts to ensure latest crypto policies are applied: Sturmvogel

Publication date: 02 Nov 2024
Type: security
Affected Mageia releases : 9
CVE: CVE-2023-52917 , CVE-2024-47670 , CVE-2024-47671 , CVE-2024-47672 , CVE-2024-47673 , CVE-2024-47675 , CVE-2024-47678 , CVE-2024-47679 , CVE-2024-47681 , CVE-2024-47682 , CVE-2024-47683 , CVE-2024-47684 , CVE-2024-47685 , CVE-2024-47686 , CVE-2024-47688 , CVE-2024-47689 , CVE-2024-47690 , CVE-2024-47691 , CVE-2024-47692 , CVE-2024-47693 , CVE-2024-47695 , CVE-2024-47696 , CVE-2024-47697 , CVE-2024-47698 , CVE-2024-47699 , CVE-2024-47700 , CVE-2024-47701 , CVE-2024-47704 , CVE-2024-47705 , CVE-2024-47706 , CVE-2024-47707 , CVE-2024-47709 , CVE-2024-47710 , CVE-2024-47712 , CVE-2024-47713 , CVE-2024-47714 , CVE-2024-47715 , CVE-2024-47716 , CVE-2024-47718 , CVE-2024-47719 , CVE-2024-47720 , CVE-2024-47722 , CVE-2024-47723 , CVE-2024-47725 , CVE-2024-47727 , CVE-2024-47728 , CVE-2024-47730 , CVE-2024-47731 , CVE-2024-47734 , CVE-2024-47735 , CVE-2024-47737 , CVE-2024-47738 , CVE-2024-47739 , CVE-2024-47740 , CVE-2024-47741 , CVE-2024-47742 , CVE-2024-47743 , CVE-2024-47744 , CVE-2024-47745 , CVE-2024-47747 , CVE-2024-47748 , CVE-2024-47749 , CVE-2024-47750 , CVE-2024-47751 , CVE-2024-47752 , CVE-2024-47753 , CVE-2024-47754 , CVE-2024-47755 , CVE-2024-47756 , CVE-2024-47757 , CVE-2024-49850 , CVE-2024-49851 , CVE-2024-49852 , CVE-2024-49853 , CVE-2024-49855 , CVE-2024-49856 , CVE-2024-49858 , CVE-2024-49859 , CVE-2024-49860 , CVE-2024-49861 , CVE-2024-49862 , CVE-2024-49863 , CVE-2024-49864 , CVE-2024-49866 , CVE-2024-49867 , CVE-2024-49868 , CVE-2024-49870 , CVE-2024-49871 , CVE-2024-49874 , CVE-2024-49875 , CVE-2024-49877 , CVE-2024-49878 , CVE-2024-49879 , CVE-2024-49881 , CVE-2024-49882 , CVE-2024-49883 , CVE-2024-49884 , CVE-2024-49886 , CVE-2024-49889 , CVE-2024-49890 , CVE-2024-49892 , CVE-2024-49894 , CVE-2024-49895 , CVE-2024-49896 , CVE-2024-49900 , CVE-2024-49901 , CVE-2024-49902 , CVE-2024-49903 , CVE-2024-49905 , CVE-2024-49907 , CVE-2024-49912 , CVE-2024-49913 , CVE-2024-49924 , CVE-2024-49925 , CVE-2024-49927 , CVE-2024-49929 , CVE-2024-49930 , CVE-2024-49931 , CVE-2024-49933 , CVE-2024-49935 , CVE-2024-49936 , CVE-2024-49937 , CVE-2024-49938 , CVE-2024-49939 , CVE-2024-49944 , CVE-2024-49946 , CVE-2024-49947 , CVE-2024-49948 , CVE-2024-49949 , CVE-2024-49950 , CVE-2024-49951 , CVE-2024-49952 , CVE-2024-49953 , CVE-2024-49954 , CVE-2024-49955 , CVE-2024-49957 , CVE-2024-49958 , CVE-2024-49959 , CVE-2024-49960 , CVE-2024-49961 , CVE-2024-49962 , CVE-2024-49963 , CVE-2024-49965 , CVE-2024-49966 , CVE-2024-49967 , CVE-2024-49969 , CVE-2024-49973 , CVE-2024-49975 , CVE-2024-49976 , CVE-2024-49977 , CVE-2024-49978 , CVE-2024-49980 , CVE-2024-49981 , CVE-2024-49982 , CVE-2024-49983 , CVE-2024-49985 , CVE-2024-49986 , CVE-2024-49987 , CVE-2024-49988 , CVE-2024-49989 , CVE-2024-49991 , CVE-2024-49992 , CVE-2024-49993 , CVE-2024-49995 , CVE-2024-49996 , CVE-2024-49997 , CVE-2024-50000 , CVE-2024-50001 , CVE-2024-50002 , CVE-2024-50003 , CVE-2024-50005 , CVE-2024-50006 , CVE-2024-50007 , CVE-2024-50008 , CVE-2024-50012 , CVE-2024-50013 , CVE-2024-50015 , CVE-2024-50016 , CVE-2024-50019 , CVE-2024-50022 , CVE-2024-50023 , CVE-2024-50024 , CVE-2024-50026 , CVE-2024-50029 , CVE-2024-50031 , CVE-2024-50032 , CVE-2024-50033 , CVE-2024-50035 , CVE-2024-50036 , CVE-2024-50038 , CVE-2024-50039 , CVE-2024-50040 , CVE-2024-50041 , CVE-2024-50044 , CVE-2024-50045 , CVE-2024-50046 , CVE-2024-50047 , CVE-2024-50048 , CVE-2024-50049 , CVE-2024-50055 , CVE-2024-50057 , CVE-2024-50058 , CVE-2024-50059 , CVE-2024-50060 , CVE-2024-50061 , CVE-2024-50062 , CVE-2024-50063 , CVE-2024-50064 , CVE-2024-50065 , CVE-2024-50066 Description Upstream kernel version 6.6.58 fixes bugs and vulnerabilities. The kmod-virtualbox and kmod-xtables-addons packages have been updated to work with this new kernel. For information about the vulnerabilities see the links. References

• https://bugs.mageia.org/show_bug.cgi?id=33667
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.53
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.54
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.55
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.56
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.57
• https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.58
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52917
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47670
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47671
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47672
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47673
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47675
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47678
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47679
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47681
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47682
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47683
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47684
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47685
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47686
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47688
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47689
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47690
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47691
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47692
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47693
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47695
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47696
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47697
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47698
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47699
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47700
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47701
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47704
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47705
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47706
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47707
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47709
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47710
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47712
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47713
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47714
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47715
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47716
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47718
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47719
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47720
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47722
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47723
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47725
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47727
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47728
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47730
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47731
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47734
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47735
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47737
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47738
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47739
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47740
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47741
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47742
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47743
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47744
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47745
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47747
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47748
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47749
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47750
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47751
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47752
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47753
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47754
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47755
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47756
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47757
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49850
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49851
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49852
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49853
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49855
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49856
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49858
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49859
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49860
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49861
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49862
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49863
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49864
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49866
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49867
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49868
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49870
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49871
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49874
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49875
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49877
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49878
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49879
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49881
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49882
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49883
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49884
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49886
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49889
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49890
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49892
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49894
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49895
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49896
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49900
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49901
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49902
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49903
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49905
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49907
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49912
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49913
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49924
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49925
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49927
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49929
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49930
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49931
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49933
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49935
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49936
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49937
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49938
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49939
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49944
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49946
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49947
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49948
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49949
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49950
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49951
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49952
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49953
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49954
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49955
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49957
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49958
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49959
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49960
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49961
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49962
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49963
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49965
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49966
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49967
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49969
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49973
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49975
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49976
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49977
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49978
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49980
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49981
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49982
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49983
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49985
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49986
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49987
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49988
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49989
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49991
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49992
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49993
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49995
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49996
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49997
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50000
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50001
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50002
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50003
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50005
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50006
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50007
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50008
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50012
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50013
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50015
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50016
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50019
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50022
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50023
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50024
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50026
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50029
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50031
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50032
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50033
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50035
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50036
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50038
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50039
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50040
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50041
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50044
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50045
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50046
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50047
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50048
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50049
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50055
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50057
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50058
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50059
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50060
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50061
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50062
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50063
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50064
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50065
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50066

SRPMS 9/nonfree

• kernel-firmware-nonfree-20240909-1.mga9.nonfree
• radeon-firmware-20240909-1.mga9.nonfree

9/core

• kernel-6.6.58-2.mga9
• kmod-xtables-addons-3.24-65.mga9
• kmod-virtualbox-7.0.20-57.mga9
• kernel-firmware-20240909-1.mga9