Lector de Feeds

‎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