Lector de Feeds
How to write and translate Mageia doc
Requirements: try to add better link to the Calenco Documentation. A shorter link would be better, but I don’t manage to find a working one on my phone
← Older revision Revision as of 10:20, 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 the Documentation drop-down menu list in [https://www.calenco.com/en/index.html Calenco] 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. === Calenco access === === Calenco access === Marja
Categorías: Wiki de Mageia
Kernel flavours
Backport incompatibilities
← Older revision Revision as of 10:07, 23 January 2026 (One intermediate revision by the same user not shown)Line 95: Line 95: Backport kernels may have problems with elder hardware, other software, or tools. Known problems: Backport kernels may have problems with elder hardware, other software, or tools. Known problems: * GPU Kabini Radeon HD 8210 (and probably similar) need the following parameters added to kernel boot command line: "radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1" {{Bug|34545#c162}}. To test, press "e" at boot menu. For persistent change see [[How_to_set_up_kernel_options|here]]. * GPU Kabini Radeon HD 8210 (and probably similar) need the following parameters added to kernel boot command line: "radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1" {{Bug|34545#c162}}. To test, press "e" at boot menu. For persistent change see [[How_to_set_up_kernel_options|here]]. +* 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|34973}}. Normal users do not need to wait for them. Morgano
Categorías: Wiki de Mageia
How to write and translate Mageia doc
Getting credentials
← Older revision Revision as of 08:17, 23 January 2026 Line 32: Line 32: then you can ask for credentials (a username and password) to access the Mageia Calenco repository. <br/><br/> then you can ask for credentials (a username and password) to access the Mageia Calenco repository. <br/><br/> −The simplest way to get them is to send an e-mail to papteur at the address <br/>+The simplest way to get them is to send an e-mail to Papoteur at the address <br/> "papoteur At mageia DOT org" "papoteur At mageia DOT org" This e-mail must include the following information: This e-mail must include the following information: Papoteur
Categorías: Wiki de Mageia
MGASA-2026-0016 - Updated avahi packages fix security vulnerabilities
Publication date: 23 Jan 2026
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-68276 , CVE-2025-68468 , CVE-2025-68471 Description Avahi has a reachable assertion in avahi_wide_area_scan_cache. (CVE-2025-68276) Avahi has a reachable assertion in lookup_multicast_callback. (CVE-2025-68468) Avahi has a reachable assertion in lookup_start. (CVE-2025-68471) References
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-68276 , CVE-2025-68468 , CVE-2025-68471 Description Avahi has a reachable assertion in avahi_wide_area_scan_cache. (CVE-2025-68276) Avahi has a reachable assertion in lookup_multicast_callback. (CVE-2025-68468) Avahi has a reachable assertion in lookup_start. (CVE-2025-68471) References
- https://bugs.mageia.org/show_bug.cgi?id=34887
- https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/DR2CTF5XR6GVX3JYIAAO3ULJNUZDGBVS/
- https://ubuntu.com/security/notices/USN-7967-1
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-68276
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-68468
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-68471
- avahi-0.8-10.3.mga9
Categorías: Actualizaciones de Seguridad
MGASA-2026-0015 - Updated harfbuzz packages fix security vulnerability
Publication date: 23 Jan 2026
Type: security
Affected Mageia releases : 9
CVE: CVE-2026-22693 Description Null Pointer Dereference in SubtableUnicodesCache::create leading to DoS. (CVE-2026-22693) References
Type: security
Affected Mageia releases : 9
CVE: CVE-2026-22693 Description Null Pointer Dereference in SubtableUnicodesCache::create leading to DoS. (CVE-2026-22693) References
- https://bugs.mageia.org/show_bug.cgi?id=35042
- https://www.openwall.com/lists/oss-security/2026/01/11/1
- https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/QJUDZGUEVHTL26NPJUIGPHUOUKLUMCFB/
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-22693
- harfbuzz-7.0.1-1.2.mga9
Categorías: Actualizaciones de Seguridad
Category:Sysadmin
Add Sysadmin Tasks link
← Older revision Revision as of 23:23, 22 January 2026 Line 6: Line 6: You will find all kinds of documentation about infrastructure Mageia here: You will find all kinds of documentation about infrastructure Mageia here: * [[Sysadmin Team]] * [[Sysadmin Team]] +* [[Sysadmin Tasks]] * [[:Category:SysadminTODO|Sysadmin TODO list]] * [[:Category:SysadminTODO|Sysadmin TODO list]] * [http://gitweb.mageia.org/infrastructure/puppet/plain/deployment/main_mirror/files/mirror/mirror.readme Mirror readme] * [http://gitweb.mageia.org/infrastructure/puppet/plain/deployment/main_mirror/files/mirror/mirror.readme Mirror readme] Danf
Categorías: Wiki de Mageia
Sysadmin Team
Useful pages: Point to Sysadmin_Tasks page rather than duplicating some links here
← Older revision Revision as of 23:22, 22 January 2026 Line 37: Line 37: == Useful pages == == Useful pages == −* [[Pushing_updates|Pushing package updates]]+* [[Sysadmin Tasks]] lists the standard operating procedures and tasks required of sysadmin −* [[SOP_Sysadmin_access_revocation|Removing Sysadm access]] −* [[SOP_Certificate_update|Updating SSL Certificates]] −* [[SOP_Version_and_Release_freeze|Controlling version/release freeze]] −* [[SOP_Rename_user|Renaming users]] Danf
Categorías: Wiki de Mageia
SOP Freeze push
Freeze push request: move procedure
← Older revision Revision as of 23:18, 22 January 2026 Line 12: Line 12: 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]]. + [[Category:Sysadmin]] [[Category:Sysadmin]] Danf
Categorías: Wiki de Mageia
Sysadmin Tasks
Move freeze push to package building section
← Older revision Revision as of 23:12, 22 January 2026 Line 34: Line 34: * [[SOP Moving RPMs]] from one media to another on Cauldron that were submitted to the wrong one * [[SOP Moving RPMs]] from one media to another on Cauldron that were submitted to the wrong one * [[SOP_Moving_RPMs#Restoring_old_RPMs|Restoring RPMs]] that were improperly removed from a media (due to bad obsoletes or bad upgrade) * [[SOP_Moving_RPMs#Restoring_old_RPMs|Restoring RPMs]] that were improperly removed from a media (due to bad obsoletes or bad upgrade) +* [[SOP Freeze push]] (submit or move a package on request of a developer during release freeze) * [[SOP Killing builds]] on the build system that are taking too long or have hung * [[SOP Killing builds]] on the build system that are taking too long or have hung * [[SOP Restarting builds]] for one architecture that failed due to a temporary issue * [[SOP Restarting builds]] for one architecture that failed due to a temporary issue Line 46: Line 47: * [[Mageia_Release_Countdown|Releasing a new Mageia version checklist]] * [[Mageia_Release_Countdown|Releasing a new Mageia version checklist]] * [[Sysadmin New Release]] * [[Sysadmin New Release]] −* [[SOP Freeze push]] (submit or move a package on request of a developer during release freeze) * Trigger full distribution rebuild of packages * Trigger full distribution rebuild of packages * [[Pushing isos]] (after a new Mageia release) * [[Pushing isos]] (after a new Mageia release) Danf
Categorías: Wiki de Mageia
SOP Freeze push
Freeze push request
← Older revision Revision as of 21:47, 22 January 2026 Line 11: Line 11: 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" 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. [[Category:Sysadmin]] [[Category:Sysadmin]] Bcornec
Categorías: Wiki de Mageia




