Wiki Mageia

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

Typo

← Older revision Revision as of 13:38, 23 January 2026 Line 11: Line 11:  and can be used to test and develop software,   and can be used to test and develop software,    or you can use it to create packages. or you can use it to create packages. −You can think of systemd-nspawn as a sort of chroot on steriods.+You can think of systemd-nspawn as a sort of chroot on steroids.     This document is meant for packagers, developers, and everyone that wants to This document is meant for packagers, developers, and everyone that wants to Papoteur

‎mkosi: install urpmi if you prefer

← Older revision Revision as of 12:57, 23 January 2026 (One intermediate revision by the same user not shown)Line 145: Line 145:  mkosi -d mageia -r 9 -m https://geex.ovh/ --architecture=x86_64 -t directory -o /container/mga9 build mkosi -d mageia -r 9 -m https://geex.ovh/ --architecture=x86_64 -t directory -o /container/mga9 build  chroot /container/mga9 chroot /container/mga9 −passwd+passwd</nowiki>}} −exit+   +set your password  +   +{{pre|<nowiki>exit  systemd-nspawn --boot --directory=/container/mga9</nowiki>}} systemd-nspawn --boot --directory=/container/mga9</nowiki>}}  +  +Login in (as root).  +  +Do some stuff in the container, for example, install urpmi if you prefer.  +  +{{pre|<nowiki>dnf in urpmi locales-en</nowiki>}}  +  +Type poweroff when done. Geex

‎Backport kernels

← Older revision Revision as of 12:15, 23 January 2026 Line 72: Line 72:  '''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+ are 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 89: Line 89:     '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle backport kernels by default, 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 (for all backport flavours):<br>   '''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle backport kernels by default, 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 (for all backport flavours):<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<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>   −*For i586 systems also+kernel-stable-testing-desktop586<br> kernel-stable-testing-desktop586-devel <br> −kernel-stable-testing-desktop586<br> kernel-stable-testing-desktop586-devel+:''(The three first only needed for 6.12, the other for 6.18 where the two last are only needed for i585 systems.)''     === Backport incompatibilities === === Backport incompatibilities === Morgano

Creat image with mkosi

