Lector de Feeds

← Older revision Revision as of 11:52, 16 October 2024 (One intermediate revision by the same user not shown)Line 11: Line 11:  Mageia Cauldron ist die '''Entwicklerversion von Mageia''' - welche später die '''nächste Mageia Veröffentlichung''' wird. Mageia Cauldron ist die '''Entwicklerversion von Mageia''' - welche später die '''nächste Mageia Veröffentlichung''' wird.    −{{note-de|Mageia Cauldron darf nicht mit einer stabilen Rolling Release version verwechselt werden. Cauldron ist eine rohe Entwicklerversion, welche unerwartet aber definitiv zu bestimmten Zeitpunkten brechen wird. Unter Umständen (abhängig von den Kenntnissen des Nutzers) wird die Installation so kaputt sein, das eine erneute Reinstallation erforderlich sein wird.}}+{{note-de|Mageia Cauldron darf nicht mit einer stabilen Rolling Release Version verwechselt werden. Cauldron ist eine rohe Entwicklerversion, welche unerwartet aber definitiv zu bestimmten Zeitpunkten brechen wird. Unter Umständen (abhängig von den Kenntnissen des Nutzers) wird die Installation so kaputt sein, das eine erneute Neuinstallation erforderlich sein wird.}}     == Wer sollte Mageia Cauldron verwenden, und wer nicht? == == Wer sollte Mageia Cauldron verwenden, und wer nicht? == Line 32: Line 32:     ===  Wie man Mageia Cauldron installiert === ===  Wie man Mageia Cauldron installiert ===  +{{Warning-de|Am 10. Oktober 2024 wurde herausgefunden, dass die Crypto-Policies der rpm-sequoia Policy hinzugefügt werden muss, damit das Upgrade auf Cauldron funktioniert. '''Die Upgrade-Methode, welche unten beschrieben ist, funktioniert nicht. Gehen Sie stattdessen wie folgt vor:'''<br>  +* Ersetzen Sie die urpmi Repositorien mit denen von Cauldron (siehe hierzu weiter unten) und führen Sie 'urpmi.update -a' aus.  +* Entfernen Sie die alten rpm Schlüssel mit 'rpm -e gpg-pubkey-80420f66-4d4fe123'  +* Installieren Sie die 'aktualisierten' Schlüssel von Cauldron:  +** rpmkeys --import https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/media/core/release/media_info/pubkey  +* Installieren Sie crypto-policies-scripts  +* Führen Sie 'urpmi --auto-s --auto --force' aus um von MGA9 auf Cauldron zu aktualisieren}}     Es gibt zwei Möglichkeiten, Mageia Cauldron zu installieren. Beide Varianten haben Vorteile. Es gibt zwei Möglichkeiten, Mageia Cauldron zu installieren. Beide Varianten haben Vorteile. Line 46: Line 53:  Entfernen aller Paketquellen der stabilen Version: Entfernen aller Paketquellen der stabilen Version:  {{command-de|urpmi.removemedia -a|prompt=#}} {{command-de|urpmi.removemedia -a|prompt=#}}  +  +Entfernen von Schlüsseln alter Pakete  +{{command|-derpm -e gpg-pubkey-80420f66-4d4fe123|prompt=#}}     Nun müssen die Cauldron Paketquellen hinzugefügt werden. Sie können entweder die Mirrorlist verwenden (diese wählt automatisch einen Spiegelserver für Sie aus) oder Sie verwenden einen bestimmten Spiegelserver. Nun müssen die Cauldron Paketquellen hinzugefügt werden. Sie können entweder die Mirrorlist verwenden (diese wählt automatisch einen Spiegelserver für Sie aus) oder Sie verwenden einen bestimmten Spiegelserver.  {{note-de|Da die Aktualisierungshäufigkeit eines Cauldron Systems sehr hoch ist wird empfohlen, einen bestimmten [https://mirrors.mageia.org/report Tier 1 Spiegelserver] zu verwenden. Bevor Sie einen bestimmten Spiegelserver auswählen, überprüfen Sie dessen [https://mirrors.mageia.org/status Status].}} {{note-de|Da die Aktualisierungshäufigkeit eines Cauldron Systems sehr hoch ist wird empfohlen, einen bestimmten [https://mirrors.mageia.org/report Tier 1 Spiegelserver] zu verwenden. Bevor Sie einen bestimmten Spiegelserver auswählen, überprüfen Sie dessen [https://mirrors.mageia.org/status Status].}}    −Wählen Sie die folgenden Befehle entsprechend der verwendeten Computerarchitektur aus: i586 für 32-Bit oder x86_64 für 64-Bit.+Wählen Sie die folgenden Befehle entsprechend der verwendeten Computerarchitektur aus: i686 für 32-Bit oder x86_64 für 64-Bit.     Wenn Sie die Mirrorlist verwenden wollen: Wenn Sie die Mirrorlist verwenden wollen: −{{command-de|urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.i586.list'|prompt=#}}+{{command-de|urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.i686.list'|prompt=#}}  oder: oder:  {{command-de|urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.x86_64.list'|prompt=#}} {{command-de|urpmi.addmedia --distrib --mirrorlist 'http://mirrors.mageia.org/api/mageia.cauldron.x86_64.list'|prompt=#}}     Wenn Sie einen spezifischen Spiegelserver verwenden wollen (Folgende URL ist ein Beispiel für einen Tier 1 Spiegelserver): Wenn Sie einen spezifischen Spiegelserver verwenden wollen (Folgende URL ist ein Beispiel für einen Tier 1 Spiegelserver): −{{command-de|urpmi.addmedia --distrib 'https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/'|prompt=#}}+{{command-de|urpmi.addmedia --distrib <nowiki>'https://mirror.accum.se/mirror/mageia/distrib/cauldron/i686/'</nowiki>|prompt=#}}  oder: oder: −{{command-de|urpmi.addmedia --distrib 'https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/'|prompt=#}}+{{command-de|urpmi.addmedia --distrib 'https://mirror.accum.se/mirror/mageia/distrib/cauldron/x86_64/'</nowiki>|prompt=#}}  +   +Installiere die crypto-policies-scripts um sicherzustellen, dass die neusten Crypto-Policies verwendet werden:  +{{command|urpmi crypto-policies-scripts|prompt=#}}    −Starten des Upgrades:+Starten Sie anschließend das Upgrade: −{{command-de|urpmi --auto-update --auto|prompt=#}}+{{command-de|urpmi --auto-update --auto --force|prompt=#}}     ==== Upgrade von der letzten stabilen Version zu Cauldron mittels DNF ==== ==== Upgrade von der letzten stabilen Version zu Cauldron mittels DNF ==== Psyca

Publication date: 16 Oct 2024
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-8508 Description NLnet Labs Unbound up to and including version 1.21.0 contains a vulnerability when handling replies with very large RRsets that it needs to perform name compression for. Malicious upstreams responses with very large RRsets can cause Unbound to spend a considerable time applying name compression to downstream replies. This can lead to degraded performance and eventually denial of service in well orchestrated attacks. The vulnerability can be exploited by a malicious actor querying Unbound for the specially crafted contents of a malicious zone with very large RRsets. Before Unbound replies to the query it will try to apply name compression which was an unbounded operation that could lock the CPU until the whole packet was complete. Unbound version 1.21.1 introduces a hard limit on the number of name compression calculations it is willing to do per packet. Packets that need more compression will result in semi-compressed packets or truncated packets, even on TCP for huge messages, to avoid locking the CPU for long. This change should not affect normal DNS traffic. References

• https://bugs.mageia.org/show_bug.cgi?id=33621
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8508

SRPMS 9/core

• unbound-1.21.1-1.mga9

‎Request Verification: Simplify command

← Older revision Revision as of 19:14, 15 October 2024 Line 9: Line 9:  * 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=MYACCOUNT,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)'  </pre> </pre> −Replace MYACCOUNT with your Mageia user ID and REQUESTER@E-MAIL with the e-mail address from Bugzilla. Use your Mageia password when it asks for a password. The user's Mageia account info will be shown including the uid of the account owner. If it matches the request, you're go to go.+Replace $USER with your Mageia user ID (if necessarY0 and REQUESTER@E-MAIL with the e-mail address from Bugzilla. Use your Mageia password when it asks for a password. The user's Mageia account info will be shown including the uid of the account owner. If it matches the request, you're go to go.     * 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. Danf

More renaming details after following the procedure

← Older revision Revision as of 18:47, 15 October 2024 Line 3: Line 3:  From time to time it is necessary to rename a user. This may be for cosmetic reasons or it could related to issues with the username such as it containing characters that cause problems with various bits of the infrastructure. From time to time it is necessary to rename a user. This may be for cosmetic reasons or it could related to issues with the username such as it containing characters that cause problems with various bits of the infrastructure.     +== Verifying the request ==  +  +First, make sure the rename request is legitimate. See the section on verification in [[SOP Change user e-mail]]. Make sure the new username is available and that it isn't somehow inappropriate or confusing.     == The actual user rename == == The actual user rename == Line 8: Line 11:  As users are stored in LDAP, this requires interaction with the primary LDAP server. As users are stored in LDAP, this requires interaction with the primary LDAP server.    −Let's say that ''olduser'' is the username that we wish to change.+Let's say that ''olduser'' is the username that we wish to change and ''newuser'' is the new one. Create a file rename.ldif containing: −   −   −  [root@valstar ~]# ldapmodify -H ldaps://ldap.mageia.org -D uid=yourusername,ou=People,dc=mageia,dc=org -W  −   −Note the use of yourusername above in the bind DN. This is, as the text suggests *your* username.  −   −It will prompt you to enter a password. After entering the password correctly you'll just be given a blank line. Continue and type:  −       dn: uid=olduser,ou=People,dc=mageia,dc=org    dn: uid=olduser,ou=People,dc=mageia,dc=org     changetype: modrdn    changetype: modrdn Line 22: Line 17:     deleteoldrdn: 1    deleteoldrdn: 1     +Next, run this:  +  [root@duvel ~]# ldapmodify -H ldaps://ldap.mageia.org -D uid=yourusername,ou=People,dc=mageia,dc=org -W < rename.ldif    −Press return on a blank line at the end and you should get:+Note the use of yourusername above in the bind DN. This is, as the text suggests *your* username. You should see: −       modifying rdn of entry "uid=olduser,ou=People,dc=mageia,dc=org"    modifying rdn of entry "uid=olduser,ou=People,dc=mageia,dc=org" −      That's it! You can just ctrl-d out of the ldapmodify shell after that. You can also write these commands to an LDIF file if you prefer. That's it! You can just ctrl-d out of the ldapmodify shell after that. You can also write these commands to an LDIF file if you prefer.    − +Now, ''if the user has a home directory'' (e.g. is a packager), change the home directory by creating a renamehd.ldif file and executing it like above (''note that this procedure is untested''): −You can then use the https://identity.mageia.org/ website to correct the home directory or fight some more with ldapmodify to change this if you're a masochist.+  dn: uid=newuser,ou=People,dc=mageia,dc=org  +  changetype: modify  +  replace: homeDirectory  +  homeDirectory: /home/newuser     You should then rename the actual homedir on git.mageia.org (currently duvel): You should then rename the actual homedir on git.mageia.org (currently duvel): −   [root@valstar ~]# mv /home/olduser /home/newuser+   [root@duvel ~]# mv /home/olduser /home/newuser −       And confirm this change worked: And confirm this change worked: −   [root@valstar ~]# getent passwd newuser+   [root@duvel ~]# getent passwd newuser     newuser:*:5123:5000:Joe User:/home/olduser:/usr/local/bin/sv_membersh.pl    newuser:*:5123:5000:Joe User:/home/olduser:/usr/local/bin/sv_membersh.pl     Hmm, it didn't work??? But perhaps it's a caching issue: Hmm, it didn't work??? But perhaps it's a caching issue:    −   [root@valstar ~]# nscd -i passwd+   [root@duvel ~]# nscd -i passwd −   [root@valstar ~]# getent passwd newuser+   [root@duvel ~]# getent passwd newuser     newuser:*:5123:5000:Joe User:/home/newuser:/usr/local/bin/sv_membersh.pl    newuser:*:5123:5000:Joe User:/home/newuser:/usr/local/bin/sv_membersh.pl    Line 52: Line 49:     Although it's run by cron, and the home directory is manually renamed, it is probably wise to run:   Although it's run by cron, and the home directory is manually renamed, it is probably wise to run:   −   [root@valstar ~]# /usr/local/bin/ldap-sshkey2file.py+   [root@duvel ~]# /usr/local/bin/ldap-sshkey2file.py  to generate ssh key files (i.e. the authorized_keys). to generate ssh key files (i.e. the authorized_keys).     If the old user maintains any packages, it is easiest to bulk change any maintainer db files with references to the old user: If the old user maintains any packages, it is easiest to bulk change any maintainer db files with references to the old user: −   [root@valstar ~]# sed -i 's/^olduser$/newuser/' /var/lib/maintdb/db/*+   [root@duvel ~]# sed -i 's/^olduser$/newuser/' /var/lib/maintdb/db/* − +See also [[SOP Reassign Package in Maintdb]] for more details on changing maintdb. −And to keep the generated people pages up-to-date, it's nice to run:  −  [root@alamut ~]# mkpeople  −  [root@alamut ~]# rm -f /var/www/vhosts/people.mageia.org/u/olduser.html  −       +And to keep the generated people pages up-to-date instead of waiting for the next cron job run, it's nice to run:  +  [root@sucuk ~]# mkpeople  +  [root@sucuk ~]# rm -f /var/www/vhosts/people.mageia.org/u/olduser.html     [[Category:Sysadmin]] [[Category:Sysadmin]] Danf

‎Also to be merged, possible extra replies in the forums: add an off-list dev ml reply

← Older revision Revision as of 12:24, 15 October 2024 Line 158: Line 158:     Everything from before October 7 has been merged. Leaving this link here for easier checking. Everything from before October 7 has been merged. Leaving this link here for easier checking.  +  +=To be merged, an off-list reply to dev ml=  +I've been using Linux for about 20 years. There are some annoying things about it.  +* Lots of graphical interfaces.  +* Lots of boot systems.  +* Lots of packaging systems.  +* Incompatibility between packages of the same format. rpm packages from openSUSE don't work on Mageia and vice-versa.  +  +There are a lot of people doing the same job. Distrowatch.com lists 275 distributions. For each of these distributions, someone needs to do the packaging for it.  +  +One of the few things I can think of to improve the packaging problem is to adopt flatpak packages, only packaging what doesn't exist in this universal format. Marja

Less librification of packages for ease of packaging

← Older revision Revision as of 01:49, 15 October 2024 (One intermediate revision by the same user not shown)Line 99: Line 99:     Once it will be made it should bring a breath of fresh air to the distribution and let it be more "efficient" also to the packaging process. With the newer cpu power/storage there should be enough room/power to test new stuff, new developing tools (that are already used elsewhere in other distro) and new ideas/scheme beside to the classic tools, at least for the size and the ambition of the distro. Once it will be made it should bring a breath of fresh air to the distribution and let it be more "efficient" also to the packaging process. With the newer cpu power/storage there should be enough room/power to test new stuff, new developing tools (that are already used elsewhere in other distro) and new ideas/scheme beside to the classic tools, at least for the size and the ambition of the distro.  +  +===Use a training mailing list for new packagers===  +A mailing list for this purpose was proposed a while back, I don't remember if it was implemented.  +  +The Idea is that those training to be packagers can post their questions on the list, and experienced packagers will answer their questions & give guidance.  Like using a mailing list instead of or complementing a mentor.  Altough a mentor would still be required to become a qualified packager.  +Existing packagers could also post questions to the list, expecially useful to relatively new packagers.  +  +Being separate from the dev list is an advantage, as the dev list is primarily focused on problems with specific packages, and not how to package.  +  +A mailing list is better than online sites, as many using Mageia are not in European time zones, such a those in the Americas and Eastern Asia.  This would give us a larger pool of potential packagers.  +  +===Make less use of librification===  +Current policies prefer moving libraries included in packages outside the upstream package.  +  +Although that makes it easier to adresse security concerns, it makes in harder to package an application, due to having to remove the internal library and link to the appropriate external version.  In some cases we have to be vigilent to ensure that the version required by the library remains available.  +  +So except in relatively simple cases, we could use the libraries included in the upstream package.  Of course that depends on the judgement of experienced packagers, and I'm not there yet.  +     ==A contributor works for free for a project if he has confidence in its future.== ==A contributor works for free for a project if he has confidence in its future.==  +  The foundations of mageia are sound. It's a community distribution with clear values. However, Our association governance doesn't work. The foundations of mageia are sound. It's a community distribution with clear values. However, Our association governance doesn't work.  ===Improve our Association Governance:=== ===Improve our Association Governance:=== Andre999

Publication date: 14 Oct 2024
Type: bugfix
Affected Mageia releases : 9
Description Latest bugfix release for mesa 24.2.x branch, which improves stability. References

• https://bugs.mageia.org/show_bug.cgi?id=33612
• https://docs.mesa3d.org/relnotes/24.2.4.html
• https://docs.mesa3d.org/relnotes/24.2.0.html#changes
• https://docs.mesa3d.org/relnotes/24.2.1.html#changes
• https://docs.mesa3d.org/relnotes/24.2.2.html#changes
• https://docs.mesa3d.org/relnotes/24.2.3.html#changes
• https://docs.mesa3d.org/relnotes/24.2.4.html#changes

SRPMS 9/tainted

• mesa-24.2.4-2.mga9.tainted

9/core

• mesa-24.2.4-2.mga9

Publication date: 14 Oct 2024
Type: bugfix
Affected Mageia releases : 9
Description This update fixes functionality and other bugs; see the references. References

• https://bugs.mageia.org/show_bug.cgi?id=33606
• https://nmap.org/changelog.html#7.95

SRPMS 9/core

• nmap-7.95-1.mga9
• libssh2-1.11.0-1.mga9

Publication date: 14 Oct 2024
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-7519 , CVE-2024-7520 , CVE-2024-7521 , CVE-2024-7522 , CVE-2024-7524 , CVE-2024-7525 , CVE-2024-7526 , CVE-2024-7527 , CVE-2024-7528 , CVE-2024-7529 , CVE-2024-7531 , CVE-2024-8385 , CVE-2024-8381 , CVE-2024-8382 , CVE-2024-8383 , CVE-2024-8384 , CVE-2024-8386 , CVE-2024-8387 Description The current version has reached EOL and several security vulnerabilities were fixed by Mozilla. We are having some issues that are delaying the build for some architectures, so for the moment we are releasing this update just for x86_64. References

• https://bugs.mageia.org/show_bug.cgi?id=33502
• https://www.thunderbird.net/en-US/thunderbird/128.1.0esr/releasenotes/
• https://www.thunderbird.net/en-US/thunderbird/128.1.1esr/releasenotes/
• https://www.mozilla.org/en-US/security/advisories/mfsa2024-37/
• https://www.thunderbird.net/en-US/thunderbird/128.2.0esr/releasenotes/
• https://www.thunderbird.net/en-US/thunderbird/128.2.1esr/releasenotes/
• https://www.thunderbird.net/en-US/thunderbird/128.2.2esr/releasenotes/
• https://www.thunderbird.net/en-US/thunderbird/128.2.3esr/releasenotes/
• https://www.mozilla.org/en-US/security/advisories/mfsa2024-43/
• https://www.thunderbird.net/en-US/thunderbird/128.3.0esr/releasenotes/
• https://www.mozilla.org/en-US/security/advisories/mfsa2024-49/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7519
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7520
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7521
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7522
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7524
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7525
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7526
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7527
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7528
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7529
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7531
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8385
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8381
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8382
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8383
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8384
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8386
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-8387

SRPMS 9/core

• thunderbird-128.3.0-1.mga9
• thunderbird-l10n-128.3.0-1.mga9

Publication date: 14 Oct 2024
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-9680 Description The updated packages fix a security vulnerability: Use-after-free in Animation timeline. (CVE-2024-9680) We are having some issues that are delaying the build for some architectures, so for the moment we are releasing this update just for x86_64. References

• https://bugs.mageia.org/show_bug.cgi?id=33629
• https://www.mozilla.org/en-US/firefox/128.3.1/releasenotes/
• https://www.mozilla.org/en-US/security/advisories/mfsa2024-51/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-9680

SRPMS 9/core

• firefox-128.3.1-1.mga9
• firefox-l10n-128.3.1-1.mga9

‎How to reach potential contributors

← Older revision Revision as of 17:31, 14 October 2024 Line 22: Line 22:  ==Statistics needed regarding younger newgen developers== ==Statistics needed regarding younger newgen developers==  to remain in the linux world, I guess many of them are developing on other linux forks, e.g. android os or android apps, but here we need more statistics. to remain in the linux world, I guess many of them are developing on other linux forks, e.g. android os or android apps, but here we need more statistics.  +     =How to reach potential contributors= =How to reach potential contributors= Line 28: Line 29:  Well, if we are brainstorming about how to increase contributors, I would say that there are several things that would help. Well, if we are brainstorming about how to increase contributors, I would say that there are several things that would help.    −  * Demonstrate that contributing has tangible benefit to the community.+* Demonstrate that contributing has tangible benefit to the community. −  * Share details of what, specifically, help is needed with.+* Share details of what, specifically, help is needed with. −  * Provide a clear path for getting involved.+* Provide a clear path for getting involved.  +   +   += Who is a contributor =  +* well, developers, helpers in forum, users, anyone can be a contributor  +* ''your'' time contributing or ''wanting'' giving time to contribute makes the difference  +* for example: editing this wiki is a contribution, proposing ideas is be(com)ing a contributor     ==Previously used methods that may need to be revived or enhanced== ==Previously used methods that may need to be revived or enhanced== Baud

added NL banner

← Older revision Revision as of 10:38, 14 October 2024 Line 4: Line 4:  [[Category:Triage]] [[Category:Triage]]    −{{Multi language banner-fr|[[Aktivieren_der_Testmedien-de|Deutsch]] ; [[Enabling_the_Testing_media|English]] ; [[Activer les dépôts Testing-fr|Français]]}}+{{Multi language banner-fr|[[Aktivieren_der_Testmedien-de|Deutsch]] ; [[Enabling_the_Testing_media|English]] ; [[Activer les dépôts Testing-fr|Français]] ; [[Activeren van de Testing-pakketdepots-nl|Nederlands]] ; }}     == Pourquoi les dépôts Testing sont désactivés ? == == Pourquoi les dépôts Testing sont désactivés ? == Hugomarc

added NL banner

← Older revision Revision as of 10:37, 14 October 2024 Line 1: Line 1: −{{multi language banner|[[Aktivieren_der_Testmedien-de|Deutsch]] ; [[Enabling_the_Testing_media|English]] ; [[Activer_les_dépôts_Testing-fr|Français]]}}+{{multi language banner|[[Aktivieren_der_Testmedien-de|Deutsch]] ; [[Enabling_the_Testing_media|English]] ; [[Activer_les_dépôts_Testing-fr|Français]] ; [[Activeren van de Testing-pakketdepots-nl|Nederlands]] ; }}     == Why are they disabled? == == Why are they disabled? == Hugomarc

added NL banner

← Older revision Revision as of 10:36, 14 October 2024 Line 3: Line 3:  [[Category:Triage]] [[Category:Triage]]  [[Category:Howtos]] [[Category:Howtos]] −{{multi_language_banner-de|[[Aktivieren der Testmedien-de|Deutsch]] ; [[Enabling the Testing media|English]] ; [[Activer_les_dépôts_Testing-fr|Français]]}}+{{multi_language_banner-de|[[Aktivieren der Testmedien-de|Deutsch]] ; [[Enabling the Testing media|English]] ; [[Activer_les_dépôts_Testing-fr|Français]] ; [[Activeren van de Testing-pakketdepots-nl|Nederlands]] ; }}  {{mgaport-de|url=Testmedien}} {{mgaport-de|url=Testmedien}}    Hugomarc

Created page with " Category:Contributors Category:QA Category:Triage Category:Howtos Category:Nederlands Category:Documenten-nl {{multi language banner|Aktivieren_de..."

New page

[[Category:Contributors]]
[[Category:QA]]
[[Category:Triage]]
[[Category:Howtos]]
[[Category:Nederlands]]
[[Category:Documenten-nl]]

{{multi language banner|[[Aktivieren_der_Testmedien-de|Deutsch]] ; [[Enabling_the_Testing_media|English]] ; [[Activer_les_dépôts_Testing-fr|Français]] ; [[Activeren van de Testing-pakketdepots-nl|Nederlands]] ; }}

== Waarom zijn de Testing-depots uitgeschakeld? ==

Updaten vanuit de Testing-pakketdepots (repositories) is standaard niet ingeschakeld. U kunt vanuit deze depots pakketten installeren, maar u kunt geen bestaand pakket updaten met eentje uit Testing. De reden hiervoor is simpelweg dat de software die erin staat niet getest is. Hoewel de pakketmakers meestal goed controleren of ze iets kapot hebben gemaakt, of ergens anders problemen hebben veroorzaakt, is het gewoon niet gecontroleerd.

Hier komt het [[QA Team-nl|QA-team]] om de hoek kijken!

{{note-nl|De benamingen "media" en "repository" (pakketdepot) worden soms door elkaar gebruikt - ze verwijzen naar de plek waar programmapakketten worden opgehaald.
"Media" betekent in sommige andere gevallen het ISO-installatiebestand.}}

== Wat betekenen al die namen? ==

Het zal u waarschijnlijk opvallen dat u veel meer media hebt uitgeschakeld dan ingeschakeld.

; Release media
: Dit zijn de media waaruit de meeste pakketten die we voor het eerst installeren afkomstig zijn. Ze bevatten alle pakketten zoals ze waren op het moment van de release (de editie van Mageia).
; Debug media
: Debug media bevat debug-informatie van de verschillende pakketten. We hoeven ons daar niet echt zorgen over te maken. Hoewel ze nuttig kunnen zijn om te helpen bij het debuggen van een pakket dat crasht, hoeft u over het algemeen niet vanaf deze media te updaten, alleen vanaf deze media te installeren.
; Updates media
: Deze bevatten alle bijgewerkte pakketten (updates) die de [[QA proces voor het valideren van updates-nl|QA-validatie]] hebben doorstaan ​​en door de systeembeheerders zijn gepusht (verplaatst van het ene medium naar het andere).
; Updates Testing media
: Dit zijn enkele van de media waarin we hier geïnteresseerd zijn. De Testing media bevatten bijgewerkte pakketten die wachten op [[QA proces voor het valideren van updates-nl|QA-validatie]]. Pakketten blijven daarin, totdat ze door het Sysadmin-team naar de relevante Updates-media worden gepusht.
; Backports media
: Backports zijn nieuwe versies van pakketten die eigenlijk niet in de bestaande release thuishoren. Ze kunnen vaak nieuwe en gewenste functies brengen, maar ook nieuwe en ongewenste problemen. Hoewel ze wel een [[QA proces voor het valideren van updates-nl|QA-validatie]]-proces doorlopen, kunnen ze conflicteren met andere pakketten op het systeem en worden ze grotendeels niet ondersteund.
; Backports Testing media
: Hier worden nieuwe backported pakketten bewaard totdat ze de [[QA proces voor het valideren van updates-nl|QA-validatie]] hebben doorlopen wanneer ze naar de relevante Backports-media worden verplaatst.

== Wat betekenen ''enabled'' (geactiveerd) en ''updates'' hier eigenlijk? ==

Zoals u in het bovenstaande overzicht ziet, worden bijgewerkte pakketten apart van de originele set in de media van ''Release'' bewaard. De bijgewerkte pakketten worden bewaard in de media van ''Updates''. Bijvoorbeeld ''Core Release'' en ''Core Updates''. De pakketten in ''Core Updates'' zijn bijgewerkte versies van de pakketten in ''Core Release''.

Om het proces van het installeren van updates te versnellen, worden alleen media waarvan is aangeduid dat zij bijgewerkte pakketten bevatten, gecontroleerd op nieuwere versies van wat u hebt geïnstalleerd. Dit is wat wordt bedoeld wanneer een media is ingesteld als een media met ''Updates''.

Er zijn ook media die de meeste gewone gebruikers niet willen gebruiken, zoals de Testing media (waar updatekandidaten worden gebouwd en getest voordat ze als updates worden gepusht) of de Debug media (die technische debuginformatie bevatten die vereist is door debuggingsoftware zoals gdb). Al deze media worden standaard voor u toegevoegd, maar slechts enkele zijn geactiveerd om te worden gebruikt. Alle 'Enabled' media (geactiveerde media) worden gebruikt en alle niet-geactiveerde media worden genegeerd.

== Welke media moet ik instellen als updatemedia ==

U zou moeten kunnen zien dat media met de naam Updates al zijn ingeschakeld voor updates, maar u moet dit mogelijk instellen op Nonfree Updates en Tainted Updates, als dat nog niet het geval is.

Voor onze doeleinden in [[QA Team-nl|QA Team]] moeten we updates kunnen testen van Updates Testing-media, maar we willen niet dat ze in eerste instantie zijn ingeschakeld, omdat we alleen de pakketten installeren van Updates Testing-media die we moeten installeren om een ​​bepaalde update te kunnen testen. UpdatesTesting media '''mag u niet voortdurend ingeschakeld laten''' .

De extra media die u kunt instellen als updatemedia zijn:

* Core Updates Testing
* Nonfree Updates Testing
* Tainted Updates Testing
* Core 32bit Updates Testing ''(alleen x86_64)''

Updates van Release-media <u>mag u niet inschakelen!</u>

== Schakel ze op de eenvoudige manier in ==

Een eenvoudige manier om ze in te schakelen is door de expert-schakelaar te gebruiken zoals hieronder:

<pre>drakrpm-edit-media --expert</pre>

Plaats een vinkje in de kolom 'Updates' naast de hierboven vermelde media. Ze zouden moeten verschijnen zoals in de afbeelding hieronder, met het vinkje in de kolom Updates voor de (Core, Nonfree, Tainted) Updates Testing media.

[[File:Testing-media-setup.png‎]]

== Schakel ze op de ingewikkelde manier in ==

U kunt ook de opdrachtregel in de tekst-console gebruiken en voorzichtig /etc/urpmi/urpmi.cfg handmatig bewerken, waarbij u de update-optie toevoegt aan de testing pakketdepots (repositories). U moet urpmi.cfg bewerken als root, dus voorzichtigheid is geboden.

Voeg gewoon het woord update toe op een aparte regel binnen de relevante secties. Verschillende secties zouden al update moeten bevatten, zoals Core Updates, wat u een idee geeft van wat u moet doen voor de Testing-secties.

Bijvoorbeeld:

<pre>
Core\ Updates\ Testing {
ignore
key-ids: 80420f66
mirrorlist: $MIRRORLIST
update
with-dir: media/core/updates_testing
}
</pre>

Als u twijfelt, breng dan geen wijzigingen aan in het bestand!

== Voeg ze apart toe ==

U kunt ook handmatig aparte Testing-repositories toevoegen vanaf de opdrachtregel, en deze toestaan om geactiveerd te worden voor updates met de opdracht urpmi.addmedia met de optie --update.

De syntaxis hiervoor is:

<pre>urpmi.addmedia choose-a-name --update $PROTOCOL://$MIRROR/path/to/Mageia/$ARCH/media/$MEDIA/$REPOSITORY_testing</pre>

Bijvoorbeeld:

<pre>urpmi.addmedia CUTesting --update http://ftp.belnet.be/mirror/mageia/distrib/1/i586/media/core/updates_testing

of

urpmi.addmedia NFBTesting --update http://twiska.zarb.org/mageia/distrib/1/x86_64/media/nonfree/backports_testing</pre>

Zorg ervoor dat u de juiste architectuur voor uw installatie selecteert. De naam die u kiest, is geheel aan u. Een lijst met Mageia-mirrors vindt u [http://mirrors.mageia.org/ hier].

== Hoe activeer ik Testing pakketdepots, en hoe schakel ik ze uit ==

Zodra u updates van Testing repositories hebt ingeschakeld, kunt u ze in- en uitschakelen met de Media Manager. U kunt dit als optie openen in rpmdrake of via het Mageia Control Centre (MCC), in de sectie Configure Media Sources for Install and Update.

Om dit vanaf de opdrachtregel aan te roepen, gebruikt u <code>edit-urpm-sources.pl</code> als root.

U kunt ook de opdracht ''urpmi.update'' gebruiken, zoals hieronder:

<pre>
Om Core Updates Testing in te schakelen:
urpmi.update --no-ignore "Core Updates Testing"

Om ze weer uit te schakelen:
urpmi.update --ignore "Core Updates Testing"
</pre>

Vergeet niet om de media uit te schakelen nadat u de geselecteerde update voor testen hebt geïnstalleerd, anders wordt tijdens reguliere systeemupdates alles van de ingeschakelde testmedia geïnstalleerd.

Om dit makkelijker te maken zijn er een aantal [[QA Tips en Trucs-nl|nuttige aliassen]] die je kunt gebruiken.

Terug naar het [[QA Team Portal-nl|QA portaal]] Hugomarc

Add category

← Older revision Revision as of 20:25, 13 October 2024 Line 1: Line 1:  +[[Category:Contributors]]  +  {{introduction| {{introduction|    Marja