Wiki de Mageia

Start page

New page

Please add any contact that you know of.

We should probably create a table for this.

Ibiblio: Don Sizemore - dls [AT] ibiblio [DOT] org
Princeton: Benjamin Rose - benrose [AT] math [DOT] princeton [DOT] edu Marja

Add lines about contacting "red" mirrors

← Older revision Revision as of 19:20, 26 October 2024 Line 6: Line 6:     [https://mirrors.mageia.org/ mirrors.mageia.org] [https://mirrors.mageia.org/ mirrors.mageia.org]  +  +There you can also see from which other mirror each mirror syncs.     The status of each of the mirrors can be seen on this page: The status of each of the mirrors can be seen on this page:     [https://mirrors.mageia.org/status mirrors.mageia.org/status] [https://mirrors.mageia.org/status mirrors.mageia.org/status]  +  +If all mirrors are red, then Mageia has a problem.  +If your preferred mirror is red, while other mirrors are green, then you preferred mirror has a problem. There are two possibilities:  +* The mirror it syncs from is red  +** If this doesn't get solved within reasonable time, then contact your preferred mirror and suggest they sync from a different mirror.  +* The mirror it syncs from is green  +** Then the problem originated in your preferred mirror, please contact the maintainers to make sure they are aware  +  +We are starting to gather contact data in [[Mirror Contacts]] Marja

added ircs channel mageia-next

← Older revision Revision as of 09:58, 26 October 2024 Line 28: Line 28:  * [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-vergadering] * [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-vergadering]     +* [ircs://irc.libera.chat:6697/#mageia-next #mageia-next] Praat over alles dat Mageia helpt aan een schitterende toekomst)  * Het #mageia-social channel (sociale kanaal) dat we hadden op Freenode, voor algemene gesprekken en voor Mageia gemeenschapsvorming, heet nu op Liberachat [ircs://irc.libera.chat:6697/#mageia-chat #mageia-chat]. * Het #mageia-social channel (sociale kanaal) dat we hadden op Freenode, voor algemene gesprekken en voor Mageia gemeenschapsvorming, heet nu op Liberachat [ircs://irc.libera.chat:6697/#mageia-chat #mageia-chat].    Hugomarc

‎To be merged, off-list reply to the association discussion: remove off-list

← Older revision Revision as of 08:51, 26 October 2024 (2 intermediate revisions by the same user not shown)Line 9: Line 9:  Every idea may be added. When brainstorming, there are no wrong or stupid ideas. That said, ideas that don't comply with our [https://www.mageia.org/en/about/code-of-conduct/ code of conduct], will be removed. Every idea may be added. When brainstorming, there are no wrong or stupid ideas. That said, ideas that don't comply with our [https://www.mageia.org/en/about/code-of-conduct/ code of conduct], will be removed.    −The intention is to sort the ideas by general topic (like whom to reach out to, or proposed changes to Mageia, or how to reach potential contributors) on this page, to make later reviewing them easier. Topics can be added when needed.}}+The intention is to sort the ideas by general topic (like whom to reach out to, or proposed changes to Mageia, or how to reach potential contributors) on this page, to make later reviewing them easier. Topics can be added when needed.  +   +You can also help brainstorming on '''[[Mageia IRC Channels Liberachat |IRC:]]''' [ircs://irc.libera.chat:6697/#mageia-next #mageia-next]}}     =Whom to reach out to= =Whom to reach out to= Line 200: Line 202:  The association should support these programs, including financially, meaning we need to have a campaign to get more funds for that. The renewal of HW would also benefit from that. The association should support these programs, including financially, meaning we need to have a campaign to get more funds for that. The renewal of HW would also benefit from that.    −=To be merged, off-list reply to the association discussion=+=To be merged, reply to the association discussion=  I remove all history, because I don't have the time to read everything, sorry. I remove all history, because I don't have the time to read everything, sorry.  I just want to add my point of view: I just want to add my point of view: Marja

‎Project-wide channels:: Add #mageia-next

← Older revision Revision as of 08:07, 26 October 2024 Line 25: Line 25:  * [ircs://irc.libera.chat:6697/#mageia-council #mageia-council] * [ircs://irc.libera.chat:6697/#mageia-council #mageia-council]  * [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-meeting] * [ircs://irc.libera.chat:6697/#mageia-meeting #mageia-meeting]  +* [ircs://irc.libera.chat:6697/#mageia-next #mageia-next] (Chat about anything that helps Mageia's bright future)     * The #mageia-social channel we had on Freenode, for General chat and Mageia community building, has become [ircs://irc.libera.chat:6697/#mageia-chat #mageia-chat] on Liberachat. * The #mageia-social channel we had on Freenode, for General chat and Mageia community building, has become [ircs://irc.libera.chat:6697/#mageia-chat #mageia-chat] on Liberachat. −  −      == Team specific: == == Team specific: == Marja

Update DaVinci Resolve to version 19.0.3

← Older revision Revision as of 19:38, 25 October 2024 Line 1: Line 1: −= How to install and use DaVinci Resolve 19.0.1 on Mageia Linux 9 =+= How to install and use DaVinci Resolve 19.0.3 on Mageia Linux 9 =     I've spent the past few years using kdenlive to edit my videos and decided it was time to up my game. In comes [https://www.blackmagicdesign.com/products/davinciresolve/ DaVinci Resolve]. I've spent the past few years using kdenlive to edit my videos and decided it was time to up my game. In comes [https://www.blackmagicdesign.com/products/davinciresolve/ DaVinci Resolve]. Line 11: Line 11:  # [https://www.blackmagicdesign.com/products/davinciresolve/ Download DaVinci Resolve] # [https://www.blackmagicdesign.com/products/davinciresolve/ Download DaVinci Resolve]  # Unzip the file # Unzip the file −## <code>unzip DaVinci_Resolve_19.0.1_Linux.zip</code>+## <code>unzip DaVinci_Resolve_19.0.3_Linux.zip</code> −# This gives us the binary installation file - '''DaVinci_Resolve_19.0.1_Linux.run'''+# This gives us the binary installation file - '''DaVinci_Resolve_19.0.3_Linux.run'''  ## Make it executable ## Make it executable −## <code>chmod 755 DaVinci_Resolve_19.0.1_Linux.run</code><br />+## <code>chmod 755 DaVinci_Resolve_19.0.3_Linux.run</code><br />  # To install this file, we have to skip some checks. # To install this file, we have to skip some checks. −## <code>sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_19.0.1_Linux.run</code>+## <code>sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_19.0.3_Linux.run</code>  # Follow the installation guide and click '''Finish''' when it appears. # Follow the installation guide and click '''Finish''' when it appears.  # Before launching DaVinci Resolve, do the following. This way, Resolve uses the system libraries instead.<br /> # Before launching DaVinci Resolve, do the following. This way, Resolve uses the system libraries instead.<br /> Kekepower

‎Communication: Add off-list association reply

← Older revision Revision as of 16:00, 25 October 2024 Line 199: Line 199:  We should ask existing users to recruit at least 1 new user during the year. Meaning we could double our community, and thus generating more possibilities to have more contributors. We should ask existing users to recruit at least 1 new user during the year. Meaning we could double our community, and thus generating more possibilities to have more contributors.  The association should support these programs, including financially, meaning we need to have a campaign to get more funds for that. The renewal of HW would also benefit from that. The association should support these programs, including financially, meaning we need to have a campaign to get more funds for that. The renewal of HW would also benefit from that.  +  +=To be merged, off-list reply to the association discussion=  +I remove all history, because I don't have the time to read everything, sorry.  +I just want to add my point of view:  +  +we left the field. We are not organized (meetings, elections) except great QA  +team which is rigoureous. I'm impressed.  +We are not publishing our presences in all event (many thanks to DTux who  +subscrib us everywhere in France for years).  +We were rejected from FOSDEM once or twice, but we did not retried.  +From the french forum, I only know 2 peoples (thank you Guygoye and Spank) who  +regularly participate on local install-party regularly.  +  +Don't questionnize too much, at work, with many IT developers, no one know  +Mageia. We are not on radars, people don't know us.  +  +What I would do:  +- split atelier in two. Atelier keep producing artwork, and respond to any  +design query. Having a dedicated Communication team, that subscibe M.Org to  +events, ask Atelier to produce XYZ goody and with their dedicated budget, buy  +and spread goodies.  +If I know someone from my city willing to spend one evening a week, I will ask  +a local to  do install party.  +  +Good night everyone, work is calling me,     =Also to be merged, possible extra replies in the forums= =Also to be merged, possible extra replies in the forums= Marja

Add some more config notes

← Older revision Revision as of 15:48, 24 October 2024 Line 2: Line 2:     Sympa is storing its parameters in a sort of "file database" of it's own in  /var/blah/sympa/<listname>/config The data files look like flat text configuration files with a weird organization... json or yaml would be so much clear and easy to manage. When we use the Sympa administration UI it fully rewrites the file (one per list) completely, changing the order in a way it alone knows. Sympa is storing its parameters in a sort of "file database" of it's own in  /var/blah/sympa/<listname>/config The data files look like flat text configuration files with a weird organization... json or yaml would be so much clear and easy to manage. When we use the Sympa administration UI it fully rewrites the file (one per list) completely, changing the order in a way it alone knows.  +  ==Puppet set up== ==Puppet set up==  +  Puppet has been set up (intelligent way to manage this but really unconventional use... I think Sympa's guys would be shocked) to control these data files as if they were human defined config files. So each configuration change made through admin interface is reverted in a matter of 30  minutes by puppet. Which explains the frustration  of all those who tried to play with this admin interface in Sympa. The hard part is that the tiniest change modifies nearly all the file, so diff is useless here... i had to print the file before and after and use a pencil to cross the unmodified parts to spot what changes were important. At the moment i have no brilliant idea, no idea at all would be more accurate, about how to manage this better. Puppet has been set up (intelligent way to manage this but really unconventional use... I think Sympa's guys would be shocked) to control these data files as if they were human defined config files. So each configuration change made through admin interface is reverted in a matter of 30  minutes by puppet. Which explains the frustration  of all those who tried to play with this admin interface in Sympa. The hard part is that the tiniest change modifies nearly all the file, so diff is useless here... i had to print the file before and after and use a pencil to cross the unmodified parts to spot what changes were important. At the moment i have no brilliant idea, no idea at all would be more accurate, about how to manage this better.  +  +== Configuration Notes ==     In the puppet "Sympa" module there is now a variable named "critical", false by default. If we set it to true the list archive and subscription get restricted. So we will be able to reuse this easily for other lists if the need appears later. In the puppet "Sympa" module there is now a variable named "critical", false by default. If we set it to true the list archive and subscription get restricted. So we will be able to reuse this easily for other lists if the need appears later.  +  +When sender_subscriber=true (a.k.a. allow_subscriber=true) then all subscribers to the list are allowed to send to the list as well. However, what isn't obvious is that ''anyone'' with a @mageia.org may also send to the list, whether subscribed or not.  +  +If automated e-mails are expected to be sent to a group, make sure the From: address is included in sender_email. This isn't necessary if sender_subscriber=true and the mail comes from @mageia.org.     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

‎Sympa Configuration: slight changes to improve readability

← Older revision Revision as of 15:43, 24 October 2024 Line 1: Line 1:  = Sympa Configuration = = Sympa Configuration =    −Sympa is storing its parameters in a sort of "file database" of it's own in  /var/blah/sympa/<listname>/config The data files look like flat text configuration files with a weird organization... json or yaml would be so much clear and easy to manage. When we use the Sympa administration UI it fully rewrites the file (one per list) completely, changing the order in a way it alone knows. Puppet has been set up (intelligent way to manage this but really unconventional use... I think Sympa's guys would be shocked) to control these data files as if they were human defined config files. So each configuration change made through admin interface is reverted in a matter of 30  minutes by puppet. Which explains the frustration  of all those who tried to play with this admin interface in Sympa. The hard part is that the tiniest change modifies nearly all the file, so diff is useless here... i had to print the file before and after and use a pencil to cross the unmodified parts to spot what changes were important. At the moment i have no brilliant idea, no idea at all would be more accurate, about how to manage this better.+Sympa is storing its parameters in a sort of "file database" of it's own in  /var/blah/sympa/<listname>/config The data files look like flat text configuration files with a weird organization... json or yaml would be so much clear and easy to manage. When we use the Sympa administration UI it fully rewrites the file (one per list) completely, changing the order in a way it alone knows.  +==Puppet set up==  +Puppet has been set up (intelligent way to manage this but really unconventional use... I think Sympa's guys would be shocked) to control these data files as if they were human defined config files. So each configuration change made through admin interface is reverted in a matter of 30  minutes by puppet. Which explains the frustration  of all those who tried to play with this admin interface in Sympa. The hard part is that the tiniest change modifies nearly all the file, so diff is useless here... i had to print the file before and after and use a pencil to cross the unmodified parts to spot what changes were important. At the moment i have no brilliant idea, no idea at all would be more accurate, about how to manage this better.    −In the puppet "Sympa" module a variable named "critical", false by default, if we set it to true the list archive and subscription get restricted. So we will be able to reuse this easily for other lists if the need appears later.+In the puppet "Sympa" module there is now a variable named "critical", false by default. If we set it to true the list archive and subscription get restricted. So we will be able to reuse this easily for other lists if the need appears later.     [[Category:Sysadmin]] [[Category:Sysadmin]] Marja

Create page with information by Maât

New page

= Sympa Configuration =

Sympa is storing its parameters in a sort of "file database" of it's own in  /var/blah/sympa/<listname>/config The data files look like flat text configuration files with a weird organization... json or yaml would be so much clear and easy to manage. When we use the Sympa administration UI it fully rewrites the file (one per list) completely, changing the order in a way it alone knows. Puppet has been set up (intelligent way to manage this but really unconventional use... I think Sympa's guys would be shocked) to control these data files as if they were human defined config files. So each configuration change made through admin interface is reverted in a matter of 30  minutes by puppet. Which explains the frustration  of all those who tried to play with this admin interface in Sympa. The hard part is that the tiniest change modifies nearly all the file, so diff is useless here... i had to print the file before and after and use a pencil to cross the unmodified parts to spot what changes were important. At the moment i have no brilliant idea, no idea at all would be more accurate, about how to manage this better.

In the puppet "Sympa" module a variable named "critical", false by default, if we set it to true the list archive and subscription get restricted. So we will be able to reuse this easily for other lists if the need appears later.

[[Category:Sysadmin]] Danf

‎Members

← Older revision Revision as of 14:12, 24 October 2024 Line 14: Line 14:     * David Walser <luigiwalser@yahoo.com> * David Walser <luigiwalser@yahoo.com>  +* Nicolas Salguero (ns80) <ns80 AT mageia DOT org     === Policies === === Policies === Marja

‎Update the Maintdb: Add a safer version

← Older revision Revision as of 20:32, 23 October 2024 Line 14: Line 14:     To unassign a package on behalf of another user, run this command on the pkgsubmit host (currently duvel): To unassign a package on behalf of another user, run this command on the pkgsubmit host (currently duvel):  +<pre>  +sudo -u maintdb /usr/local/sbin/maintdb OLDUSER set PACKAGE nobody  +</pre>  +where PACKAGE is the package name, OLDUSER is the user who will be removed and nobody is the user to which the package will be assigned.  +  +The raw (read: dangerous) alternative with fewer checks is to run this instead:  <pre> <pre>  sudo -u maintdb sh -c 'cat "/var/lib/maintdb/db/$1" && echo "$2" >"/var/lib/maintdb/db/$1"' x PACKAGE nobody sudo -u maintdb sh -c 'cat "/var/lib/maintdb/db/$1" && echo "$2" >"/var/lib/maintdb/db/$1"' x PACKAGE nobody  </pre> </pre> −where PACKAGE is the package name and nobody is the user to which the package will be assigned. The previous maintainer's ID will be displayed when done. If the package name is invalid, an error message will be displayed and no reassignment will take place.+The previous maintainer's ID will be displayed when done. If the package name is invalid, an error message will be displayed and no reassignment will take place. Danf

Add distrib

← Older revision Revision as of 18:33, 23 October 2024 Line 8: Line 8:     Source RPMs also contain the binrepo files, so if a file is removed from binrepo it can be recovered from the associated .src.rpm (assuming we have it around in a long-term archive). So, if a file was in a src.rpm for an obsolete mga release, if we can recover it if needed, and if it is no longer used in cauldron or any current mga release, then it should be fine to remove it. Source RPMs also contain the binrepo files, so if a file is removed from binrepo it can be recovered from the associated .src.rpm (assuming we have it around in a long-term archive). So, if a file was in a src.rpm for an obsolete mga release, if we can recover it if needed, and if it is no longer used in cauldron or any current mga release, then it should be fine to remove it.  +  +== distrib ==  +This holds all RPMs and metadata for all supported releases. When this fills, nobody can build any more packages. One strategy to free space is to hard link identical RPMs between bootstrap and mirror for cauldron. Another is to remove obsolete and unsupported releases, although you must first ensure the files are available elsewhere in case we need to fulfill any obligations under the GPL (and other licenses) to provide source code (this responsibility may not actually apply, but you need to be sure about that before deleting).     == Expanding partitions == == Expanding partitions == Danf

Add beeba5000 (Bill Fisher)

← Older revision Revision as of 14:13, 23 October 2024 Line 17: Line 17:     User:Ba1234 User:Ba1234  +  +User:beeba5000     User:bermisch User:bermisch Marja

‎Update the Maintdb: Mention the host

← Older revision Revision as of 21:01, 22 October 2024 Line 13: Line 13:  === Update the Maintdb === === Update the Maintdb ===    −To unassign a package on behalf of another user, run this command:+To unassign a package on behalf of another user, run this command on the pkgsubmit host (currently duvel):  <pre> <pre>  sudo -u maintdb sh -c 'cat "/var/lib/maintdb/db/$1" && echo "$2" >"/var/lib/maintdb/db/$1"' x PACKAGE nobody sudo -u maintdb sh -c 'cat "/var/lib/maintdb/db/$1" && echo "$2" >"/var/lib/maintdb/db/$1"' x PACKAGE nobody  </pre> </pre> −where PACKAGE is the package name and nobody is the user to which the package will be assigned. The previous maintainer's ID will be displayed on success. If the package name is invalid, an error message will be displayed and no reassignment will take place.+where PACKAGE is the package name and nobody is the user to which the package will be assigned. The previous maintainer's ID will be displayed when done. If the package name is invalid, an error message will be displayed and no reassignment will take place. Danf

s/adrien/agallou/

← Older revision Revision as of 19:34, 21 October 2024 (One intermediate revision by the same user not shown)Line 16: Line 16:  *  [https://matrix.to/#/#mageia-space:matrix.org matrix.org]: ngompa, neoclust, akien *  [https://matrix.to/#/#mageia-space:matrix.org matrix.org]: ngompa, neoclust, akien  *  [https://www.ovhcloud.com/ OVH DNS] ([http://bonjourmageia.fr  bonjourmageia.fr]):  ? *  [https://www.ovhcloud.com/ OVH DNS] ([http://bonjourmageia.fr  bonjourmageia.fr]):  ? −*  [https://www.scaleway.com/ Scaleway (madb)]: adrien+*  [https://www.scaleway.com/ Scaleway (madb)]: agallou (Adrien Gallou)  *  tumbler account (bonjourmageia): dams/boklm/ennael/rda/rtp *  tumbler account (bonjourmageia): dams/boklm/ennael/rda/rtp  *  [https://twitter.com/mageia_org X/Twitter]: dams/boklm/ennael/rda/rtp *  [https://twitter.com/mageia_org X/Twitter]: dams/boklm/ennael/rda/rtp Marja

‎Distro Releasing: Link to Sysadmin_New_Release

← Older revision Revision as of 18:26, 21 October 2024 Line 39: Line 39:  === Distro Releasing === === Distro Releasing ===  * [[SOP Version and Release freeze]] * [[SOP Version and Release freeze]] −* [[Pushing isos]] (after a new Mageia release)+* [[Mageia_Release_Countdown|Releasing a new Mageia version checklist]] −* [[Mageia_Release_Countdown|Releasing a new Mageia version]]+* [[Sysadmin New Release]]  * Submit or move a package on request of a developer during release freeze ("Freeze push") * Submit or move a package on request of a developer during release freeze ("Freeze push")  * Trigger full distribution rebuild of packages * Trigger full distribution rebuild of packages  +* [[Pushing isos]] (after a new Mageia release)     === Misc === === Misc === Danf

Remove owner instructions

← Older revision Revision as of 17:21, 21 October 2024 Line 10: Line 10:  Then run (using your login as uid) on a host on Mageia infrastructure: Then run (using your login as uid) on a host on Mageia infrastructure:    −   [root@valstar ~]# ldapadd -H ldaps://ldap.mageia.org -D uid=$USER,ou=People,dc=mageia,dc=org -W -f addusertogroup.ldif+   [root@duvel ~]# ldapadd -H ldaps://ldap.mageia.org -D uid=$USER,ou=People,dc=mageia,dc=org -W -f addusertogroup.ldif     = Removing user from group = = Removing user from group = Line 23: Line 23:  Then run (using your login as uid) on a host on Mageia infrastructure: Then run (using your login as uid) on a host on Mageia infrastructure:    −   [root@valstar ~]# ldapmodify -H ldaps://ldap.mageia.org -D uid=$USER,ou=People,dc=mageia,dc=org -W -f remove.ldif+   [root@duvel ~]# ldapmodify -H ldaps://ldap.mageia.org -D uid=$USER,ou=People,dc=mageia,dc=org -W -f remove.ldif  +   += Removing owner of group =  +   +Before removing an owner of a group, ensure that another valid & active owner will remain. Create a small file removeowner.ldif with the following contents:  +  dn: cn=<mga-groupname>,ou=Group,dc=mageia,dc=org                   +  changetype: modify  +  delete: owner  +  owner: uid=<user-login>,ou=People,dc=mageia,dc=org  +where ''<mga-groupname>'' is the group from which you want to remove the user, and ''<user-login>'' is the login of the user.  +   +Then run (using your login as uid) on a host on Mageia infrastructure:  +   +  [root@duvel ~]# ldapmodify -H ldaps://ldap.mageia.org -D uid=$USER,ou=People,dc=mageia,dc=org -W -f removeowner.ldif     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

‎Upgrading from Mageia 9

← Older revision Revision as of 06:43, 21 October 2024 Line 454: Line 454:     <span style="color:red">'''Not supported:'''</span> <span style="color:red">'''Not supported:'''</span> −* Upgrading directly from Mageia 7. (or earlier releases)+* Upgrading directly from Mageia 8. (or earlier releases)  * Using any of the Live images - due to the Live system being copied "as is" to the target system. * Using any of the Live images - due to the Live system being copied "as is" to the target system.  * Upgrading a Mageia installation which was '''NOT''' in UEFI, towards a UEFI-mode. * Upgrading a Mageia installation which was '''NOT''' in UEFI, towards a UEFI-mode. Benmc

corrected text about sysadmins

← Older revision Revision as of 13:54, 20 October 2024 Line 68: Line 68:  Uw e-mailadres. Uw e-mailadres.    −{{Note-nl|Sinds 19 februari 2018 is het voor niemand meer mogelijk om het e-mailadres van het Mageia.org-gebruikersaccount te wijzigen via [https://identity.mageia.org/ Mageia Identity Management]. De optie was onveilig. Sysadmins onderzoeken of ze de functie kunnen herstellen met een veel betere beveiliging.}}+{{Note-nl|Sinds 19 februari 2018 is het niet meer voor iedereen mogelijk om het e-mailadres van het Mageia.org-gebruikersaccount zelfstandig te wijzigen via [https://identity.mageia.org/ Mageia Identity Management]. Deze optie was onveilig. Sysadmins onderzoeken of ze de functie kunnen herstellen met een veel betere beveiliging.}}     Zolang [https://identity.mageia.org/ Mageia Identity Management] niet toestaat dat gebruikers hun eigen e-mailadres wijzigen, moet er een bugrapport worden aangemaakt zodat een SysAdmin het e-mailadres kan wijzigen .</br> Zolang [https://identity.mageia.org/ Mageia Identity Management] niet toestaat dat gebruikers hun eigen e-mailadres wijzigen, moet er een bugrapport worden aangemaakt zodat een SysAdmin het e-mailadres kan wijzigen .</br> Hugomarc