← Older revision Revision as of 12:07, 23 January 2026 Line 137: Line 137:  or or  {{pre|<nowiki>machinectl stop mageia9</nowiki>}} {{pre|<nowiki>machinectl stop mageia9</nowiki>}}  +  +=== mkosi ===  +  +An alternative is to create the chroot with mkosi (it uses dnf to install).  +  +{{pre|<nowiki>urpmi mkosi dnf  +mkosi -d mageia -r 9 -m https://geex.ovh/ --architecture=x86_64 -t directory -o /container/mga9 build  +chroot /container/mga9  +passwd  +exit  +systemd-nspawn --boot --directory=/container/mga9</nowiki>}} Geex

‎Backport kernels

← Older revision Revision as of 11:50, 23 January 2026 Line 73: Line 73:  ''{{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+ are provided in Backport repository for all architectures in desktop and server flavour, plus desktop586.<br> Kernel 6.18.4+ are 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 - note it is old security wise now.<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>     Only two packages to install per kernel''' (from Backport): <br> Only two packages to install per kernel''' (from Backport): <br> Line 80: Line 80:  - Also note you need the suggested corresponding -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.) - Also note you need the suggested corresponding -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, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, to not break compatibility with non-backport kernels, so you can reboot between 6.6 and backport kernels without needing to change installed packages.''+'''Keep having latest non-backport''' lib64bpf1 & cpupower, and keep them updated.  ''- we do not backport lib64bpf1 and cpupower, in order not to break compatibility with non-backport kernels, so you can reboot between 6.6 and backport kernels without needing to change installed packages.''     '''Regarding kernel-*-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 - and using non backport kernel versions >= 6.6.105. '''Regarding kernel-*-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 - and using non backport kernel versions >= 6.6.105. Line 88: Line 88:  '''If running VirtualBox < 7.1.14,''' see {{Bug|34408#c7}}. '''If running VirtualBox < 7.1.14,''' see {{Bug|34408#c7}}.    −'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle backport kernels by default, 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 (for all backport versions):<br>  +'''Remove-Old-Kernels''', {{prog|rok}}, do currently not see nor handle backport kernels by default, 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 (for all backport flavours):<br>    kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source <br> kernel-stable-desktop <br> kernel-stable-desktop-devel <br> kernel-stable-source <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-desktop <br> kernel-stable-testing-desktop-devel <br> kernel-stable-testing-server <br> kernel-stable-testing-server-devel <br> kernel-stable-testing-source<br>  +*For i586 systems also  +kernel-stable-testing-desktop586<br> kernel-stable-testing-desktop586-devel     === Backport incompatibilities === === Backport incompatibilities === Morgano

‎machinectl: mga9

← Older revision Revision as of 11:26, 23 January 2026 (2 intermediate revisions by the same user not shown)Line 84: Line 84:  filesystem: filesystem:    −{{pre|<nowiki>systemd-nspawn --boot --directory=/container/mageia6</nowiki>}}+{{pre|<nowiki>systemd-nspawn --boot --directory=/container/mageia9</nowiki>}}    −Disable the network daemon:+Logout, and exit the container by pressing ctrl+] 3 times or Ctrl+D    −{{pre|<nowiki>chkconfig network off</nowiki>}}+If we want to access a network bridged with the host (the default is to use a veth device), we create a file named  +/etc/systemd/nspawn/mageia9.nspawn :    −Logout, and exit the container by pressing ctrl+] 3 times+{{pre|<nowiki>[Network]  +VirtualEthernet=no</nowiki>}}     === machinectl === === machinectl === Line 113: Line 115:  systemctl enable var-lib-machines.mount</nowiki>}} systemctl enable var-lib-machines.mount</nowiki>}}    −To show the Mageia6 'image', execute:+To show the Mageia9 'image', execute:     {{pre|<nowiki>machinectl list-images</nowiki>}} {{pre|<nowiki>machinectl list-images</nowiki>}} Line 119: Line 121:  Start the image: Start the image:    −{{pre|<nowiki>machinectl start mageia6</nowiki>}}+{{pre|<nowiki>machinectl start mageia9</nowiki>}}     To login: To login:    −{{pre|<nowiki>machinectl shell mageia6</nowiki>}}+{{pre|<nowiki>machinectl shell mageia9</nowiki>}}    −Exit the shell by pressing ctrl+] 3 times,+Exit the shell by pressing ctrl+] 3 times or Ctrl+D,  and view the status: and view the status:    −{{pre|<nowiki>machinectl status mageia6</nowiki>}}+{{pre|<nowiki>machinectl status mageia9</nowiki>}}     Now you can shutdown the container until next time you need it: Now you can shutdown the container until next time you need it:    −{{pre|<nowiki>machinectl poweroff mageia6</nowiki>}}+{{pre|<nowiki>machinectl poweroff mageia9</nowiki>}}  +or  +{{pre|<nowiki>machinectl stop mageia9</nowiki>}} Geex

‎Kernel series in Cauldron

← Older revision Revision as of 11:16, 23 January 2026 (One intermediate revision by the same user not shown)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, ''work is in progress'' '''+'''In Mageia 9'''<br>  +''{{Bug|34962}} January 2026 kernels are currently in backport_testing repo)''<br>  +Kernel 6.18.4+ are 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 - note it is old security wise now.<br>    −Kernel 6.12.60+ (working but old security wise now) and 6.18.4+ are provided in Backport repository for all architectures '''in desktop flavour, and for 6.18 also in server flavour''' ''- no other flavour.''<br>  −''('''In progress''' {{Bug|34962}} January 2026; kernels are currently in backport_testing repo)''<br>  −'''<br>   Only two packages to install per kernel''' (from Backport): <br> Only two packages to install per kernel''' (from 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 118: Line 118:  ** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)'' ** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)''  * kernel-stable -> 6.16.12 (x86_64, desktop only) * kernel-stable -> 6.16.12 (x86_64, desktop only) −* kernel -> '''6.12.63''' and '''6.18.4''' (all arches, all flavours) ''We might drop 6.12.''+* kernel -> '''6.12.63''' and '''6.18.6''' (all arches, all flavours) ''We might drop 6.12.''  * kernel-lts -> 6.6.100 (all arches, all flavours) * kernel-lts -> 6.6.100 (all arches, all flavours) Morgano