Wiki de Mageia

‎Running Live on weak computers: moved Trinity to point after other desktops, added tip on firejail file access

← Older revision Revision as of 15:46, 27 January 2026 (One intermediate revision by the same user not shown)Line 498: Line 498:  * Using persistence save on RAM compared to using a ramdisk which otherwise is used. * Using persistence save on RAM compared to using a ramdisk which otherwise is used.  * Use swap to free more RAM - [[#Swap_file|add a swap file]] or partition: [[#Custom_partitioning|Custom partitioning]]. ''A few hundred MB is enough unless you want to hibernate.'' * Use swap to free more RAM - [[#Swap_file|add a swap file]] or partition: [[#Custom_partitioning|Custom partitioning]]. ''A few hundred MB is enough unless you want to hibernate.'' −* Use a lightweight desktop such as Xfce, or one of our even lighter desktops - IceWM is installed in all Lives already. ''Note that you can have several desktops installed and choose at each login which to use.''+* Use a '''lightweight desktop''' such as Xfce, or one of our even lighter desktops - IceWM is installed in all Lives already. ''Note that you can have several desktops installed and choose at each login which to use.''  +* The third party '''lightweight desktop {{Prog|Trinity}}''' ''(forked KDE3)'' include a plethora of relatively lightweight programs. [[Desktop_environments#TDE_Trinity_Desktop_Environment|Installation instructions here.]]  * Use light weight programs. i.e Falkon for web browsing, and Gwenview for browsing-cropping-resizing photos. ''(Even Xfce by default use the heavy Firefox and Gimp, respectively)'' * Use light weight programs. i.e Falkon for web browsing, and Gwenview for browsing-cropping-resizing photos. ''(Even Xfce by default use the heavy Firefox and Gimp, respectively)'' −* If you have more than 2GBs of RAM available in your old computer, you could install firejail to run certain programs on the RAM. It is significantly faster than the USB stick (especially USB 2.0). But it also means that you will not be able to save almost anything. The following have been tested with lightweight window managers.+* If you have more than 2GBs of RAM available in your old computer, you could install firejail to run certain programs on the RAM. It is significantly faster than the USB stick (especially USB 2.0). But it also means that you will not be able to save almost anything. - But restrictions can altered: see the options "read-only" and "read-write" here: {{cmd|man firejail}}, {{cmd|firejail --help}}. The following have been tested with lightweight window managers.    Example commands:   Example commands:    firejail --private falkon   firejail --private falkon    firejail --private firefox   firejail --private firefox    firejail --private --appimage ~/apps/librewolf/LibreWolf.x86_64.AppImage   firejail --private --appimage ~/apps/librewolf/LibreWolf.x86_64.AppImage −* You can set your web browser to prefer the, much lighter, mobile version of a website (provided that there is a mobile version), instead of the standard version. Depending on the website, the experience may vary from "great" to "dysfunctional". The easiest way to do that is to install an extension like [https://addons.mozilla.org/el/firefox/addon/user-agent-string-switcher/  User Agent Switcher and Manager], and then customize your web browser's User Agent, to something like...+* You can set your web browser to prefer the much lighter mobile version of a website (provided that there is a mobile version), instead of the standard version. Depending on the website, the experience may vary from "great" to "dysfunctional". The easiest way to do that is to install an extension like [https://addons.mozilla.org/el/firefox/addon/user-agent-string-switcher/  User Agent Switcher and Manager], and then customize your web browser's User Agent, to something like...    Mozilla/5.0 (Android 15; Mobile; rv:145.0) Gecko/145.0 Firefox/145.0   Mozilla/5.0 (Android 15; Mobile; rv:145.0) Gecko/145.0 Firefox/145.0  Unfortunately some browsers currently do not have such working extensions (e.g. Falkon, SeaMonkey). Unfortunately some browsers currently do not have such working extensions (e.g. Falkon, SeaMonkey). −* [[Desktop_environments#TDE_Trinity_Desktop_Environment | Trinity (KDE3)]] has a plethora of relatively lightweight programs. You will need to enable Trinity's rpm repositories, in order to access their applications. Tip in a tip: Using Mageia's tools (<code>drakrpm-edit-media</code>) will help you mark Trinity's software media as update media.      == Caution == == Caution == Morgano

‎TDE Trinity Desktop Environment

← Older revision Revision as of 15:16, 27 January 2026 Line 119: Line 119:     [https://wiki.trinitydesktop.org/Mageia_Trinity_Repository_Installation_Instructions Mageia Trinity Repository Installation Instructions] [https://wiki.trinitydesktop.org/Mageia_Trinity_Repository_Installation_Instructions Mageia Trinity Repository Installation Instructions]  +  +In addition the the instructions there, you may want to tell our tools to look for '''updates''' in case they are released there. To do so, execute {{cmd|drakrpm-editmedia --expert}} and put check marks in the "Updates" column before the Trinity repositories.     == Logging in to other desktop environments == == Logging in to other desktop environments == Morgano

‎Testing: Updating

← Older revision Revision as of 15:06, 27 January 2026 (2 intermediate revisions by the same user not shown)Line 67: Line 67:  * Your favourite software we have in our repositories. * Your favourite software we have in our repositories.  * [[Ways_to_install_programs|Other software of interest]] - But do not "bug" us of issues not related to Mageia. * [[Ways_to_install_programs|Other software of interest]] - But do not "bug" us of issues not related to Mageia.  +  +==== Updating ===  +  +Now during development, packages are updated directly over elder packages in release repositories, and our updater tools look for updates there.     ==== Upgrading from Mageia 9 ==== ==== Upgrading from Mageia 9 ==== Line 75: Line 79:  * Follow normal [[Mageia_10_Release_Notes#Upgrading_from_Mageia_9|upgrade procedures]]. * Follow normal [[Mageia_10_Release_Notes#Upgrading_from_Mageia_9|upgrade procedures]].  * And account for: [[#Release_repositories_do_change|Release repositories do change]]. * And account for: [[#Release_repositories_do_change|Release repositories do change]].  +* Notable problems (read for workaround) at time of writing this:  +** {{Bug|34966}} - kwin_x11 not installed anymore after an upgrade  +** {{Bug|35063}} - Unable to upgrade Mageia10-alpha1 due to certificate error     ''Alternatively you may like to upgrade to [[Cauldron|Cauldron]]. Note that you would shortly after Mageia 10 release probably want to switch repositories from Cauldron to Mageia 10.'' ''Alternatively you may like to upgrade to [[Cauldron|Cauldron]]. Note that you would shortly after Mageia 10 release probably want to switch repositories from Cauldron to Mageia 10.'' −<!--  −==== Updating an installed system ====     −To get updates, you must set your system to get updates from the release repository. -[[Release_repositories_do_change|Release repositories do change]] during this development phase!  −  −# Like normal, you need to have set up repositories.  −# Then one way is to add a checkmark in updates column for release repositories using our tool {{prog|drakrpm-editmedia}}. -But to be able to change updates repository, you need to launch it in expert mode like so:  {{cmd|drakrpm-editmedia --expert}}.  −  −Then after Mageia is finally released, unset release repositories from being update repositories.   −-->   ==== Found a problem? ==== ==== Found a problem? ==== − +* Do the problem go away after updating the system?  * See [[#Current_status|Current status]], [[#Current_notes|Current notes]], and [[#Expected_problems|Expected problems]] below. * See [[#Current_status|Current status]], [[#Current_notes|Current notes]], and [[#Expected_problems|Expected problems]] below.  * Search for if it is already described in [[Mageia_10_Errata|the Errata]] or if it is told in [[Mageia_10_Release_Notes|Release Notes]]. * Search for if it is already described in [[Mageia_10_Errata|the Errata]] or if it is told in [[Mageia_10_Release_Notes|Release Notes]]. Line 103: Line 101:  == Current notes == == Current notes ==  '' To be revised at each pre-release release (remove old stuff), and updated any time needed.''<br> '' To be revised at each pre-release release (remove old stuff), and updated any time needed.''<br> −''' ''Revised 2026-01-11'' '''<br>+''' ''Revised 2026-01-27'' '''<br>  Current version of ISOs: '''10alpha1''' ''(from internal round 2)''<br> Current version of ISOs: '''10alpha1''' ''(from internal round 2)''<br>  === Prominent enhancements comparing to Mageia 9 === === Prominent enhancements comparing to Mageia 9 ===  +* Updated applications, desktops, basesystems, drivers, kernel...<br>  ''For more complete list see Release Notes.'' ''For more complete list see Release Notes.'' −* Kernel series: default is 6.12.63 LTS (so used in Live ISOs). Available in repos: 6.18.4 LTS+==== 10alpha1 ==== −* Updated desktops and other software of course.+* Kernel series: default is 6.12.63 LTS (so used in Live ISOs). ''Available in repos: '''6.18.7+''' LTS'' −==== Upcoming next pre-release ====+==== Upcoming next pre-release - 10beta1 ====  * Classic installer wifi support {{Bug|32125}} * Classic installer wifi support {{Bug|32125}}  * Updated hardware detection * Updated hardware detection Morgano

‎Running Live on weak computers: Trinity (KDE3)

← Older revision Revision as of 08:48, 27 January 2026 Line 508: Line 508:    Mozilla/5.0 (Android 15; Mobile; rv:145.0) Gecko/145.0 Firefox/145.0   Mozilla/5.0 (Android 15; Mobile; rv:145.0) Gecko/145.0 Firefox/145.0  Unfortunately some browsers currently do not have such working extensions (e.g. Falkon, SeaMonkey). Unfortunately some browsers currently do not have such working extensions (e.g. Falkon, SeaMonkey).  +* [[Desktop_environments#TDE_Trinity_Desktop_Environment | Trinity (KDE3)]] has a plethora of relatively lightweight programs. You will need to enable Trinity's rpm repositories, in order to access their applications. Tip in a tip: Using Mageia's tools (<code>drakrpm-edit-media</code>) will help you mark Trinity's software media as update media.     == Caution == == Caution == Nikos5446

‎Dorsync

← Older revision Revision as of 00:05, 26 January 2026 Line 169: Line 169:  Enter between the " marks: Enter between the " marks:  * location: The path of your umbrella ISO directory, which once defined you will probably not alter. * location: The path of your umbrella ISO directory, which once defined you will probably not alter. −* release: e.g. ''mageia10-alpha''; to be changed at each new Release as announced on the QA MailList.+* release: e.g. ''mageia10-alpha''; '''change this at each new Release as announced on the QA MailList.'''  * user: The current rsync username e.g. ''isoqa''; normally constant, but may change; which is announced and defined on tha QA MailList. * user: The current rsync username e.g. ''isoqa''; normally constant, but may change; which is announced and defined on tha QA MailList.  * password: The rsync password, given out by private e-mail; changes announced (but not given) on tha QA MailList. * password: The rsync password, given out by private e-mail; changes announced (but not given) on tha QA MailList. Line 272: Line 272:  Dorsync can update files in place, provided they have the new name. Dorsync can update files in place, provided they have the new name.  Before using dorsync for the new Release, you ''must''   Before using dorsync for the new Release, you ''must''   −* Update the settings in dorsync.conf.+* Update the setting after release= in dorsync.conf. −* Update accordingly all your likal ISO directory names and all their subordinate filenames. This is quickly done in your ISOs umbrella directory by a couple of precise ''rename'' commands (and they have to be exactly right) given out on the mailing list. You can copy/paste them into a console.+* Update accordingly all your local ISO directory names and all their subordinate filenames. This is quickly done in your ISOs umbrella directory by a couple of precise ''rename'' commands (and they have to be exactly right) given out on the mailing list. You can copy/paste them into a console.  Or lazily just manually rename the directories and .iso files and delete the rest of files, they are small to download... −* If you use the ''dorsync.skip'' file to exclude ISOs, update that also. As an aid, to list the new ISO names, do+* If you use the ''dorsync.skip'' file to exclude ISOs, update that also. -Or simply delete it, and dorsync will ask which you want. − $ RSYNC_PASSWORD="<password>" rsync --list-only rsync://isoqa@bcd.mageia.org/isos/<Release>/  −where <Release> is e.g. ''mageia10-alpha1''.      == Onesync == == Onesync == Morgano

← Older revision Revision as of 16:33, 25 January 2026 (One intermediate revision by the same user not shown)Line 98: Line 98:     # {{Press item|FileEnergy|https://fileenergy.com/component/finder/search?q{{=}}mageia+10&Itemid{{=}}111|https://fileenergy.com/component/finder/search?q{{=}}mageia+10&Itemid{{=}}111|2026-01-17}} # {{Press item|FileEnergy|https://fileenergy.com/component/finder/search?q{{=}}mageia+10&Itemid{{=}}111|https://fileenergy.com/component/finder/search?q{{=}}mageia+10&Itemid{{=}}111|2026-01-17}} −  −#      == Spanish - Español == == Spanish - Español ==    −=== Blog de Mageia en Español ===  −# {{Press item|Mageia Blog (Español)|https://blog.mageia.org/es/2026/01/11/mageia-10-primera-alpha-iso-validada-por-el-consejo/|Mageia 10 Primera Alpha ISO validada por el Consejo|2026-01-11}}   # {{Press item|Reddit Español|https://www.reddit.com/r/Ubuntu_ES18011979/comments/1qbnrxd/versi%C3%B3n_de_desarrollo_mageia_10_alpha/|Versión de desarrollo: Mageia 10 Alpha |2026-01-13}} # {{Press item|Reddit Español|https://www.reddit.com/r/Ubuntu_ES18011979/comments/1qbnrxd/versi%C3%B3n_de_desarrollo_mageia_10_alpha/|Versión de desarrollo: Mageia 10 Alpha |2026-01-13}}  # {{Press item|Soploslinux.com|https://soploslinux.com/instalar-mageia-10-alpha-un-viaje-nostalgico-al-futuro-de-un-clasico-linux/|Instalar Mageia 10 Alpha: Un Viaje Nostálgico al Futuro de un Clásico Linux|2026-01-21}} # {{Press item|Soploslinux.com|https://soploslinux.com/instalar-mageia-10-alpha-un-viaje-nostalgico-al-futuro-de-un-clasico-linux/|Instalar Mageia 10 Alpha: Un Viaje Nostálgico al Futuro de un Clásico Linux|2026-01-21}} Line 116: Line 112:  == Turkish -Türkçe == == Turkish -Türkçe ==    −# {{Press item|getgnu Türkçe|https://www.getgnu.org/gnulinux/mageia-10-alpha-1-duyuruldu.html|Mageia 10 Alpha 1 duyuruldu|2026-01-16}}+# {{Press item|getGNU|https://www.getgnu.org/gnulinux/mageia-10-alpha-1-duyuruldu.html|Mageia 10 Alpha 1 duyuruldu|2026-01-16}}     <!-- <!-- Line 129: Line 125:  == Mageia Blog == == Mageia Blog ==    −'''http://blog.mageia.org/'''+# '''http://blog.mageia.org/''' − +# {{Press item|Español|https://blog.mageia.org/es/2026/01/11/mageia-10-primera-alpha-iso-validada-por-el-consejo/|Mageia 10 Primera Alpha ISO validada por el Consejo|2026-01-11}} −#  Morgano

Show changes Morgano

tell this page will be replaced

← Older revision Revision as of 11:46, 25 January 2026 Line 5: Line 5:  {{multi language banner|[[How_to_write_and_translate_Mageia_doc|English]] ; [[Como_escrever_e_trduzir_documentos_Mageia_pt_PT|Portuguese (Portugal)]] ;}} {{multi language banner|[[How_to_write_and_translate_Mageia_doc|English]] ; [[Como_escrever_e_trduzir_documentos_Mageia_pt_PT|Portuguese (Portugal)]] ;}}    −{{template:draft}}+'''This page is OUTDATED and will be replaced as soon as possible by [[How to write our official documentation]] and [[How to translate our official documentation]]'''     == Introduction == == Introduction == Marja

‎From writing to publishing

← Older revision Revision as of 11:37, 25 January 2026 Line 18: Line 18:  == From writing to publishing == == From writing to publishing ==    −Our manuals and help files are written using XML files. They are written with Calenco tools on the Calenco website, although it is also possible to upload new or changed XML files. The latter is done for all translations. Calenco tools are used to create HTML, WebHelp HTML, EPUB and PDF publications. See [https://publish.calenco.com/Calenco/en/780251e6-0bc8-4597-8cac-202917f5c77d-1621626492/index.html Calenco's exhaustive documentation]. There is also a very short [https://www.calenco.com/en/Documentation/Getting-to-write-quickly.html quickstarter] available.+Our manuals and help files are written using DocBook XML files. They are written with Calenco tools on the Calenco website, although it is also possible to upload new or changed XML files. The latter is done for all translations. Calenco tools are used to create HTML, WebHelp HTML, EPUB and PDF publications. See [https://publish.calenco.com/Calenco/en/780251e6-0bc8-4597-8cac-202917f5c77d-1621626492/index.html Calenco's exhaustive documentation]. There is also a very short [https://www.calenco.com/en/Documentation/Getting-to-write-quickly.html quickstarter] available.     == Calenco access == == Calenco access == Marja

start stub

New page

[[Category:Doc]]
[[Category:Howtos]]
[[Category:l10n]]

{{multi language banner|[[How_to_translate_our_official_documentation|English]]; None yet}}

{{template:draft}}

To be created. Together with [[How to write our official documentation]] intended as replacement of outdated [[How to write and translate Mageia doc]] Marja

Start page

New page

[[Category:Doc]]
[[Category:Howtos]]

{{multi language banner|[[How_to_write_our_official_documentation|English]]; None yet}}

{{template:draft}}

== Introduction ==

This page deals with the tools and processes to write Mageia's official documentation. Whilst primarily intended for use by members of the Documentation Team, all are welcome to read it.

This page is intended to replace [[How to write and translate Mageia doc]], which became outdated. About translating our official documentation, [[How to translate our official documentation]] will be written later.

== Requirements ==

If you aren't coming from this page [https://wiki.mageia.org/en/Documentation_team https://wiki.mageia.org/en/Documentation_team], have a look on it. You will learn how to join the Doc team and how to subscribe the doc-discuss mailing list. It is the place to be to have all the needed information about works in progress.

== From writing to publishing ==

Our manuals and help files are written using XML files. They are written with Calenco tools on the Calenco website, although it is also possible to upload new or changed XML files. The latter is done for all translations. Calenco tools are used to create HTML, WebHelp HTML, EPUB and PDF publications. See [https://publish.calenco.com/Calenco/en/780251e6-0bc8-4597-8cac-202917f5c77d-1621626492/index.html Calenco's exhaustive documentation]. There is also a very short [https://www.calenco.com/en/Documentation/Getting-to-write-quickly.html quickstarter] available.

== Calenco access ==

If you would like to help improve our official documentation and have already helped to improve the English part of our wiki, then you can ask for credentials.

However, If we see that we haven't managed to explain you well enough how to correctly contribute to the wiki, then we first need to find a way to improve our communication.<br/><br/>

If that isn't a problem, then you can send a mail to <br/>
"papoteur At mageia DOT org"
This e-mail must include the following information:
* Your full name (given name + surname)
* The chosen nickname Marja

‎Kernel maintenance: About kernel -devel packages and related

← Older revision Revision as of 23:36, 24 January 2026 Line 200: Line 200:           We have a helper: Beginning with Mageia 9 on 64 bit Live like on a 64 bit installed system, {{cmd|rok}}, [[Mageia_9_Release_Notes#remove-old-kernels|remove-old-kernels]] is installed. The updated 1.0.3+ version detects when it runs on a Live system and then keep max 2 kernels (of each flavour - note backport kernel is of another flavour) and does never uninstall the original kernel.  rok runs occasionally in the background which means on slow USB dives the system may suddenly become sluggish for a while, and Xfce file managers pop up {{Bug|34964}}.  To avoid such surprise you may want to disable rok from running automatically by launching it by {{cmd|rok -A0}} as root. We have a helper: Beginning with Mageia 9 on 64 bit Live like on a 64 bit installed system, {{cmd|rok}}, [[Mageia_9_Release_Notes#remove-old-kernels|remove-old-kernels]] is installed. The updated 1.0.3+ version detects when it runs on a Live system and then keep max 2 kernels (of each flavour - note backport kernel is of another flavour) and does never uninstall the original kernel.  rok runs occasionally in the background which means on slow USB dives the system may suddenly become sluggish for a while, and Xfce file managers pop up {{Bug|34964}}.  To avoid such surprise you may want to disable rok from running automatically by launching it by {{cmd|rok -A0}} as root.  +  +==== About kernel -devel packages ====  +Note that for '''(the few) wifi''' adapters needing drivers rtl8192eu or broadcom-wl:  If Live finds such hardware during boot, kernel modules will be automatically complied for it. For this to succeed, the corresponding -devel package for the running kernel needs to be installed. The same applies to the '''proprietary nvidia''' driver(s) if you choose that boot alternative or install them another way.  +  +From the beginning there is no -devel- package installed in Live systems. It is however like other packages needed for compilation included in the in-ISO repositories and gets installed when needed. But of course it is the version for the original kernel - not compatible with other kernels you install.  +  +That means that if you update the system and get a new kernel, you should manually '''install the same kernel package that have "-devel-" added in the name''', so the system is prepared to compile kernel modules whenever needed.  Also note that at least for nvidia, you should also keep the driver updated - as early driver sometimes do not work for a late kernel.  Once installed, -devel packages and drivers will be updated like the kernel when you update the system.     == Custom Live ISO == == Custom Live ISO == Morgano

‎Backport kernels: Released :-)

← Older revision Revision as of 23:24, 24 January 2026 Line 71: Line 71:     '''In Mageia 9'''<br> '''In Mageia 9'''<br> −''{{Bug|34962}} January 2026 kernels are currently in backport_testing repo''<br>+Kernel 6.18.4+ is provided since January 2026 in the core backport repository for x86_64 in desktop and server flavour, and for i586 the same plus desktop586.<br> −Kernel 6.18.4+ is provided in Backport repository for all architectures in desktop and server flavour, plus desktop586.<br>+For aarch64 and armv7hl we currently only provide source and doc packages. <br> −You also find kernel 6.12.60 for all architectures in desktop flavour in Backort testing repository ''- note that it is old security wise now but you may like to ''test'' it if 6.18 is not compatible for your use.''<br>+You also find kernel 6.12.60 for all architectures in desktop flavour in core backort testing repository ''- note that it is old security wise now but you may like to ''test'' it if 6.18 is not compatible for your use.''<br>     Only two packages to install per kernel''' (from Backport): <br> Only two packages to install per kernel''' (from Backport): <br> Morgano

← Older revision Revision as of 21:15, 24 January 2026 Line 71: Line 71:     '''In Mageia 9'''<br> '''In Mageia 9'''<br> −''{{Bug|34962}} January 2026 kernels are currently in backport_testing repo)''<br>+''{{Bug|34962}} January 2026 kernels are currently in backport_testing repo''<br>  Kernel 6.18.4+ is provided in Backport repository for all architectures in desktop and server flavour, plus desktop586.<br> Kernel 6.18.4+ is provided in Backport repository for all architectures in desktop and server flavour, plus desktop586.<br>  You also find kernel 6.12.60 for all architectures in desktop flavour in Backort testing repository ''- note that it is old security wise now but you may like to ''test'' it if 6.18 is not compatible for your use.''<br> You also find kernel 6.12.60 for all architectures in desktop flavour in Backort testing repository ''- note that it is old security wise now but you may like to ''test'' it if 6.18 is not compatible for your use.''<br> Line 92: Line 92:  kernel-stable-testing-source <br> kernel-stable-testing-server <br> kernel-stable-testing-server-devel <br> kernel-stable-testing-desktop <br> kernel-stable-testing-desktop-devel <br>   kernel-stable-testing-source <br> kernel-stable-testing-server <br> kernel-stable-testing-server-devel <br> kernel-stable-testing-desktop <br> kernel-stable-testing-desktop-devel <br>    kernel-stable-testing-desktop586<br> kernel-stable-testing-desktop586-devel <br> kernel-stable-testing-desktop586<br> kernel-stable-testing-desktop586-devel <br> −:''(The three first only needed for 6.12, the other for 6.18 where the two last are only needed for i585 systems.)''+:''(The three first only needed for 6.12, the other for 6.18 where the two last are only needed for i586 systems.)''     === Backport incompatibilities === === Backport incompatibilities === Psyca

← Older revision Revision as of 21:14, 24 January 2026 Line 65: Line 65:  Es ist möglich, dass ein Kernel für zuvor veröffentlichte Mageia Ausgaben zurückportiert wird, zum Beispiel von Cauldron zur offiziellen, aktuell verfügbaren, Mageia Version. Es ist möglich, dass ein Kernel für zuvor veröffentlichte Mageia Ausgaben zurückportiert wird, zum Beispiel von Cauldron zur offiziellen, aktuell verfügbaren, Mageia Version.    −'''Für Mageia 9,  ''aktuell in Arbeit'' '''+'''Für Mageia 9'''<br>    −Kernel 6.12.60+ (funktioniert, aber ist sicherheitstechnisch alt) und 6.18.4+ befinden sich in den Backport Repositorien für alle Architekturen '''als Desktop Variante und 6.18 auch als Server Variante''' ''- ansonsten keine weitere Varianten.''<br>+''{{Bug|34962}} Januar 2026 Kernel befinden sich aktuell im backport_testing Repository''<br>  +Kernel 6.18.4+ wird in den Backport Repositorien für alle Architekturen, für Desktop und Server, sowie desktop586, angeboten.<br>  +Sie finden auch Kernel 6.12.60 für alle Architekturen für den Desktop im backport testing Repository '' - beachten Sie, dass dieser alt ist, was die Sicherheit betrifft, aber Sie möchten diese gegebenenfalls zum ''testen'' verwenden, falls 6.18 nicht mit Ihrem System kompatibel ist.''<br>    −''('''In Bearbeitung''' {{Bug|34962}} Januar 2026; Kernel befinden sich aktuell im backport_testing Repositorium)''<br>  −'''<br>   Es werden nur zwei Pakete pro Kernel installiert''' (aus Backport): <br> Es werden nur zwei Pakete pro Kernel installiert''' (aus Backport): <br>  kernel-stable-desktop-6.12... / kernel-stable-testing-desktop-6.18... / kernel-stable-testing-server-6.18 <br> kernel-stable-desktop-6.12... / kernel-stable-testing-desktop-6.18... / kernel-stable-testing-server-6.18 <br> Line 80: Line 80:  '''Betreffend kernel-*-userspace-headers''' gegen ''kernel-userspace-headers bei 6.6 Kerneln:'' Diese Pakete werden benötigt um Anwendungen zu paketieren; verwenden Sie den für den aktuellen Kernel, für den Sie dies Pakte erstellen. Sie stehen untereinander in Konflikt und werden von urpmi & drakrpm richtig gehandhabt - wenn Sie die  '''mageia-repos und meta-task packages''' auf Version 9.4 aktualisiert haben - und eine Kernelvariante >= 6.6.105, welche nicht aus aus dem Backport Repository stammt, verwenden. '''Betreffend kernel-*-userspace-headers''' gegen ''kernel-userspace-headers bei 6.6 Kerneln:'' Diese Pakete werden benötigt um Anwendungen zu paketieren; verwenden Sie den für den aktuellen Kernel, für den Sie dies Pakte erstellen. Sie stehen untereinander in Konflikt und werden von urpmi & drakrpm richtig gehandhabt - wenn Sie die  '''mageia-repos und meta-task packages''' auf Version 9.4 aktualisiert haben - und eine Kernelvariante >= 6.6.105, welche nicht aus aus dem Backport Repository stammt, verwenden.    −'''Remove-Old-Kernels''', {{prog|rok}}, kann weder den Kernel 6.12 erkennen, noch mit diesem umgehen, weshalb Sie nicht mehr benötigte Kernel händisch deinstallieren 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+'''Remove-Old-Kernels''', {{prog|rok}}, kann weder den Kernel 6.12 erkennen, noch mit diesem umgehen, weshalb Sie nicht mehr benötigte Kernel händisch deinstallieren 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 (für alle backport Kernel-Arten)<br> −kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source <br>+kernel-stable-source <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> −kernel-stable-testing-desktop <br> kernel-stable-testing-desktop-devel <br> kernel-stable-testing-server <br> kernel-stable-testing-server-devel <br> kernel-stable-testing-source+kernel-stable-testing-source <br> kernel-stable-testing-server <br> kernel-stable-testing-server-devel <br> kernel-stable-testing-desktop <br> kernel-stable-testing-desktop-devel <br>   − +kernel-stable-testing-desktop586<br> kernel-stable-testing-desktop586-devel <br> −'''Wenn VirtualBox < 7.1.14 ausgeführt wird''', schauen Sie nach  {{Bug|34408#c7}}.+:''(Die ersten drei werden nur für Kernel 6.12 benötigt, das andere für 6.18, während die beiden letzten nur für i586 Systeme benötigt werden.)''     == Inkompatibilitäten bei Rückportierungen == == Inkompatibilitäten bei Rückportierungen ==  Rückportierte Kernel haben möglicherweise Probleme mit älterer Hardware, Software oder Werkzeugen. Bekannte Probleme: Rückportierte Kernel haben möglicherweise Probleme mit älterer Hardware, Software oder Werkzeugen. Bekannte Probleme:  * GPU Kabini Radeon HD 8210 (und möglicherweise ähnliche) benötigen folgenden Parameter im Kernel Startbefehl: "radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1" {{Bug|34545#c162}}. Zum Testen drücken Sie {{keypress|e}} im Startmenü. Für eine bestehende Änderung schauen Sie [[Wie_man_Kerneloptionen_einstellt-de|hier]]. * GPU Kabini Radeon HD 8210 (und möglicherweise ähnliche) benötigen folgenden Parameter im Kernel Startbefehl: "radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1" {{Bug|34545#c162}}. Zum Testen drücken Sie {{keypress|e}} im Startmenü. Für eine bestehende Änderung schauen Sie [[Wie_man_Kerneloptionen_einstellt-de|hier]]. −* Wenn Kernel -devel Dateien von anderen Paketen benötigt werden holen sich unsere Werkzeuge die neuste 6.6.x Version, {{Bug|34973}}. Es ist OK diese zusätzlich zu haben, vergewissern Sie sich jedoch, dass Sie immer die -devel Dateien für Ihren 6.18 Kernel händisch, zusätzlich, installieren.+* Das WLAN Modul boradcom-wl wird nicht richtig, während der Durchführung, erstellt {{Bug|34975}}. Workaround ist, einen anderen Treiber auszuwählen - schauen Sie sich hierzu den Trick in {{Bug|31473}} an.  +* Wenn Kernel -devel Dateien von anderen Paketen benötigt werden holen sich unsere Werkzeuge die neuste 6.6.x Version, {{Bug|34952}}. Es ist OK diese zusätzlich zu haben, vergewissern Sie sich jedoch, dass Sie immer die -devel Dateien für Ihren 6.18 Kernel händisch, zusätzlich, installieren.  * User-space Werkzeuge werden vorbereitet {{Bug|34973}}. Normale Anwender müssen auf diese nicht warten. * User-space Werkzeuge werden vorbereitet {{Bug|34973}}. Normale Anwender müssen auf diese nicht warten.    Line 110: Line 111:  ** ''(kernel-stablenew -> 6.15.7 (x86_64, nur Desktop) - diese Serie wurde, für kernel-stable-testing, verworfen.)'' ** ''(kernel-stablenew -> 6.15.7 (x86_64, nur Desktop) - diese Serie wurde, für kernel-stable-testing, verworfen.)''  * kernel-stable -> 6.16.12 (x86_64, nur Desktop) * kernel-stable -> 6.16.12 (x86_64, nur Desktop) −* kernel -> '''6.12.63''' und '''6.18.4''' (alle Architekturen, alle Arten) ''Möglicherweise verwerfen wir 6.12.''+* kernel -> '''6.12.63''' und '''6.18.6''' (alle Architekturen, alle Arten) ''Möglicherweise verwerfen wir 6.12.''  * kernel-lts -> 6.6.100 (alle Architekturen, alle Arten) * kernel-lts -> 6.6.100 (alle Architekturen, alle Arten) Psyca

← Older revision Revision as of 21:00, 24 January 2026 Line 25: Line 25:  | 18.01.2026 | 18.01.2026  | Entwickler, Paketersteller | Entwickler, Paketersteller −| 19.01.2026+| 20.01.2026  |- |-  | '''Beta''' | '''Beta''' Psyca

‎Freeze push request: Freeze move

← Older revision Revision as of 00:38, 24 January 2026 Line 9: Line 9:  == Freeze push request == == Freeze push request ==    −If a developer feels the benefits of having a new version during a freeze overcomes the risks, he/she can send a request including "freeze push" in the subject to the dev@ list including a rationale. One of the [https://people.mageia.org/g/mga-release_managers.html release managers] will evaluate the request and if it seems valid, will perform the push.+If a developer feels the benefits of having a new version during a freeze overcomes the risks, he/she can send a request including "Freeze push" (or "Freeze move", as appropriate) in the subject to the dev@ list including a rationale. One of the [https://people.mageia.org/g/mga-release_managers.html release managers] will evaluate the request and if it seems valid, will perform the push.     The release manager has to issue : <code>mgarepo submit pkg</code> to have it built on our infrastructure. The release manager has to issue : <code>mgarepo submit pkg</code> to have it built on our infrastructure.    −If the packager already built the package in ''updates_testing'' (since that media is still open for building during a freeze), then the release manager must move it to ''release'' rather than rebuilding it there using the appropriate procedure in [[SOP Moving RPMs]].+If the packager has already built the package in ''updates_testing'' (since that media is still open for building during a version freeze), then the release manager must move it to ''release'' rather than rebuilding it there using the appropriate procedure in [[SOP Moving RPMs]].     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

‎Backport incompatibilities: Bug number correction

← Older revision Revision as of 23:36, 23 January 2026 Line 99: Line 99:  * wifi broadcom-wl module is not built correctly {{Bug|34975}}, in progress. Workaround is another driver, note the trick to select it {{Bug|31473}}. * wifi broadcom-wl module is not built correctly {{Bug|34975}}, in progress. Workaround is another driver, note the trick to select it {{Bug|31473}}.  * Where kernel -devel- files are needed by other packages, our tools seem to pull in latest 6.6.x version, {{Bug|34973}}. It is OK to have that extra, just you make sure to always manually install the -devel- file for your 6.18 kernel you install. * Where kernel -devel- files are needed by other packages, our tools seem to pull in latest 6.6.x version, {{Bug|34973}}. It is OK to have that extra, just you make sure to always manually install the -devel- file for your 6.18 kernel you install. −* User-space tools are in progress {{Bug|34973}}. Normal users do not need to wait for them.+* User-space tools are in progress {{Bug|34952}}. Normal users do not need to wait for them.     == Kernel series in Cauldron == == Kernel series in Cauldron == Morgano

‎Request Verification: Mention dkim verification

← Older revision Revision as of 22:06, 23 January 2026 Line 7: Line 7:  Each request must be verified to ensure that the user request is valid. We don't want random people taking over someone else's account. Here are some methods: Each request must be verified to ensure that the user request is valid. We don't want random people taking over someone else's account. Here are some methods:    −* Have the user open a formal request in Bugzilla (in the Accounts) section. If the user is still able to log in to Bugzilla, this is the most straightforward way as you can check the Bugzilla account that opened the bug. Take the e-mail address shown under '''Reported:''' and look it up under by running the following on a Mageia server:+* Have the user open a formal request in Bugzilla (in the ''Accounts'') section. If the user is still able to log in to Bugzilla, this is the most straightforward way as you can check the Bugzilla account that opened the bug. Take the e-mail address shown under '''Reported:''' and look it up under by running the following on a Mageia server:  <pre> <pre>  ldapsearch -H ldaps://ldap.mageia.org -b ou=People,dc=mageia,dc=org -D uid=$USER,ou=People,dc=mageia,dc=org -W '(mail=REQUESTER@E-MAIL)' ldapsearch -H ldaps://ldap.mageia.org -b ou=People,dc=mageia,dc=org -D uid=$USER,ou=People,dc=mageia,dc=org -W '(mail=REQUESTER@E-MAIL)' Line 14: Line 14:     * If the user isn't able to log in to Bugzilla but has an SSH key on file, you can use that to authenticate him/her. If the account holder is a packager, he/she can prove identity by making a specific requested change to an svn or git file. * If the user isn't able to log in to Bugzilla but has an SSH key on file, you can use that to authenticate him/her. If the account holder is a packager, he/she can prove identity by making a specific requested change to an svn or git file.  +  +* If the e-mail address tied to the user's account is from a well-known and secure mail provider that signs its messages with DKIM, you may verify the request by checking the DKIM signature of an e-mail from the user. If your mail client doesn't already check DKIM signatures, you can use a program like dkimverify (from python3-dkimpy).     == Update E-mail == == Update E-mail == Danf

‎Requirements: re-add the link to "Getting to write quickly"

← Older revision Revision as of 13:51, 23 January 2026 Line 15: Line 15:  If you aren't coming from this page [https://wiki.mageia.org/en/Documentation_team https://wiki.mageia.org/en/Documentation_team], have a look on it. You will learn how to join the Doc team and how to subscribe the doc-discuss mailing list. It is the place to be to have all the needed information about works in progress. If you aren't coming from this page [https://wiki.mageia.org/en/Documentation_team https://wiki.mageia.org/en/Documentation_team], have a look on it. You will learn how to join the Doc team and how to subscribe the doc-discuss mailing list. It is the place to be to have all the needed information about works in progress.    −Mageia documentation is written with Calenco. See [https://publish.calenco.com/Calenco/en/780251e6-0bc8-4597-8cac-202917f5c77d-1621626492/index.html the Calenco Documentation] to find out how it works.+Mageia documentation is written with Calenco. See [https://publish.calenco.com/Calenco/en/780251e6-0bc8-4597-8cac-202917f5c77d-1621626492/index.html the Calenco Documentation] to find out how it works. There is also a very short [https://www.calenco.com/en/Documentation/Getting-to-write-quickly.html quickstarter] available.     === Calenco access === === Calenco access === Marja