Lector de Feeds

‎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

portableapps -- javascripts

← Older revision Revision as of 08:42, 17 December 2025 Line 158: Line 158:     No programming needed. Maybe just pass some parameters to kernel to cache more an write more lazy, maybe setting in fstab, though I am not sure if that really works on Live.  Backside of course is that the more we delay writes, the mare are lost and also more risk of filesystem failure if power are cut or the USB suddenly is plugged put.  https://www.ecosia.org/search?q=disk+write+cache+linux gives some ideas.  Firefox is slow to even launch also on my Thinkpad T3, single core 32 bit with spinning disk.  I have tried light weight browsers, Falkon and some other, but they do not work at all on that system (if I and packagers had more people I would have raised bugs). No programming needed. Maybe just pass some parameters to kernel to cache more an write more lazy, maybe setting in fstab, though I am not sure if that really works on Live.  Backside of course is that the more we delay writes, the mare are lost and also more risk of filesystem failure if power are cut or the USB suddenly is plugged put.  https://www.ecosia.org/search?q=disk+write+cache+linux gives some ideas.  Firefox is slow to even launch also on my Thinkpad T3, single core 32 bit with spinning disk.  I have tried light weight browsers, Falkon and some other, but they do not work at all on that system (if I and packagers had more people I would have raised bugs).  +----  +32bit is a problem nowadays. We have a 32bit Microsoft Windows system -- portableapps has 32bit versions of programs for Microsoft Windows, maybe you can find some cross platform tools there.  +  +I use SeaMonkey with javascripts disabled by default, and open another browser (maybe with "firejail --private") when I must use javascripts. I just skip most sites that need javascripts -- there are plenty of fish in the ocean.  +  +[[User:Nikos5446]] Nikos5446

Introduction

Hi there, blog readers! For the last week or so I've been poking into AI code review tools. Yes, this is partly because of the Red Hat "you must do AI things!" policy. But also, to be honest, because they seem to be...actually good now. I set up AI reviews for pull requests to our openQA test repo as an experiment. But especially over the last couple of months, they've got to the point where well over half of the review notes are actually useful, and the writing style isn't so awful I want to stab myself in the eyeballs. So I'd quite like to keep doing them, but in a more open source-y way. So far I've simply been cloning the pull requests to a GitHub mirror of the repo that exists solely to get AI reviews done. That repo has Gemini Code Assist enabled so the PRs are reviewed by Gemini automatically, e.g. here. It's very simple, but entirely closed source, there's no control over it, and Google could take it away at any time.

