Lector de Feeds
SOP Freeze push
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
Categorías: Wiki de Mageia
Kernel flavours
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
Categorías: Wiki de Mageia
SOP Change user e-mail
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
Categorías: Wiki de Mageia
How to write and translate Mageia doc
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
Categorías: Wiki de Mageia
Systemd-nspawn
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
Categorías: Wiki de Mageia
Systemd-nspawn
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
Categorías: Wiki de Mageia
Kernel flavours
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
Categorías: Wiki de Mageia
Systemd-nspawn
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
Categorías: Wiki de Mageia




