Lector de Feeds

‎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