Lector de Feeds

El primero de Diciembre, el equipo de desarrolladores de Mageia se reunió para debatir el progreso de Mageia 10, estableciendo la ruta inicial e informándose sobre el estado de los principales componentes de software.

Se acordó un calendario tentativo, destinado a iniciar el ciclo de lanzamiento tan pronto como sea posible con la primera versión alpha saliendo para “ayer” (aquí estoy bromeando un poco), la primera beta en la primera mitad de Enero de 2026, continuando con la segunda beta un mes después. Se ha programado la primera RC (candidato a versión final) dos semanas después de la segunda beta, mientras que la versión final se espera para Abril de 2026.

Esta planeación pretende evitar que los componentes principales en Mageia 10 estén obsoletos antes del lanzamiento de la versión estable y al mismo tiempo asegúrale a los usuarios que todo esta trabajando perfectamente según nuestros estándares

Los componentes a incluir en la próxima versión serian:

• PHP: versiones 8.5 (en Cauldron) y 8.4 (probablemente en paralelo) se incluirán para soportar una amplia variedad de sitios.
• Python: no se ha planeado migrar a Python 3.14.
• Ruby: no se ha planeado actualizar a Ruby 4.0.0, ya que no contiene grandes cambios.
• Java: Java 21 se mantendrá como versión LTS (Long-Term Support) para asegurar el soporte 32-bit, but Java 25 (la versión más reciente) estará disponible como java-latest para las arquitecturas de 64-bits.
• GCC y LLVM: GCC actualmente está en 15.2.0, y LLVM en 20.1.8; se decidio mantnerlas par el lanzamiento.
• Go/Golang: Se acordó usar la versión 1.25.x, enfocándonos en corregir los paquetes que lo utilizan y necesitan ser actualizados (cerca de 820 paquetes).
• Kernel: La versión actual es 5.12.XX (LTS). Hay un debate actualmente sobre utilizar la versión 6.18.XX (próxima versión LTS) para mayor soporte del hardware más reciente en especial para los juegos.

En cuanto a los entornos de escritorio, LXDE y LXQt están actualmente actualizados, pero se esta debatiendo sobre KDE y GNOME. LibreOffice está en la versión 25.8.3, con la versión 26.2 planeada para finales de Enero de 2026.

Puede encontrar una lista mas detallada de las versiones de componentes, aplicaciones aqui.

Ahora los puntos críticos.

Al momento de la reunión, la creación de las ISO de 32-bit ISOs estaba bloqueda por un fallo en perl-URPM, que ha sido corregido.

Se descubrió la necesidad de actualizar manualmente las claves GPG y el paquete crypto-policies para la migración de Mageia 9 a Mageia 10. El equipo esta buscando una solución a implementarse en Mageia 9 antes del lanzamiento de Mageia 10.

Mozilla y otros están abandonando la arquitectura de 32-bit, incrementando la dificultad de mantener un soporte total.

Hay incertidumbre sobre el estado de Chromium que actualmente no esta mantenido.

El trabajo de integrar dos nuevos nodos ARM rentados para la construcción de paquetes va por buen camino, con progreso en el uso de contenedores Docker para la tarea, a pesar de las pequeñas modificaciones requeridas en las herramientas ulri e iurt para ello.

La reunión se destacó por clima constructivo y orientado al progreso. Mageia 10 parece estar lista para entrar en la fase Alfa, siendo conscientes de los problemas que aún quedan por resolver, especialmente en lo que respecta a i686, el kernel y el ajuste de los distintos componentes de software.

La comunidad está activa y colaborando, y el trabajo de consolidación realizado hasta ahora sienta una sólida base para un lanzamiento estable en los próximos meses.

Más actualizaciones sobre esto vendrán en el futuro, pero recomendamos mantener vigiladas las páginas Release Notes y Erratas.

¡Aún recibimos gratamente a quienes quieran probar nuestra distribución (o hacer cualquier tipo de contribución)!
Traducido por katnatek de la publicación original de Davide

‎Transifex: clarify reg. steps.

