Lector de Feeds

‎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

‎Kernel series in Cauldron

← Older revision Revision as of 11:16, 23 January 2026 (One intermediate revision by the same user not shown)Line 70: Line 70:  It happens that a kernel get backported to previous Mageia release, i.e from Cauldron to latest official Mageia. It happens that a kernel get backported to previous Mageia release, i.e from Cauldron to latest official Mageia.    −'''In Mageia 9, ''work is in progress'' '''+'''In Mageia 9'''<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>  +You also find kernel 6.12.60 for all architectures in desktop flavour - note it is old security wise now.<br>    −Kernel 6.12.60+ (working but old security wise now) and 6.18.4+ are provided in Backport repository for all architectures '''in desktop flavour, and for 6.18 also in server flavour''' ''- no other flavour.''<br>  −''('''In progress''' {{Bug|34962}} January 2026; kernels are currently in backport_testing repo)''<br>  −'''<br>   Only two packages to install per kernel''' (from Backport): <br> Only two packages to install per kernel''' (from Backport): <br>  kernel-stable-desktop-6.12... / kernel-stable-testing-desktop-6.18... / kernel-stable-testing-server-6.18 <br> kernel-stable-desktop-6.12... / kernel-stable-testing-desktop-6.18... / kernel-stable-testing-server-6.18 <br> Line 118: Line 118:  ** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)'' ** ''(kernel-stablenew -> 6.15.7 (x86_64, desktop only) - this series gets obsoleted in favour of kernel-stable-testing.)''  * kernel-stable -> 6.16.12 (x86_64, desktop only) * kernel-stable -> 6.16.12 (x86_64, desktop only) −* kernel -> '''6.12.63''' and '''6.18.4''' (all arches, all flavours) ''We might drop 6.12.''+* kernel -> '''6.12.63''' and '''6.18.6''' (all arches, all flavours) ''We might drop 6.12.''  * kernel-lts -> 6.6.100 (all arches, all flavours) * kernel-lts -> 6.6.100 (all arches, all flavours) Morgano

‎Root password: mga9

← Older revision Revision as of 11:11, 23 January 2026 (One intermediate revision by the same user not shown)Line 29: Line 29:  Let's make a Mageia container directory: Let's make a Mageia container directory:    −{{pre|mkdir /container/mageia6}}  +{{pre|mkdir /container/mageia9}}       Initialize the rpm database for Mageia: Initialize the rpm database for Mageia:    −{{pre|rpm --rebuilddb --root{{=}}/container/mageia6}}+{{pre|rpm --rebuilddb --root{{=}}/container/mageia9}}     Install some base rpm's. Installing these ensures that you can install Install some base rpm's. Installing these ensures that you can install −the packages for the Mageia 6 release.  +the packages for the Mageia 9 release.    Officially you can skip this step, but it makes the configuration somewhat Officially you can skip this step, but it makes the configuration somewhat  easier. You can ignore warnings. easier. You can ignore warnings.    −{{pre|<nowiki>rpm --root=/container/mageia6/ --nodeps -ivh \+{{pre|<nowiki>rpm --root=/container/mageia9/ --nodeps -ivh \ −http://free.nchc.org.tw/mageia/distrib/6/x86_64/media/core/release/mageia-release-Default-6-4.mga6.x86_64.rpm+http://free.nchc.org.tw/mageia/distrib/9/x86_64/media/core/release/mageia-release-Default-9-2.mga9.x86_64.rpm    −rpm --root=/container/mageia6/ --nodeps -ivh \+rpm --root=/container/mageia9/ --nodeps -ivh \ −http://free.nchc.org.tw/mageia/distrib/6/x86_64/media/core/release/mageia-release-common-6-4.mga6.x86_64.rpm+http://free.nchc.org.tw/mageia/distrib/9/x86_64/media/core/release/mageia-release-common-9-2.mga9.x86_64.rpm    −rpm --root=/container/mageia6/ --nodeps -ivh \+rpm --root=/container/mageia9/ --nodeps -ivh \ −http://free.nchc.org.tw/mageia/distrib/6/x86_64/media/core/release/lsb-release-2.0-52.mga6.noarch.rpm</nowiki>}}+http://free.nchc.org.tw/mageia/distrib/9/x86_64/media/core/release/lsb-release-3.1-5.mga9.noarch.rpm</nowiki>}}     Configure the Mageia repositories: Configure the Mageia repositories:    −{{pre|<nowiki>urpmi.addmedia --distrib http://free.nchc.org.tw/mageia/distrib/6/x86_64/ --urpmi-root /container/mageia6</nowiki>}}+{{pre|<nowiki>urpmi.addmedia --distrib http://free.nchc.org.tw/mageia/distrib/9/x86_64/ --urpmi-root /container/mageia9</nowiki>}}     Of course you can use other mirrors! Of course you can use other mirrors! Line 57: Line 57:  Now you can start a minimal installation: Now you can start a minimal installation:    −{{pre|<nowiki>urpmi basesystem-minimal urpmi locales locales-en systemd --auto --no-recommends --urpmi-root /container/mageia6/ --root /container/mageia6/</nowiki>}}+{{pre|<nowiki>urpmi basesystem-minimal urpmi locales locales-en systemd --auto --no-recommends --urpmi-root /container/mageia9/ --root /container/mageia9/</nowiki>}}     === Root password === === Root password === Line 64: Line 64:  Therefore you need to change your root filesystem into the container. Therefore you need to change your root filesystem into the container.    −{{pre|chroot /container/mageia6}}+{{pre|chroot /container/mageia9}}     Now you can set the root password: Now you can set the root password: Geex

‎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

‎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

‎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

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

‎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

‎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

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

‎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

‎Getting credentials: papoteur (the Documentation Team leader) can give credentials

← Older revision Revision as of 19:42, 22 January 2026 (One intermediate revision by the same user not shown)Line 24: Line 24:     If that isn't a problem and if ''you'' have done all of the following: If that isn't a problem and if ''you'' have done all of the following: −# successfully translated some of our .xml files by yourself after which they were uploaded to Calenco+<!--# successfully translated some of our .xml files by yourself after which they were uploaded to Calenco −## someone with Calenco access will download the needed .xml files for you, it is impossible to do that without credentials+## someone with Calenco access will download the needed .xml files for you, it is impossible to do that without credentials-->  # read the following: # read the following:  ## [[How to write and translate Mageia doc#Translate an English doc| Translate an English document]] (this page) ## [[How to write and translate Mageia doc#Translate an English doc| Translate an English document]] (this page) 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 John at the address <br/>+The simplest way to get them is to send an e-mail to papteur at the address <br/> −"john At neodoc DOT biz" '''with''' a copy to <br/>+"papoteur At mageia DOT org" −"marja11 AT xs4all DOT nl" <br/>  −("AT" to be replaced by @ and DOT by ".").<br/><br/>   This e-mail must include the following information: This e-mail must include the following information:  * Your full name (given name + surname) * Your full name (given name + surname) Marja