We're in the middle of migrating Fedora projects from Pagure to our new Forgejo instance, so I decided to try and get some sort of AI review system integrated with Forgejo. And I kinda succeeded! I wrote a Forgejo integration for ai-code-review, a tool I found that was written by another Red Hatter, and managed to set up a proof-of-concept Forgejo Actions workflow using it on a repo I own that's hosted at Codeberg (since Codeberg has public Forgejo Actions runners available; we don't have Actions entirely set up in the Fedora instance yet). Right now it's using Gemini as the model provider just because that was the easiest thing to set up for a PoC, but ai-code-review's design makes the LLM provider easily pluggable, so it's trivial to swap it out. Long term I hope we'll get a Fedora LLM provider set up, serving open source models, and we can make it use that. There's an Ollama backend, and adding an OpenAI API backend should be pretty easy.

Before going any further with that, though, I decided to look around and see if there are other tools out there, and if so, which might be the best one. I poked around a bit and found a few, and wrote up a very half-assed comparative assessment. I figured this might interest others, so I've prettied it up a tiny bit and put it below. I make no claims that this is comprehensive, accurate or fair, please send all complaints to the happyassassin.net HR department! The takeaway is that I'll probably keep working on the ai-code-review approach and also experiment with forking Qodo's archived open-source pr-agent project and see if I can add Forgejo support to it, to compare it against ai-code-review.

If anyone knows of any I missed, please let me know! I briefly looked at RhodeCode but discounted it because it's a whole-ass forge, not just a review tool. ReviewBoard doesn't seem to have any LLM integration as best as I could tell.

The Contenders ai-code-review

• Repo: https://gitlab.com/redhat/edge/ci-cd/ai-code-review
• Author: Juanje Ojeda (Red Hat)
• Language: Python (typed)
• Architecture: Modular
• Tests: Yes, LLM-generated, fairly comprehensive unit tests, very limited integration tests
• Begun: August 2025
• Status: Active
• Forges: GitLab, GitHub, local changes (Forgejo supported submitted)
• Model providers: Gemini, Anthropic, Ollama
• Output: Console or PR/MR comment
• Deployment: Local execution, GitLab CI, GitHub Actions (one-shot deployment via container image in CI job)
• Prompts: Here

ai-codereview

• Repo: Red Hat internal
• Author: Tuvya Korol (Red Hat)
• Language: Python (untyped)
• Architecture: Monolithic
• Tests: No
• Begun: June 2025
• Status: Active
• Forges: GitLab, local changes
• Model providers: RH-internal Claude, Gemini, Granite
• Output: Console or MR comment
• Deployment: Local execution, GitLab CI (ad hoc deployment via curl/pip in CI job)
• Prompts: Red Hat internal

kodus-ai

• Repo: https://github.com/kodustech/kodus-ai
• Author: Kodus
• Language: Typescript
• Architecture: Modular
• Tests: Yes, handwritten, unit and integration, not sure of coverage
• Begun: April 2025
• Status: Active
• Forges: GitHub, GitLab, BitBucket
• Model providers: OpenAI, Gemini, Anthropic, Novita, OpenRouter, any OpenAI-compatible
• Output: MR/PR comment and/or review (seems to depend on configuration)
• Deployment: Local via yarn (indicated as for development only), as containerized webapp (for prod) with own installer - looks complex
• Prompts: Here

pr-agent

• Repo: https://github.com/qodo-ai/pr-agent
• Author: Qodo (formerly Codium)
• Language: Python (untyped)
• Architecture: Modular
• Tests: Yes, handwritten, unit and integration, somewhat primitive, many commented out, 24% coverage (per codecov)
• Begun: July 2023
• Status: Archived (Nov 2025)
• Forges: GitHub, GitLab, Gitea, Gerrit, BitBucket, AWS CodeCommit, Azure DevOps, local changes
• Model providers: Any OpenAI-compatible (looks like some special handling for Azure), LiteLLM
• Output: MR/PR comment and/or review, has interactive features
• Deployment: Local execution or Forge CI. There's a custom GitHub action but it may be abandoned. Installable via pip, should be trivial to containerize for simple one-shot CI job deployment
• Prompts: Here

ai-pr-reviewer

• Repo: https://github.com/coderabbitai/ai-pr-reviewer
• Author: CodeRabbit
• Language: Typescript
• Architecture: Modular
• Tests: Barely any
• Begun: Feb 2023
• Status: Archived (Nov 2023)
• Forges: GitHub
• Model providers: OpenAI
• Output: PR review/comment
• Deployment: GitHub Action (no longer maintained). No generic or local deployment documented
• Prompts: Here

Conclusions

ai-code-review (Juanje) and pr-agent (Qodo/Codium) seem the best options.

Of the RH-developed, greenfield projects, ai-code-review is more featureful and better architected than ai-codereview, and not tied to an RH-internal model provider.

Of the existing public projects, ai-pr-reviewer (CodeRabbit) was very tied to GitHub, has no documented standalone deployment ability, and was archived fairly early in development. Plus it's in TypeScript. Kodus is actively developed, but similarly is in TypeScript, deployment looks complex, and from what I've seen I don't love its review style. Hard to say why but the project overall gives me a sloppy vibe. pr-agent (Qodo) had the longest development history and seems the most mature and capable at the point where it was abandoned (well, they actually seem to have done a heel turn and gone closed source / SaaS). It has a documented standalone deployment process which looks relatively simple and subject to integration into generic CI workflows.

← Older revision Revision as of 12:01, 16 December 2025 Line 154: Line 154:     [[User:Nikos5446]] [[User:Nikos5446]]  +----  +[[User:Morgano|morgano]] ([[User talk:Morgano|talk]]) 12:01, 16 December 2025 (UTC)  +  +No programming needed. Maybe just pass some parameters to kernel to cache more an write more lazy, maybe setting in fstab, though I am not sure if that really works on Live.  Backside of course is that the more we delay writes, the mare are lost and also more risk of filesystem failure if power are cut or the USB suddenly is plugged put.  https://www.ecosia.org/search?q=disk+write+cache+linux gives some ideas.  Firefox is slow to even launch also on my Thinkpad T3, single core 32 bit with spinning disk.  I have tried light weight browsers, Falkon and some other, but they do not work at all on that system (if I and packagers had more people I would have raised bugs). Morgano

opposite direction?

← Older revision Revision as of 09:25, 16 December 2025 Line 147: Line 147:     I wonder if it is  possible to implement a large write buffer, that dynamically use all free RAM to swallow writes and then write lazily to USB. I wonder if it is  possible to implement a large write buffer, that dynamically use all free RAM to swallow writes and then write lazily to USB.  +----  +  +> I wonder if it is  possible to implement a large write buffer...  +  +That would be far beyond my abilities (no programming knowledge whatsoever). Also, this is far beyond my time schedule. The opposite direction would be to write less: for example use a "mobile" User Agent for the browser that would direct the user to the "lighter" mobile version of a site. That type of tricks...  +  +[[User:Nikos5446]] Nikos5446

Publication date: 15 Dec 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-14321 , CVE-2025-14322 , CVE-2025-14323 , CVE-2025-14324 , CVE-2025-14325 , CVE-2025-14328 , CVE-2025-14329 , CVE-2025-14330 , CVE-2025-14331 , CVE-2025-14333 Description Use-after-free in the WebRTC: Signaling component. (CVE-2025-14321) Sandbox escape due to incorrect boundary conditions in the Graphics: CanvasWebGL component. (CVE-2025-14322) Privilege escalation in the DOM: Notifications component. (CVE-2025-14323) IT miscompilation in the JavaScript Engine: JIT component. (CVE-2025-14324, CVE-2025-14325, CVE-2025-14330) Privilege escalation in the Netmonitor component. (CVE-2025-14328, CVE-2025-14329) Same-origin policy bypass in the Request Handling component. (CVE-2025-14331) Memory safety bugs fixed in Firefox ESR 140.6, Thunderbird ESR 140.6, Firefox 146 and Thunderbird 146. (CVE-2025-14333) References

• https://bugs.mageia.org/show_bug.cgi?id=34820
• https://www.thunderbird.net/en-US/thunderbird/140.6.0esr/releasenotes/
• https://www.mozilla.org/en-US/security/advisories/mfsa2025-96/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14321
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14322
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14323
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14324
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14325
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14328
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14329
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14330
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14331
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14333

SRPMS 9/core

• thunderbird-140.6.0-1.mga9
• thunderbird-l10n-140.6.0-1.mga9

Publication date: 15 Dec 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2025-14321 , CVE-2025-14322 , CVE-2025-14323 , CVE-2025-14324 , CVE-2025-14325 , CVE-2025-14328 , CVE-2025-14329 , CVE-2025-14330 , CVE-2025-14331 , CVE-2025-14333 Description Use-after-free in the WebRTC: Signaling component. (CVE-2025-14321) Sandbox escape due to incorrect boundary conditions in the Graphics: CanvasWebGL component. (CVE-2025-14322) Privilege escalation in the DOM: Notifications component. (CVE-2025-14323) JIT miscompilation in the JavaScript Engine: JIT component. (CVE-2025-14324, CVE-2025-14325, CVE-2025-14330) Privilege escalation in the Netmonitor component. (CVE-2025-14328, CVE-2025-14329) Same-origin policy bypass in the Request Handling component. (CVE-2025-14331) Memory safety bugs fixed in Firefox ESR 140.6, Thunderbird ESR 140.6, Firefox 146 and Thunderbird 146. (CVE-2025-14333) References

• https://bugs.mageia.org/show_bug.cgi?id=34814
• https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/-FCacePkmj8
• https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/V7GVSScpn5w
• https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/qFuz87KunGc
• https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_118.html
• https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_118_1.html
• https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_119.html
• https://www.firefox.com/en-US/firefox/140.6.0/releasenotes/
• https://www.mozilla.org/en-US/security/advisories/mfsa2025-94/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14321
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14322
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14323
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14324
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14325
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14328
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14329
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14330
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14331
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-14333

SRPMS 9/core

• nspr-4.38.2-1.mga9
• nss-3.119.0-1.mga9
• firefox-140.6.0-1.mga9
• firefox-l10n-140.6.0-1.mga9

Publication date: 15 Dec 2025
Type: security
Affected Mageia releases : 9
Description Several vulnerabilities have been discovered in the FFmpeg multimedia framework, which could result in denial of service or potentially the execution of arbitrary code if malformed files/streams are processed. References

• https://bugs.mageia.org/show_bug.cgi?id=34832
• https://lists.debian.org/debian-security-announce/2025/msg00245.html

SRPMS 9/core

• ffmpeg-5.1.8-1.mga9

9/tainted

• ffmpeg-5.1.8-1.mga9.tainted

Publication date: 15 Dec 2025
Type: bugfix
Affected Mageia releases : 9
Description Current version has a bogus requirement on python3-sip. Current version misses a python3-lxml requirement. Current version crashes after downloading images. The updated package fixes the reported issues. References

• https://bugs.mageia.org/show_bug.cgi?id=34027
• https://github.com/dglent/sansimera-qt/issues/1

SRPMS 9/core

• sansimera-qt-1.1.0-1.3.mga9

← Older revision Revision as of 12:41, 15 December 2025 Line 55: Line 55:     User:ftg User:ftg  +  +User:geex     User:ghibo User:ghibo Papoteur