← Older revision Revision as of 00:09, 20 December 2025 (3 intermediate revisions by the same user not shown)Line 36: Line 36:     * [http://www.mageia.org/langs/report.php '''web pages translation statistics'''], * [http://www.mageia.org/langs/report.php '''web pages translation statistics'''], −* various reports about differences in translation level between [https://www.transifex.com/MageiaLinux/mageia/languages/ Transifex] and [http://gitweb.mageia.org/ our git repository] (as synchronisation is not yet automatic) of+* various reports about differences in translation level between [https://explore.transifex.com/MageiaLinux/mageia/ Transifex] and [http://gitweb.mageia.org/ our git repository] (as synchronisation is not yet automatic) of  ** [http://www.mageia.org/langs/report_tx_git.php '''our web pages'''], ** [http://www.mageia.org/langs/report_tx_git.php '''our web pages'''],  ** [http://www.mageia.org/langs/report_tx_git.php?c=Documentation '''documentation'''], ** [http://www.mageia.org/langs/report_tx_git.php?c=Documentation '''documentation'''], Line 96: Line 96:  === Transifex === === Transifex ===    −The simplest way to help translating is to use [https://www.transifex.com/ Transifex]. It is a web-based translation tool which enables us to have an overview of the status of the work on various projects and to translate online or offline (in this case, using your favorite translation tool). We abbreviate Transifex as Tx <br>+The simplest way to help translating is to use [https://explore.transifex.com/MageiaLinux/mageia/ Transifex]. It is a web-based translation tool which enables us to have an overview of the status of the work on various projects and to translate online or offline (in this case, using your favorite translation tool). We abbreviate Transifex as Tx <br>  With Transifex, you can easily translate the distribution itself, the help pages and the websites. <br> With Transifex, you can easily translate the distribution itself, the help pages and the websites. <br>  +  +To register an open source Transifex account, you must start directly from an open source project's page, e.g.:  +  +* Open [https://explore.transifex.com/MageiaLinux/mageia/ Transifex Mageia page]  +* Click "Join this project" button next to the language list.  +* That should bring up an open source registration, fill e-mail, username, password. Top of the page should show ''Create an Open Source Transifex account'' (don't worry it says "business e-mail" here).  +* That should bring up a page where you can set your full name and choose languages you will translate. Note top of this page should show: ''You are about to join the Mageia project''.  +* Then after you log in, and confirm your e-mail address via the link you received, Magiea team admins will confirm your application.  +* Thank you for contributing to the project!  +* The rest of the steps below are not necessary if you work on the Transifex web page and admins commit your work into the Mageia system files.     Once translated in Tx, the .po files must be committed to Mageia's [http://gitweb.mageia.org/software/ GIT repository] (GIT). Each team has to choose one or two committers, who shall have GIT write access.<br> Once translated in Tx, the .po files must be committed to Mageia's [http://gitweb.mageia.org/software/ GIT repository] (GIT). Each team has to choose one or two committers, who shall have GIT write access.<br> Kempelen

On December 1st, the Mageia development team met to discuss the progress of Mageia 10, establishing an initial release roadmap and addressing the status of key software stacks.

A tentative schedule was agreed upon, aiming to start the release cycle as soon as possible with a first alpha version to be released “yesterday” (here I’m kidding on the square), a first beta due in the first half of January 2026 followed by a second beta a month later. The release candidate is scheduled two weeks after the second beta while the final release is expected in April 2026.

This sequence aims to prevent the software stacks in Mageia 10 from becoming obsolete before its stable release and at the same time to ensure users that everything works perfectly as per our standards.

The team also reviewed the status of various software stacks to be included in the next version:

• PHP: versions 8.5 (in Cauldron) and 8.4 (likely in parallel) will be included to support a wider range of websites.
• Python: no immediate move to Python 3.14 is planned.
• Ruby: no planned update to Ruby 4.0.0, as it does not contain major changes.
• Java: Java 21 will be kept as the LTS (Long-Term Support) version to ensure 32-bit support, but Java 25 (the latest version) will be available as java-latest for 64-bit architectures.
• GCC and LLVM: GCC is currently at 15.2.0, and LLVM at 20.1.8; the decision was to stay with these for the release.
• Go/Golang: It was agreed to move to version 1.25.x, with a focus on fixing dependent packages that need updating (around 820 packages).
• Kernel: The current kernel is 6.12.XX (LTS). There is an ongoing discussion about adopting Kernel 6.18.XX (the next LTS) for better support of the latest hardware, especially for gaming.

For the desktop environments, LXDE and LXQt are already up to date but there is still an open discussion about KDE and GNOME. LibreOffice is at 25.8.3, with 26.2 planned for the end of January 2026.

You can find a more detailed list of stacks/apps/software versions proposed here.

Now the critical points.

At the time of the team meeting, creation of 32-bit ISOs was blocked due to a segfault in perl-URPM, which has since been overcome.

The problem of manually updating GPG keys and crypto-policies for migration from Mageia 9 to Mageia 10 was raised. The team is looking for a solution to be implemented in Mageia 9 prior to the release.

Mozilla and other vendors are abandoning the 32-bit architecture, making it increasingly difficult to maintain full support.

There is uncertainty about the status of Chromium as it’s currently unmaintained.

The work on integrating two new rented ARM build nodes is well underway, with progress made on using Docker containers for builds, although minor modifications to the ulri and iurt tools are required.

The meeting highlighted a constructive and progress-oriented climate. Mageia 10 appears ready to enter the Alpha phase, with awareness of the problems still to be solved – especially regarding i686 – the kernel and the tuning of the various software stacks.

The community is active and collaborative, and the consolidation work done so far lays a solid foundation for a stable release in the coming months.

Further updates on the work will follow but we still recommend keeping Release Notes and Errata pages monitored.

We’re still welcoming your contribution to test our distribution (or even more contribute to it)!

‎Various software: remove kdenlive

← Older revision Revision as of 17:59, 18 December 2025 Line 197: Line 197:     === Various software === === Various software === −{{Bug|34293}}, {{Bug|34812}} Some KDE applications like {{prog|plasmatube}} and {{prog|kdenlive}}, can fail when are installed for use in systems that not include Plasma Desktop with '''module "org.kde.desktop" is not installed''' exist two workarounds see {{Bug|34812#c3}}+{{Bug|34293}}, Some KDE applications like {{prog|plasmatube}}, can fail when are installed for use in systems that not include Plasma Desktop with '''module "org.kde.desktop" is not installed''' exist two workarounds see {{Bug|34812#c3}}     {{Bug|34634}} - '''CodeBlocks:''' For now, we had to disable the wxSmith plugin. {{Bug|34634}} - '''CodeBlocks:''' For now, we had to disable the wxSmith plugin. Katnatek

‎The raw material

← Older revision Revision as of 19:08, 17 December 2025 (2 intermediate revisions by the same user not shown)Line 37: Line 37:  == What Are You Testing? == == What Are You Testing? ==    −Mageia is available in a large number of formats known as ''ISOs'', each of which needs to be tested. Although traditionally aimed at creating bootable CD/DVD installation, increasingly they are used for creating bootable USB sticks. The ISOS are:-+Mageia is available in a large number of formats known as ''ISOs'', each of which needs to be tested. Although traditionally aimed at creating bootable CD/DVD installation, increasingly they are used for creating bootable USB sticks. From Mageia 10 onwards Council decided we allow greater than the previous DVD limit of 4.7GB, will try hard to fit any in "8 GB" USB drive but absolutely within DVD-R_DL size, 8.5GB. The ISOs are: (sizes of Mageia 10 alpha1)    −* Classical Installation Flavours which can be used to '''upgrade from the previous Mageia release'''.+* Classical Installation Flavours which can be used to '''upgrade from the previous Mageia release''': −- DVD 32bit 3.7GB+- DVD 32bit i686 4.2 GB −<BR>- DVD 64bit 3.7GB+<BR>- DVD 64bit 5.0 GB    −* LiveDVDs which '''cannot''' be used to upgrade a system.+* LiveDVDs which '''cannot''' be used to upgrade a system:  +- LiveDVD Plasma-x86_64  4.5 GB  +<BR>- LiveDVD GNOME-x86_64  4.2 GB  +<BR>- LiveDVD Xfce-i686  3.5 GB  +<BR>- LiveDVD Xfce-x86_64  3.9 GB    −<BR>- LiveDVD Plasma-x86_64 All languages 2.4GB+* Network-based Installation ISOs: −<BR>- LiveDVD GNOME-x86_64 All languages 2.1GB+Find them in your favourite mirror at −<BR>- LiveDVD Xfce-i586 All languages 1.9GB+<BR>- 32 bit: /mirror/mageia/distrib/10/i686/install/images/ −<BR>- LiveDVD Xfce-x86_64 All languages 2.0GB+<BR>- 64 bit: /mageia/distrib/10/x86_64/install/images/    −* Wired Network-based Installation CD.+<!--  - Network installer, Free Software CD 32bit ~35MB  - Network installer, Free Software CD 32bit ~35MB  <BR>- Network installer, Free Software CD 64bit ~20MB  <BR>- Network installer, Free Software CD 64bit ~20MB  <BR>- Network installer + nonfree firmware CD 32bit ~55MB  <BR>- Network installer + nonfree firmware CD 32bit ~55MB −<BR>- Network installer + nonfree firmware CD 64bit ~30MB +<BR>- Network installer + nonfree firmware CD 64bit ~30MB  +-->     === Terminology === === Terminology ===    −Conventionally the word 'release' applies to the major release of a distribution, say Mageia 3 or Mageia 5. Each major release involves a number of pre-release 'versions' (which encompass all the ISOs), typically alpha1, alpha2, beta1, beta2, RC (Release Candidate), final. Externally one talks in terms of "Mageia 5 is available in its Beta2 version".+Conventionally the word 'release' applies to the major release of a distribution, say Mageia 8 or Mageia 9. Each major release involves a number of pre-release 'versions' (which encompass all the ISOs), typically alpha1, alpha2, beta1, beta2, RC (Release Candidate), final. Externally one talks in terms of "Mageia 10 is available in its Beta2 version".     In the world of Mageia ISOs, the word ''Release'' combines the two: ''release-version'', like ''mageia4-final'' or ''mageia5-beta1''. (This may be because each such [pre] Release is in fact ultimately released to the public). This convention is used in the organization of the pre-release ISOs, and the tools for downloading & updating them, and hence also in this document. A final release is preceded by all the named [pre] Releases, mageiax-alpha1 -> mageiax-final. In the world of Mageia ISOs, the word ''Release'' combines the two: ''release-version'', like ''mageia4-final'' or ''mageia5-beta1''. (This may be because each such [pre] Release is in fact ultimately released to the public). This convention is used in the organization of the pre-release ISOs, and the tools for downloading & updating them, and hence also in this document. A final release is preceded by all the named [pre] Releases, mageiax-alpha1 -> mageiax-final. Line 101: Line 106:    mageia5-beta1   mageia5-beta1    −A typical ISO set for one is:-+A typical ISO set for one is: −  Mageia-5-beta1-LiveCD-GNOME-en-i586-CD+  Mageia-10-alpha1-i686 −  Mageia-5-beta1-LiveCD-KDE4-en-i586-CD+  Mageia-10-alpha1-x86_64/ −  Mageia-5-beta1-LiveDVD-GNOME-i586-DVD+  Mageia-10-alpha1-Live-GNOME-x86_64 −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD+  Mageia-10-alpha1-Live-Plasma-x86_64 −  Mageia-5-beta1-LiveDVD-KDE4-i586-DVD+  Mageia-10-alpha1-Live-Xfce-i686 −  Mageia-5-beta1-LiveDVD-KDE4-x86_64-DVD+  Mageia-10-alpha1-Live-Xfce-x86_64 − Mageia-5-beta1-dual-DVD  − Mageia-5-beta1-i586-DVD  − Mageia-5-beta1-x86_64-DVD     −In fact each so-called ''ISO'' is a '''directory''' which contains not only the actual ISO image file ''*.iso'', but additional files like date, checksums. For example (the Classic DVD):-+In fact each so-called ''ISO'' is a '''directory''' which contains not only the actual ISO image file ''*.iso'', but additional files like date, checksums. For example (the Classic DVD):    DATE.txt   DATE.txt −  Mageia-5-beta1-x86_64-DVD.idx+  Mageia-10-alpha1-x86_64.idx −  Mageia-5-beta1-x86_64-DVD.iso+  Mageia-10-alpha1-x86_64.iso −  Mageia-5-beta1-x86_64-DVD.iso.md5+  Mageia-10-alpha1-x86_64.iso.md5 −  Mageia-5-beta1-x86_64-DVD.iso.sha1+  Mageia-10-alpha1-x86_64.iso.sha3  + Mageia-10-alpha1-x86_64.iso.sha512    −or (a Live ISO):-+or for a Live ISO:    DATE.txt   DATE.txt −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.iso+  Mageia-10-alpha1-Live-Xfce-x86_64.iso.sha3 −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.iso.md5+  Mageia-10-alpha1-Live-Xfce-x86_64.lst −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.iso.sha1+  Mageia-10-alpha1-Live-Xfce-x86_64.lst.names −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.langs+  Mageia-10-alpha1-Live-Xfce-x86_64.iso −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.lst+  Mageia-10-alpha1-Live-Xfce-x86_64.iso.sha512 −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.lst.full+  Mageia-10-alpha1-Live-Xfce-x86_64.lst.full −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.lst.leaves+  Mageia-10-alpha1-Live-Xfce-x86_64.iso.md5 −  Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.lst.names+  Mageia-10-alpha1-Live-Xfce-x86_64.langs  + Mageia-10-alpha1-Live-Xfce-x86_64.lst.leaves  +      Note well that both the ISO directory and subordinate file names ''incorporate the Release''. This has consequences for '''you''' discussed later in "Directory/file name changes at Release changes". Note well that both the ISO directory and subordinate file names ''incorporate the Release''. This has consequences for '''you''' discussed later in "Directory/file name changes at Release changes".    −To see the contents of the ''DATE.txt'', ''iso.md5'' or ''iso.sha1'' files, simply+To see the contents of other files than the large .iso files, simply    cat <filename>   cat <filename>    Line 205: Line 210:  ==== Dorsync ==== ==== Dorsync ====    −Our command line tool dorsync can both fetch and update the ISOs, and also create bootable USB from downloaded file or directly downloading.  In contrast to IsoDomper, it can not make persistence for Live ISOs.+Our command line tool {{prog|dorsync}} can both fetch and update the ISOs, and also create bootable USB from downloaded file.  In contrast to IsoDomper, it can not make persistence for Live ISOs.     See the "ISO_testing_rsync_tools" [[ISO_testing_rsync_tools#Dorsync|here]] for further instructions. See the "ISO_testing_rsync_tools" [[ISO_testing_rsync_tools#Dorsync|here]] for further instructions. Morgano

← Older revision Revision as of 18:28, 17 December 2025 (2 intermediate revisions by the same user not shown)Line 1: Line 1:  {{multi language banner|[[ISO testing rsync tools|English]]; [[Outils rsync pour les tests d’image ISO-fr|Francais]];}} {{multi language banner|[[ISO testing rsync tools|English]]; [[Outils rsync pour les tests d’image ISO-fr|Francais]];}}    −{{introduction|This page describes tools to facilitate the management of Mageia ISOs for pre-release testing. It also details the use of ''rsync'' directly for this purpose. It is a supplement to the [[Pre-release ISO testing|"Pre-release ISO testing"]] page.}}+{{introduction|This page describes tools to facilitate the management of Mageia ISOs for pre-release testing. It also details the use of ''rsync'' directly for this purpose. It is a supplement to the [[Pre-release ISO testing|"Pre-release ISO testing"]] page. See that page about writing the downloaded ISO.  After that continue at [[Pre-release_ISO_testing:_Part_2|Pre-release ISO testing: Part_2]] for using it.}}     == Introduction == == Introduction == Line 147: Line 147:  * If you already have old versions it only transfers the difference * If you already have old versions it only transfers the difference  * Checksums the *.iso image files. * Checksums the *.iso image files. −* Can create bootable USB sticks both without downloading first, after download or synchronisation, and from downloaded files.+* Can create bootable USB sticks after download or synchronisation, and from previously downloaded files. ''If you want to make Mageia Live with persistence, or well as save/restore previous content, or reformat afterwards, use [[IsoDumper Writing ISO images on USB sticks|Isodumper]].''     === Installation and configuration === === Installation and configuration ===    −{{prog|dorsync}} is now packaged as mga-dorsync. In Mageia 9 it is in core updates repos (at time of writing 2025-12-17 in updates_testing)+{{prog|dorsync}} is now packaged as mga-dorsync. In Mageia 9 it is in core updates repos (at time of writing 2025-12-17 in updates_testing {{bug|34826}}).     Let it create the config file (if it does not exist already) by running it: Let it create the config file (if it does not exist already) by running it: Line 167: Line 167:  user=""    # Username used by rsync. user=""    # Username used by rsync.  password="" # Password used by rsync. </nowiki> password="" # Password used by rsync. </nowiki>  +Enter between the " marks:  * location: The path of your umbrella ISO directory, which once defined you will probably not alter. * location: The path of your umbrella ISO directory, which once defined you will probably not alter.  * release: e.g. ''mageia10-alpha''; to be changed at each new Release as announced on the QA MailList. * release: e.g. ''mageia10-alpha''; to be changed at each new Release as announced on the QA MailList. Line 175: Line 176:  When dorsync.conf is in place and correct, run dorsync again. When dorsync.conf is in place and correct, run dorsync again.    −First it will ask if to download to files or directly to USB media.+First it will ask if to Rsync (download/sync) or go directly to questions about dumping to USB media.    −Then, if dorsync.skip does not exist, it will ask you what files you want and create dorsync.skip. Then it immediately goes on to download the files.+Then, if dorsync.skip does not exist, it will ask you if to download all files or what files you want, and it creates dorsync.skip.  +   +Then it immediately goes on to download the files.    <nowiki>   <nowiki>  [morgan@svarten ~]$ dorsync   [morgan@svarten ~]$ dorsync   Line 239: Line 242:  === Using dorsync to write to USB === === Using dorsync to write to USB ===    −After it have downloaded/synced the files, it will ask (see above) if you want to dump one ISO file to one USB flash.+After it have downloaded/synced the files, it will ask (see above) if you want to dump one ISO file to an USB flash.     If you already have the files, launch dorsync and answer "D" on the question, so it skips downloading and checking. If you already have the files, launch dorsync and answer "D" on the question, so it skips downloading and checking. Line 245: Line 248:  It will list attached USB drives, and ask you which you choose, and then it will ask you which file to dump onto it.  It ask you for confirmation and then for root password.  It shows progress during writing. It will list attached USB drives, and ask you which you choose, and then it will ask you which file to dump onto it.  It ask you for confirmation and then for root password.  It shows progress during writing.    −See the [[Pre-release_ISO_testing]] page, "Creating a bootable ISO USB stick->Dorsync" for the sequel.+See the [[Pre-release_ISO_testing#Making_the_boot_media|Pre-release ISO testing]] for alternative ways, i.e isodumper can save and restore content, as well as making persistence for Live ISOs, and reformat.     === Limiting your ISO set === === Limiting your ISO set === Line 259: Line 262:  +Mageia-10-alpha1-Live-Xfce-x86_64 +Mageia-10-alpha1-Live-Xfce-x86_64  Mageia-10-alpha1-i686 Mageia-10-alpha1-i686 −Mageia-10-alpha1-x86_64+Mageia-10-alpha1-x86_64 </nowiki> −</nowiki>      As you see, the files to download are prepended by a "+". You can edit it as you like, and even create it before running dorsync the first time if you like. As you see, the files to download are prepended by a "+". You can edit it as you like, and even create it before running dorsync the first time if you like. Line 267: Line 269:     === When the Release changes === === When the Release changes ===  +  Dorsync can update files in place, provided they have the new name. Dorsync can update files in place, provided they have the new name.  Before using dorsync for the new Release, you ''must''   Before using dorsync for the new Release, you ''must''   Line 397: Line 400:                 rsync -av /src/foo /dest                rsync -av /src/foo /dest                 rsync -av /src/foo/ /dest/foo                rsync -av /src/foo/ /dest/foo −       [There are other basic ways of achieving the same thing, with /* or option-r]+       [There are other basic ways of achieving the same thing, with /* or option-r] </nowiki> −</nowiki>      ''Remember that all usage of 'rsync' requires that directory and filenames must be identical at both ends'' - unless you do not yet have the ISO locally. ''Remember that all usage of 'rsync' requires that directory and filenames must be identical at both ends'' - unless you do not yet have the ISO locally. Morgano

Please archive.

New page

This page should be archived, but I have forgot how to do it...

We now have [[Pre-release_ISO_testing]] instead. Morgano

Making downloading tools prominent, Promoting Isodumper, Dorsync updated and links further.

← Older revision Revision as of 16:43, 17 December 2025 Line 2: Line 2:     {{multi language banner|[[Pre-release ISO testing|English]] ; [[Vérification des images ISO avant diffusion : 1re PARTIE-fr|Français]] ;}} {{multi language banner|[[Pre-release ISO testing|English]] ; [[Vérification des images ISO avant diffusion : 1re PARTIE-fr|Français]] ;}} −  −[[Working on pre-release ISOs]] Seems obsolete. Keep it?      {{introduction|This Wiki page aimed to explain everything you need to know to participate in testing Pre-release Mageia ISO images. This is especially important to people who have not done it before. It got too big, so now: {{introduction|This Wiki page aimed to explain everything you need to know to participate in testing Pre-release Mageia ISO images. This is especially important to people who have not done it before. It got too big, so now: −* This PART 1 covers from joining Mageia QA up to creating the boot media to test.+* This PART 1 covers from joining Mageia QA up to creating the boot media to test. Also see  [[ISO_testing_rsync_tools|ISO testing rsync tools]] for our helpful tools!  * [[Pre-release ISO testing: Part 2]] covers from booting the test ISO to recording the results.}} * [[Pre-release ISO testing: Part 2]] covers from booting the test ISO to recording the results.}}    Line 154: Line 152:  The main thing to keep in mind is that you maintain just one copy of the ISOs you wish to test, keeping them up-to-date (''synchronised'') with their latest versions on the server - whether that be the latest Round in the ongoing Release, or a new Release - rather than downloading them entirely again. The main thing to keep in mind is that you maintain just one copy of the ISOs you wish to test, keeping them up-to-date (''synchronised'') with their latest versions on the server - whether that be the latest Round in the ongoing Release, or a new Release - rather than downloading them entirely again.    −Both the initial download (priming) & subsequent updating of your local ISOs are done using '''rsync''', which has the powerful & important ability to download ''only the changed parts'' of files, notably the large ISO images, greatly reducing download times. The use of ''rsync'' is very exact: it requires great care to make it do just what you want, and the long ISO directory names make difficult parameters. If you get it wrong, you will probably download entire ISOs you do not want. For this reason, there are several tools to make it ''easy to manage'' your own ISO set, keep it up-to-date: '' synchronized'' with the server. There is a separate Wiki page "https://wiki.mageia.org/en/ISO_testing_rsync_tools" devoted to these easy tools, which also covers hands-on use of naked ''rsync''. Take a look *now*.+Both the initial download (priming) & subsequent updating of your local ISOs are done using '''rsync''', which has the powerful & important ability to download ''only the changed parts'' of files, notably the large ISO images, greatly reducing download times. The use of ''rsync'' is very exact: it requires great care to make it do just what you want, and the long ISO directory names make difficult parameters. If you get it wrong, you will probably download entire ISOs you do not want.      −New Releases, and the issue of new Rounds of ISOs within the ongoing Release, are announced on the QA mailing list; together with other related information. These announcements are the signal for you to update ''your'' local ISOs.+==== Use our tools ! ====    −''Rsync'' requires a password, which is given out as needed by private e-mail whenever it changes. This is one item at least that you will ''have'' to maintain, whichever ISO synchronization tool you use.+For reason above, we have several tools to make it ''easy to manage'' your own ISO set, keep it up-to-date: '' synchronized'' with the server.  +Our Wiki page [[ISO_testing_rsync_tools|ISO testing rsync tools]] is devoted to these easy tools, which also covers hands-on use of naked ''rsync''. Take a look *now*.     ==== Directory/file name changes at Release changes ==== ==== Directory/file name changes at Release changes ====  +  +New Releases, and the issuing of new Rounds of ISOs within the ongoing Release, are announced on the QA mailing list; together with other related information. These announcements are the signal for you to update ''your'' local ISOs.  +  +''Rsync'' requires a password, which is given out as needed by private e-mail whenever it changes. This is one item at least that you will ''have'' to maintain, whichever ISO synchronization tool you use.     Look again at the last three lists above. Because ISO directory names and their subordinate file names incorporate the Release, when a Release changes, all these names change also - on the server. [The download source changes, and its content]. <BR> The business of synchronizing your local ISOs with those on the server necessitates that the elements you are synchronizing must be identically named. ''You must follow server changes''. Look again at the last three lists above. Because ISO directory names and their subordinate file names incorporate the Release, when a Release changes, all these names change also - on the server. [The download source changes, and its content]. <BR> The business of synchronizing your local ISOs with those on the server necessitates that the elements you are synchronizing must be identically named. ''You must follow server changes''. Line 192: Line 195:  === Creating a bootable ISO USB stick === === Creating a bootable ISO USB stick ===    −{{Note|On some older systems it is not possible to set a USB key as a boot device. If the BIOS doesn't give this option, you won't be able to do this}}+{{Note|On some older systems it is not possible to set a USB key as a boot device. If the BIOS doesn't give this option, you won't be able to boot from USB.  the setting may be a bit convoluted on modern BIOSes, amongst security settings.}}  +   +==== IsoDumper ====  +   +We recommend our GUI tool {{prog|IsoDumper}}. It can not only write an ISO boot image to a USB stick, but preserve & later restore its contents, and also simply format the stick for another use. Being a generic utility, it is fully documented on its [[IsoDumper Writing ISO images on USB sticks|own page]].  A speciality is that you can by a checkmark tell it to create a partition for persistence on Live ISOs, and optionally make it encrypted.  +   +It is available as a normal package '''isodumper''' to install as you like. Launched from menu or "isodumper" console command.     ==== Dorsync ==== ==== Dorsync ====    −The ''dorsync'' tool is downloaded by +Our command line tool dorsync can both fetch and update the ISOs, and also create bootable USB from downloaded file or directly downloading.  In contrast to IsoDomper, it can not make persistence for Live ISOs. − $ wget https://gitweb.mageia.org/qa/dorsync/tree/dorsync  −See the "ISO_testing_rsync_tools" [[ISO_testing_rsync_tools|Wiki page]] for a fuller note, and setting it up ("Dorsync->Preparation"). If you ''only'' want it as an ISO dumping tool, then just the following item should need defining:  − # location is where you stored the ISOs    #  − location=""  −It can quickly & easily make bootable ISO USB sticks for you; either after completing ISO synchronizations or when launched directly. After selecting "dump to usb", d|D, it asks which USB device to use [a warning is output if it finds none]:  −  <nowiki>  −$ dorsync  −Do you want to Rsync (R), skip Rsync and just dump to usb (D) or quit (Q): d  −USB drives found:  −    Device Size When Found Model  −1) /dev/sdb 4Gb Monday, November 17, 2014 18:29:29 CET CBM Flash Disk  −Please choose which USB to use or Q to quit and press <enter>: 1 </nowiki>  −Then it shows a list of ISO images it finds in your ISO directories, for you to chose which one to write out, e.g.  − <nowiki>  −List of ISOs:  −1) Mageia-5-beta1-x86_64-DVD.iso  −2) Mageia-5-beta1-LiveDVD-GNOME-x86_64-DVD.iso  −3) Mageia-5-beta1-LiveDVD-KDE4-x86_64-DVD.iso  −4) anyOldISO.iso  −Please choose which ISO to use or Q to quit and press <enter>: 3 </nowiki>  −And off it goes:  − <nowiki>  −About to dump /mnt/common/Mageia/KDE64/Mageia-5-beta1-LiveDVD-KDE4-x86_64-DVD.iso  −onto /dev/sdb (4Gb CBM Flash Disk found at Monday, November 17, 2014 18:29:29 CET)  −This will destroy any data already on the USB device.  −Press Y to confirm or Q to quit: y  −Please be patient this can take a while  −This operation requires root privileges  −Please enter your root password..  −Password:   −...  −Completed OK. </nowiki>  −   −==== IsoDumper ====     −Otherwise the new GUI tool ''IsoDumper'' is the easiest way to not only write an ISO boot image to a USB stick, but preserve & restore its previous contents. Being a generic utility, it is fully documented on its [[IsoDumper Writing ISO images on USB sticks|own page]].+See the "ISO_testing_rsync_tools" [[ISO_testing_rsync_tools#Dorsync|here]] for further instructions. −It is available as a normal package '''isodumper''' to install as you like. Launched from menu or "isodumper" console command, it can variously do:<BR>  −- Writing out a selected ''*.iso'' image. <BR>  −- Backup the USB stick to a chosen ''*.img'' file, then write out the selected ''*.iso'' image. <BR>  −- Restore the USB stick from its backup ''*.img'' file (achieved by selecting this file to write out).  −<BR>   −Note: The warning dialogue that "the USB stick contents will be destroyed" is currently displayed even when a backup is requested.      ==== Doing it by hand ==== ==== Doing it by hand ==== Morgano

← Older revision Revision as of 13:34, 17 December 2025 Line 3: Line 3:  {{introduction|This page describes tools to facilitate the management of Mageia ISOs for pre-release testing. It also details the use of ''rsync'' directly for this purpose. It is a supplement to the [[Pre-release ISO testing|"Pre-release ISO testing"]] page.}} {{introduction|This page describes tools to facilitate the management of Mageia ISOs for pre-release testing. It also details the use of ''rsync'' directly for this purpose. It is a supplement to the [[Pre-release ISO testing|"Pre-release ISO testing"]] page.}}    −= Introduction =+== Introduction ==     Mageia ISOs are hosted on a server: ''bcd.mageia.org/isos''. Mageia ISOs are hosted on a server: ''bcd.mageia.org/isos''. Line 60: Line 60:  Applies to all the tools: despite its amazing capabilities, it seems that any line break stops ''rsync'': it does not recover/resume after the break. You probably will have to abort it. Re-running the synchronisation, it will quickly catch up to where it got to, and carry on. Thus, if necessary you can interrupt an ongoing transfer without significant penalty when you re-do later. Applies to all the tools: despite its amazing capabilities, it seems that any line break stops ''rsync'': it does not recover/resume after the break. You probably will have to abort it. Re-running the synchronisation, it will quickly catch up to where it got to, and carry on. Thus, if necessary you can interrupt an ongoing transfer without significant penalty when you re-do later.    −= MageiaSync =+== MageiaSync ==     '''mageiaSync''' is a tool to get one or more ISOs images of Mageia, from testing repositories or from mirrors. It is the main tool for ISO testers, the only one with a GUI. It manipulates ISOs under their full long (and evolving) names. It has a facility (after a new Release) to rename local ISO directories & files - on demand. '''mageiaSync''' is a tool to get one or more ISOs images of Mageia, from testing repositories or from mirrors. It is the main tool for ISO testers, the only one with a GUI. It manipulates ISOs under their full long (and evolving) names. It has a facility (after a new Release) to rename local ISO directories & files - on demand.    −==Functionalities==+=== Functionalities ===     * GUI * GUI Line 72: Line 72:  * Provides a tool for Release changes, i.e. renaming directories and files with the new name. * Provides a tool for Release changes, i.e. renaming directories and files with the new name.    −==Installation==+=== Installation ===     An RPM package '''mageiasync''' is available for Mageia 5 and later. An RPM package '''mageiasync''' is available for Mageia 5 and later.    −==Usage==+=== Usage ===     To launch it, there is a menu entry "MageiaSync" under System Tools. From a console, simply type:<BR> To launch it, there is a menu entry "MageiaSync" under System Tools. From a console, simply type:<BR>    $ mageiasync   $ mageiasync    −=== First launch ===+==== First launch ====     At first launch, you have to give some information. A ''Preferences'' dialogue asks for: At first launch, you have to give some information. A ''Preferences'' dialogue asks for: Line 109: Line 109:  Clicking ''OK'' leads to the main dialogue below. Clicking ''OK'' leads to the main dialogue below.    −== Regular use: the main window ==+=== Regular use: the main window ===     This appears directly for any subsequent use of Mageiasync, using the pre-defined information to display immediately all that is required to 'synchronise' your current ISO set. This appears directly for any subsequent use of Mageiasync, using the pre-defined information to display immediately all that is required to 'synchronise' your current ISO set. Line 123: Line 123:  [[File:Mageiasync5.png]] [[File:Mageiasync5.png]]    −=== When the Release changes ===+==== When the Release changes ====     At a new release, all your local ISO directory and subordinate filenames ''must'' be updated to be the same as their new equivalents on the server. From the menus, ''Sync-> Rename archives'' At a new release, all your local ISO directory and subordinate filenames ''must'' be updated to be the same as their new equivalents on the server. From the menus, ''Sync-> Rename archives'' Line 147: Line 147:  * If you already have old versions it only transfers the difference * If you already have old versions it only transfers the difference  * Checksums the *.iso image files. * Checksums the *.iso image files. −* Can create bootable USB sticks both after synchronisation, and independently.+* Can create bootable USB sticks both without downloading first, after download or synchronisation, and from downloaded files.     === Installation and configuration === === Installation and configuration ===    −dorsync is now packaged as mga-dorsync. In Mageia 9 it is in core updates repos (at time of writing 2025-12-17 in updates_testing)+{{prog|dorsync}} is now packaged as mga-dorsync. In Mageia 9 it is in core updates repos (at time of writing 2025-12-17 in updates_testing)    −Let it create the config file by running it:+Let it create the config file (if it does not exist already) by running it:    <nowiki>   <nowiki>  $ dorsync   $ dorsync   Line 262: Line 262:  </nowiki> </nowiki>    −Note that you have to edit do this ''at every Release change'' to reflect the new ISO directory names.+As you see, the files to download are prepended by a "+". You can edit it as you like, and even create it before running dorsync the first time if you like.  +   +Note that you have to edit this file ''at every Release change'' to reflect the new ISO directory names.    −=== Release changes ===+=== When the Release changes ===  Dorsync can update files in place, provided they have the new name. Dorsync can update files in place, provided they have the new name.  Before using dorsync for the new Release, you ''must''   Before using dorsync for the new Release, you ''must''   Line 273: Line 275:  where <Release> is e.g. ''mageia10-alpha1''. where <Release> is e.g. ''mageia10-alpha1''.    −= Onesync =+== Onesync ==     This command line ISO synchronisation script is quite different from the previous tools. It is aimed at people who, while they may *test* several ISOs, find synchronising one at a time quite enough - because of a slow Internet connection, for example. ({{prog|Mageiasync}} is great for this too). It demands almost no user pre-definition or data input, working dynamically & interactively with what it finds on the server. Broadly, for the preceding tools you define the ''rsync'' remote source & local destination directories, which they subsequently use for speedy action. {{prog|Onesync}} has no such memory; you give it the local destination ISO directory as its parameter, then steer it to the equivalent remote source ISO. This command line ISO synchronisation script is quite different from the previous tools. It is aimed at people who, while they may *test* several ISOs, find synchronising one at a time quite enough - because of a slow Internet connection, for example. ({{prog|Mageiasync}} is great for this too). It demands almost no user pre-definition or data input, working dynamically & interactively with what it finds on the server. Broadly, for the preceding tools you define the ''rsync'' remote source & local destination directories, which they subsequently use for speedy action. {{prog|Onesync}} has no such memory; you give it the local destination ISO directory as its parameter, then steer it to the equivalent remote source ISO. Line 284: Line 286:  It is verbose and cautious, outputting a lot of information about both ends and seeking confirmation that you are where, and seeing what, you expect. It is verbose and cautious, outputting a lot of information about both ends and seeking confirmation that you are where, and seeing what, you expect.    −===Features===+=== Features ===     * Normally only the rsync password to maintain. * Normally only the rsync password to maintain. Line 295: Line 297:  * Checksums the *.iso image file. * Checksums the *.iso image file.    −===Installation===+=== Installation ===     It is downloadable from https://bugs.mageia.org/attachment.cgi?id=11685&action=edit It is downloadable from https://bugs.mageia.org/attachment.cgi?id=11685&action=edit Line 301: Line 303:  $ chmod a+x onesync $ chmod a+x onesync    −===Changeable information===+=== Changeable information ===       <nowiki>   <nowiki> Line 315: Line 317:  You *must* define RSYNC_PASSWORD appropriately - by editing the script. That normally is all. You *must* define RSYNC_PASSWORD appropriately - by editing the script. That normally is all.    −==Usage==+=== Usage ===    <nowiki>   <nowiki>  # onesync -h | DIR # onesync -h | DIR Line 373: Line 375:  Nothing for you to change. The new Release will show up ''automatically'' for you to select. When ''onesync'' spots that filenames have changed, it will - with your confirmation - ''rename all the local ISOs files to be the same as their corresponding ones on the server''. [Note that this is a blind transformation, with no knowledge of the complex filename format other than their extensions]. You will be shown the revised local ISO directory contents for information, before the synchronisation. Nothing for you to change. The new Release will show up ''automatically'' for you to select. When ''onesync'' spots that filenames have changed, it will - with your confirmation - ''rename all the local ISOs files to be the same as their corresponding ones on the server''. [Note that this is a blind transformation, with no knowledge of the complex filename format other than their extensions]. You will be shown the revised local ISO directory contents for information, before the synchronisation.    −= Rsync directly =+== Rsync directly ==     Rsync is extremely clever, but difficult to drive to get the results you want. One '/', '.' '*' or command option can change the outcome radically. Extracts from its man page: Rsync is extremely clever, but difficult to drive to get the results you want. One '/', '.' '*' or command option can change the outcome radically. Extracts from its man page: Morgano

← Older revision Revision as of 13:01, 17 December 2025 Line 7: Line 7:     which will store them in {{Folder|./usr/lib64/drakx-installer-images/install}} (creating the necessary directory tree on the way). which will store them in {{Folder|./usr/lib64/drakx-installer-images/install}} (creating the necessary directory tree on the way).  +  +The rpm built contains the .iso.     When submitting to the build system, you need to submit twice to build both the free and non-free versions by When submitting to the build system, you need to submit twice to build both the free and non-free versions by Bcornec

‎Dorsync

Show changes Morgano

Created page with "Category:Development This article describes how the netinstall boot images are generated and how to produce them locally. You need to build the {{File|drakx-installer-ima..."

New page

[[Category:Development]]
This article describes how the netinstall boot images are generated and how to produce them locally.

You need to build the {{File|drakx-installer-images}} package. It has a build option to choose between the ''free'' and ''non-free'' versions. Once built, you can either install the package, which will put the files in {{Folder|/usr/lib64/drakx-installer-images/install}}, or just extract the files using

rpm2cpio drakx-installer-images-<version>.rpm | cpio -id

which will store them in {{Folder|./usr/lib64/drakx-installer-images/install}} (creating the necessary directory tree on the way).

When submitting to the build system, you need to submit twice to build both the free and non-free versions by

mgarepo submit --define section=core/release
mgarepo submit --define section=nonfree/release

The build system remembers the last section used, so don't assume core/release is the default.

The build system automatically extracts the files when the package is uploaded and puts them in the images directory in the distrib tree. Papoteur