Lector de Feeds
gtk-chtheme-0.3.1-18.mga10.src.rpm
In Mageia/cauldron/i586:
Gtk-chtheme allows you to change the Gtk+ 2.0 theme when not using GNOME.
Categorías: RPMs
qtlocation5-5.15.12-3.mga10.src.rpm
In Mageia/cauldron/i586:
Qt5 Location component.
Categorías: RPMs
qtlocation5-5.15.12-3.mga10.src.rpm
In Mageia/cauldron/x86_64:
Qt5 Location component.
Categorías: RPMs
QA proces voor het valideren van updates-nl
corrected two links for updates-announce
← Older revision Revision as of 16:00, 26 September 2024 Line 67: Line 67: ==== Voorbereiding ==== ==== Voorbereiding ==== −# '''Start de juiste installatie en installeer alle officieel uitgebrachte updates'''. Controleer in de header van het bugrapport welk "Product", "Version" en "Platform" staat vermeld, bijvoorbeeld Mageia 4 x86_64. Besef hierbij dat sommige bugs updates kunnen bevatten voor beide releases, dus controleer ook de advisory (het advies) van de packager. U moet in dit stadium alle testing-media uitschakelen.<br/><br/>De [[Example update advisory announcement|advisory]] beschrijft waarom het pakket wordt bijgewerkt en wat ermee is gedaan. De advisory is er er zodat we weten waarop we moeten testen. De kandidaat wordt later geüpload naar SVN Subversion) door iemand die daar toegang toe heeft, en openbaar gemaakt op [https://advisories.mageia.org/ Mageia's webpagina], evenals op de [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/updates-announce updates-announce mailinglijst], wanneer de updatekandidaten worden gepusht als een update.<br/><br/>Het moet ook de RPM's vermelden die worden bijgewerkt, evenals hun [[How to find a source RPM|SRPMs]].<br/><br/>+# '''Start de juiste installatie en installeer alle officieel uitgebrachte updates'''. Controleer in de header van het bugrapport welk "Product", "Version" en "Platform" staat vermeld, bijvoorbeeld Mageia 4 x86_64. Besef hierbij dat sommige bugs updates kunnen bevatten voor beide releases, dus controleer ook de advisory (het advies) van de packager. U moet in dit stadium alle testing-media uitschakelen.<br/><br/>De [[Example update advisory announcement|advisory]] beschrijft waarom het pakket wordt bijgewerkt en wat ermee is gedaan. De advisory is er er zodat we weten waarop we moeten testen. De kandidaat wordt later geüpload naar SVN Subversion) door iemand die daar toegang toe heeft, en openbaar gemaakt op [https://advisories.mageia.org/ Mageia's webpagina], evenals op de [https://ml.mageia.org/l/info/updates-announce updates-announce mailing list], wanneer de updatekandidaten worden gepusht als een update.<br/><br/>Het moet ook de RPM's vermelden die worden bijgewerkt, evenals hun [[How to find a source RPM|SRPMs]].<br/><br/> # '''Probeer de bug te reproduceren voordat u de bijgewerkte pakketten installeert vanuit de testing-repository'''. Dit is voor de grondigheid, omdat het bewijst dat u kunt verifiëren dat de bug is opgelost na de update. Het laat u ook zien wat u kunt verwachten als dat niet het geval is.<br/>Als u de bug niet kunt reproduceren, bijvoorbeeld bij gebrek aan geschikte hardware, moet u toch testen uitvoeren op de update, om ervoor te zorgen dat er geen nieuwe bugs zijn geïntroduceerd. U kunt ook een bericht achterlaten met de vraag of iemand anders de volledige test kan uitvoeren, bijvoorbeeld iemand met de juiste hardware. Hier is gezond verstand van toepassing. Het kan handig zijn om een e-mail te sturen naar de discuss- of dev-mailinglijst, met de vraag of mensen met de juiste hardware kunnen helpen met testen.<br/><br/>Als u de tag "has_procedure" in het Whiteboard-veld van het bugrapport vindt, is er een procedure beschikbaar om u te helpen - hetzij een recept voor het testen van de basisfunctionaliteit van het pakket, danwel (meestal met beveiligingsoplossingen) een manier om het probleem te repliceren of te provoceren. Dit kan van alles zijn, bijvoorbeeld een 'slecht' invoerbestand of een patch.<br/><br/> # '''Probeer de bug te reproduceren voordat u de bijgewerkte pakketten installeert vanuit de testing-repository'''. Dit is voor de grondigheid, omdat het bewijst dat u kunt verifiëren dat de bug is opgelost na de update. Het laat u ook zien wat u kunt verwachten als dat niet het geval is.<br/>Als u de bug niet kunt reproduceren, bijvoorbeeld bij gebrek aan geschikte hardware, moet u toch testen uitvoeren op de update, om ervoor te zorgen dat er geen nieuwe bugs zijn geïntroduceerd. U kunt ook een bericht achterlaten met de vraag of iemand anders de volledige test kan uitvoeren, bijvoorbeeld iemand met de juiste hardware. Hier is gezond verstand van toepassing. Het kan handig zijn om een e-mail te sturen naar de discuss- of dev-mailinglijst, met de vraag of mensen met de juiste hardware kunnen helpen met testen.<br/><br/>Als u de tag "has_procedure" in het Whiteboard-veld van het bugrapport vindt, is er een procedure beschikbaar om u te helpen - hetzij een recept voor het testen van de basisfunctionaliteit van het pakket, danwel (meestal met beveiligingsoplossingen) een manier om het probleem te repliceren of te provoceren. Dit kan van alles zijn, bijvoorbeeld een 'slecht' invoerbestand of een patch.<br/><br/> Line 108: Line 108: # '''Klik op ''Save''''' (opslaan). # '''Klik op ''Save''''' (opslaan). −{{note-nl|Normaal gesproken zie je dat iemand meldt dat de Advisory is geüpload. Je hoeft je hier geen zorgen over te maken. Teamleiders en mensen met relevante rechten uploaden nu de Advisories [https://svnweb.mageia.org/advisories/ als yaml-tekstbestanden naar svn]. Daar worden ze vervolgens gebruikt, wanneer de update wordt gepusht, om de [https://svnweb.mageia.org/advisories/ advisory website] en de [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/updates-announce/ updates-announce mailinglijst] bij te werken.+{{note-nl|Normaal gesproken zie je dat iemand meldt dat de Advisory is geüpload. Je hoeft je hier geen zorgen over te maken. Teamleiders en mensen met relevante rechten uploaden nu de Advisories [https://svnweb.mageia.org/advisories/ als yaml-tekstbestanden naar svn]. Daar worden ze vervolgens gebruikt, wanneer de update wordt gepusht, om de [https://svnweb.mageia.org/advisories/ advisory website] en de mailinglist [https://ml.mageia.org/l/info/updates-announce updates-announce] bij te werken. Ze worden geüpload voordat de sysadmin de update pusht en ze worden, zodra ze zijn voltooid, voorzien van een sterretje (*) in het eerste veld op [https://madb.mageia.org/tools/updates madb], en voorzien van een 'advisory'-tag in het whiteboard-veld van het updateverzoek op bugzilla. Ze worden geüpload voordat de sysadmin de update pusht en ze worden, zodra ze zijn voltooid, voorzien van een sterretje (*) in het eerste veld op [https://madb.mageia.org/tools/updates madb], en voorzien van een 'advisory'-tag in het whiteboard-veld van het updateverzoek op bugzilla. Hugomarc
Categorías: Wiki de Mageia
QA process for validating updates
Validate the update if it is ready: and update the 2nd link to the updates-announce ml, too
← Older revision Revision as of 14:43, 26 September 2024 (One intermediate revision by the same user not shown)Line 69: Line 69: ==== Preparation ==== ==== Preparation ==== −# '''Boot the correct installation and install all the officially released updates'''. Check the “Product”, “Version” and “Platform” in the header of the bug report to find what it should be, e.g. Mageia 4 x86_64. Also note that some bugs may contain updates for both releases so also check the advisory from the packager. You should have all Testing medias disabled at this stage.<br/><br/>The [[Example update advisory announcement|advisory]] is a description of why the package is being updated and what has been done to it. It is there so that we know what to test for. It is later uploaded to SVN by somebody who has access and made public on [https://advisories.mageia.org/ Mageia's webpage], as well as on the [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/updates-announce updates-announce mailing list] when the update candidates are pushed as an update.<br/><br/>It should also list the RPMs being updated as well as their [[How to find a source RPM|SRPMs]].<br/><br/>+# '''Boot the correct installation and install all the officially released updates'''. Check the “Product”, “Version” and “Platform” in the header of the bug report to find what it should be, e.g. Mageia 4 x86_64. Also note that some bugs may contain updates for both releases so also check the advisory from the packager. You should have all Testing medias disabled at this stage.<br/><br/>The [[Example update advisory announcement|advisory]] is a description of why the package is being updated and what has been done to it. It is there so that we know what to test for. It is later uploaded to SVN by somebody who has access and made public on [https://advisories.mageia.org/ Mageia's webpage], as well as on the [https://ml.mageia.org/l/info/updates-announce updates-announce mailing list] when the update candidates are pushed as an update.<br/><br/>It should also list the RPMs being updated as well as their [[How to find a source RPM|SRPMs]].<br/><br/> # '''Try to reproduce the bug before installing the updated packages from the testing repository'''. This is for thoroughness as it proves you are able to verify the bug is fixed after the update. It also shows you what to expect if it isn't.<br/>If you are unable to reproduce the bug, without suitable hardware for instance, you should still carry out testing of the update to ensure there have been no new bugs introduced. You can also leave a message asking if somebody else is able to fully test, for example, somebody with the correct hardware. Common sense applies here. It can be useful to send an email to the discuss or dev mailing list asking for people with the correct hardware to assist with testing.<br/><br/>If you find the tag "has_procedure" in the Whiteboard field of the bug report, then there is a procedure available to assist you - either a recipe for testing basic functionality of the package or (mostly with security fixes) a way to replicate or provoke the issue. This can be anything, e.g. a 'bad' input file or a patch.<br/><br/> # '''Try to reproduce the bug before installing the updated packages from the testing repository'''. This is for thoroughness as it proves you are able to verify the bug is fixed after the update. It also shows you what to expect if it isn't.<br/>If you are unable to reproduce the bug, without suitable hardware for instance, you should still carry out testing of the update to ensure there have been no new bugs introduced. You can also leave a message asking if somebody else is able to fully test, for example, somebody with the correct hardware. Common sense applies here. It can be useful to send an email to the discuss or dev mailing list asking for people with the correct hardware to assist with testing.<br/><br/>If you find the tag "has_procedure" in the Whiteboard field of the bug report, then there is a procedure available to assist you - either a recipe for testing basic functionality of the package or (mostly with security fixes) a way to replicate or provoke the issue. This can be anything, e.g. a 'bad' input file or a patch.<br/><br/> − ==== Installing the Update Candidate ==== ==== Installing the Update Candidate ==== Line 111: Line 110: # '''Click on ''Save''''' # '''Click on ''Save''''' −{{note|You will normally see that somebody mentions that the advisory has been uploaded. You need not worry about this. Team leaders and people with relevant permissions are now uploading the advisories [https://svnweb.mageia.org/advisories/ as yaml text files to svn] where they are then used, when the update is pushed, to update the [https://advisories.mageia.org/ advisories website] and [https://ml.mageia.org/wwsympa-wrapper.fcgi/info/updates-announce updates-announce] mailing list.+{{note|You will normally see that somebody mentions that the advisory has been uploaded. You need not worry about this. Team leaders and people with relevant permissions are now uploading the advisories [https://svnweb.mageia.org/advisories/ as yaml text files to svn] where they are then used, when the update is pushed, to update the [https://advisories.mageia.org/ advisories website] and [https://ml.mageia.org/l/info/updates-announce updates-announce] mailing list. They are uploaded before sysadmin push the update and, once completed, denoted by a star (*) in the first field on [https://madb.mageia.org/tools/updates madb] and the 'advisory' tag in the whiteboard field of the update request on bugzilla. They are uploaded before sysadmin push the update and, once completed, denoted by a star (*) in the first field on [https://madb.mageia.org/tools/updates madb] and the 'advisory' tag in the whiteboard field of the update request on bugzilla. Marja
Categorías: Wiki de Mageia
qtpositioning6-6.7.2-2.mga10.src.rpm
In Mageia/cauldron/i586:
Qt6 Positioning API provides positioning information via QML and C++ interfaces.
Categorías: RPMs
qtpositioning6-6.7.2-2.mga10.src.rpm
In Mageia/cauldron/x86_64:
Qt6 Positioning API provides positioning information via QML and C++ interfaces.
Categorías: RPMs
zsync-0.6.2-12.mga10.src.rpm
In Mageia/cauldron/x86_64:
zsync is a file transfer program. It allows you to download a file
from a remote web server, where you have a copy of an older version of
the file on your computer already. zsync downloads only the new parts
of the file. It uses the same algorithm as rsync.
zsync does not require any special server software or a shell account
on the remote system (rsync, in comparison, requires that you have an
rsh or ssh account, or that the remote system runs rsyncd). Instead,
it uses a control file - a .zsync file - that describes the file to be
downloaded and enables zsync to work out which blocks it needs. This
file can be created by the admin of the web server hosting the
download, and placed alongside the file to download - it is generated
once, then any downloaders with zsync can use it.
Categorías: RPMs
zsync-0.6.2-12.mga10.src.rpm
In Mageia/cauldron/i586:
zsync is a file transfer program. It allows you to download a file
from a remote web server, where you have a copy of an older version of
the file on your computer already. zsync downloads only the new parts
of the file. It uses the same algorithm as rsync.
zsync does not require any special server software or a shell account
on the remote system (rsync, in comparison, requires that you have an
rsh or ssh account, or that the remote system runs rsyncd). Instead,
it uses a control file - a .zsync file - that describes the file to be
downloaded and enables zsync to work out which blocks it needs. This
file can be created by the admin of the web server hosting the
download, and placed alongside the file to download - it is generated
once, then any downloaders with zsync can use it.
Categorías: RPMs
xlogical-1.0_8-20.mga10.src.rpm
In Mageia/cauldron/x86_64:
XLogical is a puzzle game based on an Amiga game developed
by Rainbow Arts called Logical. It features ray-traced graphics,
music, and sound effects. The game is addictive, requiring
parallel thinking and quick reflexes.
Categorías: RPMs
xlogical-1.0_8-20.mga10.src.rpm
In Mageia/cauldron/i586:
XLogical is a puzzle game based on an Amiga game developed
by Rainbow Arts called Logical. It features ray-traced graphics,
music, and sound effects. The game is addictive, requiring
parallel thinking and quick reflexes.
Categorías: RPMs
gvolwheel-1.0.3-1.mga10.src.rpm
In Mageia/cauldron/x86_64:
GVolWheel is application which lets you control the volume easily through a
tray icon you can scroll on. Easily integrate with minimal desktops (Openbox,
IceWM,XFCE etc).
GVolWheel is configured to use pavucontrol from the Pulseaudio project as the
optional mixer.
Categorías: RPMs
gvolwheel-1.0.3-1.mga10.src.rpm
In Mageia/cauldron/i586:
GVolWheel is application which lets you control the volume easily through a
tray icon you can scroll on. Easily integrate with minimal desktops (Openbox,
IceWM,XFCE etc).
GVolWheel is configured to use pavucontrol from the Pulseaudio project as the
optional mixer.
Categorías: RPMs
gtypist-2.9.5-7.mga10.src.rpm
In Mageia/cauldron/i586:
GNU Typist (or gtypist) is free software that assist you in learning
to type correctly.
It is intended to be used on a raw terminal without graphics.
Categorías: RPMs
gtypist-2.9.5-7.mga10.src.rpm
In Mageia/cauldron/x86_64:
GNU Typist (or gtypist) is free software that assist you in learning
to type correctly.
It is intended to be used on a raw terminal without graphics.
Categorías: RPMs
zip-3.0-15.mga10.src.rpm
In Mageia/cauldron/x86_64:
The zip program is a compression and file packaging utility. Zip is analogous
to a combination of the UNIX tar and compress commands and is compatible with
PKZIP (a compression and file packaging utility for MS-DOS systems).
Install the zip package if you need to compress files using the zip program.
This version support crypto encryption.
Categorías: RPMs
zip-3.0-15.mga10.src.rpm
In Mageia/cauldron/i586:
The zip program is a compression and file packaging utility. Zip is analogous
to a combination of the UNIX tar and compress commands and is compatible with
PKZIP (a compression and file packaging utility for MS-DOS systems).
Install the zip package if you need to compress files using the zip program.
This version support crypto encryption.
Categorías: RPMs
zfs-fuse-0.7.2.2-8.mga10.src.rpm
In Mageia/cauldron/x86_64:
ZFS is an advanced modern general-purpose filesystem from Sun
Microsystems, originally designed for Solaris/OpenSolaris.
This project is a port of ZFS to the FUSE framework for the Linux
operating system.
Categorías: RPMs