Lector de Feeds

‎Whiteboard:: Remove strings that already became keywords for Mageia 9 and later

← Older revision Revision as of 11:16, 10 December 2025 (4 intermediate revisions by the same user not shown)Line 93: Line 93:  === Thirdly, is the bug filed on a supported release? === === Thirdly, is the bug filed on a supported release? ===    −If the Mageia release on which the bug is filed is no longer supported, add the '''NEEDINFO''' keyword and ask the reporter for testing if it's still valid with the latest cauldron or any still supported products.+If the Mageia release on which the bug is filed is no longer supported, set the report to the "NEEDINFO" status and ask the reporter for testing if it's still valid with the latest cauldron or any still supported products.  Ping him if he doesn't reply within two weeks. If he doesn't reply within another two weeks, you can set it to the '''RESOLVED OLD''' resolution with a comment explaining the reason. This doesn't apply to enhancement requests as most of them should be set to '''Cauldron''' version (modify version field if needed). Ping him if he doesn't reply within two weeks. If he doesn't reply within another two weeks, you can set it to the '''RESOLVED OLD''' resolution with a comment explaining the reason. This doesn't apply to enhancement requests as most of them should be set to '''Cauldron''' version (modify version field if needed).    Line 111: Line 111:  A very good way to check whether all necessary information has been provided is to see whether you can reproduce the issue yourself using the information provided in the bug report. Triage team members are advised to keep copies of all currently supported Mageia releases available to help with this. You may want to consider using VirtualBox, VMware, qemu... etc for this purpose. A very good way to check whether all necessary information has been provided is to see whether you can reproduce the issue yourself using the information provided in the bug report. Triage team members are advised to keep copies of all currently supported Mageia releases available to help with this. You may want to consider using VirtualBox, VMware, qemu... etc for this purpose.    −If sufficient information has not yet been provided, you should add the '''NEEDINFO''' keyword to the bug, and add a comment explaining to the reporter what further information is required and - if necessary - how to obtain it. Ping him if he doesn't reply within two weeks. If he still doesn't reply within another two weeks, you can set it to the '''RESOLVED INVALID''' resolution with a comment explaining the reason and, ideally, inviting the reporter to reopen the bug report when he supplies the needed information.+If sufficient information has not yet been provided, you should add the '''NEEDINFO''' status to the bug, and add a comment explaining to the reporter what further information is required and - if necessary - how to obtain it. Ping him if he doesn't reply within two weeks. If he still doesn't reply within another two weeks, you can set it to the '''RESOLVED INVALID''' resolution with a comment explaining the reason and, ideally, inviting the reporter to reopen the bug report when he supplies the needed information.  +   +===Commands that give much information about a user's system===  +   +{{command|lspcidrake -v}}  +   +In Mageia 9: {{command|inxi -F}}  +In Mageia 10 and later: {{command|inxi -e}}     == Special cases of specific information required == == Special cases of specific information required == Line 384: Line 391:     see [[Becoming a Mageia Packager]] see [[Becoming a Mageia Packager]]  +  +== Keywords ==  +  +Current keywords can be found [https://bugs.mageia.org/describekeywords.cgi here]  +At least some of our Whitboard strings should become keywords, see also [https://bugs.mageia.org/show_bug.cgi?id=19637 bug 19637]  +     == Whiteboard: == == Whiteboard: ==    −* FOR_ERRATA7 : needs to be added to the [[Mageia 7 Errata]] page.+  −* IN_ERRATA7 : has been added to the [[Mageia 7 Errata]] page.  −* FOR_RELNOTES7: to be added to the [[Mageia 7 Release Notes]] page.  −* IN_RELNOTES7: has been added to the [[Mageia 7 Release Notes]] page.  −* FOR_ERRATA6 : needs to be added to the [[Mageia 6 Errata]] page.  −* IN_ERRATA6 : has been added to the [[Mageia 6 Errata]] page.   * check : for bug to close * check : for bug to close  * cauldron : for package requests, when the package already exists in cauldron - also for when the cauldron version of a package is requested to be backported for stable * cauldron : for package requests, when the package already exists in cauldron - also for when the cauldron version of a package is requested to be backported for stable Marja

← Older revision Revision as of 08:31, 10 December 2025 Line 84: Line 84:     [[User:Nikos5446]] [[User:Nikos5446]]  +  +----  +[[User:Morgano|morgano]] ([[User talk:Morgano|talk]]) 08:31, 10 December 2025 (UTC)  +  +Thank you for the tip Nikos.  +  +But are you sure it really is noticeably faster?  It need to load the program from the USB anyway.  +  +I guess(have not tested) you need more than 2GB RAM for this method to work nicely, especially with a non minimalistic DE (think Plasma) and hungry program like Firefox?  +  +BTW, if you want to update or improve the page, please go ahead :)  I do not have much time anymore.  Just make sure you test things first :)  +  +Also, by now, I think we now can remove the stuff that is elder than Mageia 8, like suggested by sturmvogel earlier, see top post above. Morgano

firejail

← Older revision Revision as of 08:16, 10 December 2025 Line 72: Line 72:     One big advantage with Live is that if the updates or settings foul up (been there), (i.e by glitchy connector) you can boot without the persistence. One big advantage with Live is that if the updates or settings foul up (been there), (i.e by glitchy connector) you can boot without the persistence.  +  +----  +  +We could add the following in the "Tips" section:  +  +- 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.  +  Example commands:  + "firejail --private falkon"  + "firejail --private firefox"  + "firejail --private --appimage ~/apps/librewolf/LibreWolf.x86_64.AppImage"  +  +[[User:Nikos5446]] Nikos5446

‎For Qa team:

← Older revision Revision as of 13:20, 9 December 2025 Line 95: Line 95:  * Aussie_matt - Xboxboy - xboxboy dot mageia at gmail dot com * Aussie_matt - Xboxboy - xboxboy dot mageia at gmail dot com    −* papoteur - Yves Brungard - yves.brungard_mageia at gadz dotorg+* papoteur - Yves Brungard - yves.brungard+mageia at gadz dotorg     * tonyb - Tony Blackwell - tablackwell at bigpond dot com * tonyb - Tony Blackwell - tablackwell at bigpond dot com Papoteur

Adding nikos5446

← Older revision Revision as of 12:15, 9 December 2025 Line 121: Line 121:     User:mvt7 User:mvt7  +  +User:nikos5446     User:nmalykh   User:nmalykh   Marja

Publication date: 08 Dec 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-66293 Description LIBPNG has an out-of-bounds read in png_image_read_composite. (CVE-2025-66293) References

• https://bugs.mageia.org/show_bug.cgi?id=34799
• https://www.openwall.com/lists/oss-security/2025/12/03/5
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-66293

SRPMS 9/core

• libpng-1.6.38-1.2.mga9

Publication date: 08 Dec 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-55753 , CVE-2025-58098 , CVE-2025-65082 , CVE-2025-66200 Description Apache HTTP Server: mod_md (ACME), unintended retry intervals. (CVE-2025-55753) Apache HTTP Server 2.4.65 and earlier with Server Side Includes (SSI) enabled and mod_cgid (but not mod_cgi) passes the shell-escaped query string to #exec cmd="..." directives. (CVE-2025-58098) Apache HTTP Server: CGI environment variable override. (CVE-2025-65082) Apache HTTP Server: mod_userdir+suexec bypass via AllowOverride FileInfo. (CVE-2025-66200) References

• https://bugs.mageia.org/show_bug.cgi?id=34803
• https://www.openwall.com/lists/oss-security/2025/12/04/4
• https://www.openwall.com/lists/oss-security/2025/12/04/5
• https://www.openwall.com/lists/oss-security/2025/12/04/7
• https://www.openwall.com/lists/oss-security/2025/12/04/8
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-55753
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-58098
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-65082
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-66200

SRPMS 9/core

• apache-2.4.66-1.mga9