Lector de Feeds

‎A way forward: Improve clarity, fix typo

← Older revision Revision as of 17:35, 6 March 2025 Line 71: Line 71:  Overview: Overview:    −# Developer builds a package SRPM containing all application source code as well as any unpackaged dependency source code for an application (i.e. vendoring it), including a SBOM+# Developer builds a package SRPM containing all application source code as well as any unpackaged dependency source code needed by the application (i.e. vendoring it), including a SBOM for those dependencies −# The build system adds packaged dependencies to the SBOM+# The build system uses only locally-available source to build (as always) and adds a reference to the main source(s) to the SBOM, for completeness −# For interpreted languages, the build system puts any vendored code into a filesystem location specific to the application+# For interpreted languages, the build system puts any vendored code into a filesystem location specific to the application in the final RPM  # The build system stores the SBOM at the end of the build into a central repository # The build system stores the SBOM at the end of the build into a central repository  # A security scanner periodically scans all SBOMs to look for dependencies that have reported security vulnerabilities # A security scanner periodically scans all SBOMs to look for dependencies that have reported security vulnerabilities Line 81: Line 81:  SBOMs will be stored in the [https://spdx.dev/ SPDX] format. SBOMs will be stored in the [https://spdx.dev/ SPDX] format.    −Security updates are assumed to consist of upgrading to a new upstream release. Those that require patching a dependency complicates this flow, since the same patch must then be applied to each vendored instance of that dependency. If an unpackaged dependency needs a local patch instead of an upgrade, then we could implement a policy that the dependency much be first be packaged before rebuilds are performed, with that new package added as a dependency to any application that needs it before rebuilding. That avoids carrying the identical patch around in many packages.+Security updates are assumed to consist of upgrading to a new upstream release. Those that require patching a dependency complicates this flow, since the same patch must then be applied to each vendored instance of that dependency. If an unpackaged dependency needs a local patch instead of an upgrade, then we could implement a policy that the dependency must be first be packaged before rebuilds are performed, with that new package added as a dependency to any application that needs it before rebuilding. That avoids carrying the identical patch around in many packages.     A script will be created to take care of the bulk of step 1 for the developer. It would scan the application source code to find out what dependencies are needed, then exclude any dependencies already supplied by packages in ''BuildRequires:'' leaving a list of outstanding ones. These would be downloaded using the language's normal package download mechanism and installed into a private temporary location. All these would then be archived into a compressed tarball along with an SBOM containing all the packaged dependency names and versions and stored in the ''SOURCES/'' directory under a standard name (maybe ''dependencies.tar.xz'').  This file would then be added to ''sha1.lst'' and uploaded to ''binrepo''. This could all be integrated into a ''mgarepo'' subcommand. ''TODO: who is responsible for ensuring that the licenses of all the dependencies are allowed, compatible and that the License: line in the .spec file matches?'' A script will be created to take care of the bulk of step 1 for the developer. It would scan the application source code to find out what dependencies are needed, then exclude any dependencies already supplied by packages in ''BuildRequires:'' leaving a list of outstanding ones. These would be downloaded using the language's normal package download mechanism and installed into a private temporary location. All these would then be archived into a compressed tarball along with an SBOM containing all the packaged dependency names and versions and stored in the ''SOURCES/'' directory under a standard name (maybe ''dependencies.tar.xz'').  This file would then be added to ''sha1.lst'' and uploaded to ''binrepo''. This could all be integrated into a ''mgarepo'' subcommand. ''TODO: who is responsible for ensuring that the licenses of all the dependencies are allowed, compatible and that the License: line in the .spec file matches?'' Danf

zekemx

← Older revision Revision as of 14:39, 5 March 2025 Line 227: Line 227:  | joselp || papoteur,mokraemer || {{yes|Done}} ||  || {{yes|Done}} ||  ||  ||  ||  ||  || photomontage ||   | joselp || papoteur,mokraemer || {{yes|Done}} ||  || {{yes|Done}} ||  ||  ||  ||  ||  || photomontage ||    |- |- −| zekemx || kekepower || {{yes|Done}} ||  || ||  ||  || 1. conky ||  ||  || displaylink ||+| zekemx || kekepower || {{yes|Done}} ||  || ||  ||  || 1. conky ||  ||  || displaylink<br>new-lg4ff<br>oversteer ||  |} |}    Papoteur

Nocomprendo

← Older revision Revision as of 08:45, 5 March 2025 Line 344: Line 344:     Knotes has been replaced by Marknote. This one include a path for [https://blogs.kde.org/2024/06/28/marknote-1.3/#switching-to-marknote importing the notes]. Knotes has been replaced by Marknote. This one include a path for [https://blogs.kde.org/2024/06/28/marknote-1.3/#switching-to-marknote importing the notes].  +  +NoComprendo is a tools for voice recognition, including control of the desktop and dictation. It now uses Vosk libraries and models.     === Internet apps === === Internet apps === Papoteur

‎Games: Link to list needs to get fixed!

← Older revision Revision as of 12:45, 4 March 2025 (One intermediate revision by the same user not shown)Line 287: Line 287:  ==== LXDE ==== ==== LXDE ====    −The very lightweight GTK+3-based desktop environment is still available and continues to receive improvements from upstream and our Mageia maintainer, even though its community has partly refocused on LXQt.  Starting with Mageia 10, LXDE migrated from GTK+2 to GTK+3.  LXDE cannot use PipeWire as sound server, only PulseAudio. Now Srain is the IRC client installed instead of Hexchat.+This very lightweight GTK+3-based desktop environment is still available and continues to receive improvements from upstream and our Mageia maintainer, even though its community has partly refocused on LXQt.  Starting with Mageia 10, LXDE migrated from GTK+2 to GTK+3.  LXDE cannot use PipeWire as sound server, only PulseAudio. Now Srain is the IRC client installed instead of Hexchat.     LXDE can be installed from the Classical DVD ISO (traditional installer). LXDE can be installed from the Classical DVD ISO (traditional installer). Line 365: Line 365:  === Games === === Games ===    −In the Mageia community, our love for free software extends to open source games. A huge effort has been made during the Mageia 10 release cycle to package many new games, making Mageia 10 a very good platform for intensive and casual gamers alike. You can check the Mageia App DB to see a list of [https://madb.mageia.org/package/comparison/release/9/withrelease/10/group/78%2C20%2C64%2C10%2C30%2C46%2C109%2C138%2C74%2C1 all the new and updated games in Mageia 10]. <!--The following section will only give some cherry-picked examples for each game category.--> Also see [[Ways_to_install_programs#Game_environments_.28and_some_apps_too.29|Game environments]].+In the Mageia community, our love for free software extends to open source games. A huge effort has been made during the Mageia 10 release cycle to package many new games, making Mageia 10 a very good platform for intensive and casual gamers alike. You can check the Mageia App DB to see a list of [https://madb.mageia.org/package/comparison/release/9/withrelease/10/group/78%2C20%2C64%2C10%2C30%2C46%2C109%2C138%2C74%2C1 '''(FIXME!)''' all the new and updated games in Mageia 10]. <!--The following section will only give some cherry-picked examples for each game category.--> Also see [[Ways_to_install_programs#Game_environments_.28and_some_apps_too.29|Game environments]].     === Education === === Education === Morgano

‎LXDE

← Older revision Revision as of 10:24, 4 March 2025 Line 287: Line 287:  ==== LXDE ==== ==== LXDE ====    −The very lightweight GTK+3-based desktop environment is still available and continues to receive improvements from upstream and our Mageia maintainer, even though its community has partly refocused on LXQt.  Starting with Mageia 10, LXDE migrated from GTK+2 to GTK+3.  LXDE cannot use PipeWire as sound server, only PulseAudio.+The very lightweight GTK+3-based desktop environment is still available and continues to receive improvements from upstream and our Mageia maintainer, even though its community has partly refocused on LXQt.  Starting with Mageia 10, LXDE migrated from GTK+2 to GTK+3.  LXDE cannot use PipeWire as sound server, only PulseAudio. Now Srain is the IRC client installed instead of Hexchat.     LXDE can be installed from the Classical DVD ISO (traditional installer). LXDE can be installed from the Classical DVD ISO (traditional installer). Papoteur

To do a good job, we need good tools. Some of our servers are old, no longer powerful enough and have limited disk resources to meet the needs of developers. RPM manufacturing takes a long time and this is detrimental to the efficiency of maintaining and evolving the distribution. In short, the machines are well depreciated.

This is why our infrastructure is first getting a makeover. Better adapted to new technologies, it will allow our developers to work faster and more efficiently.

So where is this new infrastructure?

 We received 5 new servers:

– 2 new nodes for building packages: HPE ProLiant DL 360 Gen10 – 2xXeon 6126 (12C/2.6GHz) –

256GB RAM – 2xSSD 3.8TB HW Raid 1 – 2x10Gb/s NICs

– 2 servers to replace sucuk and duvel: HPE ProLiant DL 380 Gen10 – 2 Xeon 6126 (12C/2.6GHz) –

256GB RAM – 2xSSD 3.8TB HW Raid 1 – 10xHDD 12TB HW Raid 5 – 2x10Gb/s NICs

– 1 server for deployment and backup: HPE ProLiant DL80 Gen9 – 2xXeon  E5-2603v4

(6C/1.7GHz) – 256GB RAM – 6xHDD 6TB (donated, with some renewed parts)

– 1 Arista 7120T switch 20xRJ-45 10Gb/s 4xSFP+ 10Gb/s for interconnecting the machines

One of the ideas is to use the latest server to deploy quickly and as automatically as possible the construction nodes and other machines. The method is ready for x86_64 nodes and is being finalized for ARM nodes. The preparation of the servers takes time because the teams anticipate the future and future developments.

Once the preparation part of our servers is finished, the integration part into the Data Center will remain.

We are therefore taking our time to do things well in order to perpetuate the future and future versions of Mageia.

In the meantime, the future version 10 of Mageia continues to bubble in its cauldron! But we are not ready yet to plan a release date for the moment.

Feel free to come and strengthen our teams.

Para hacer un buen trabajo, necesitamos buenas herramientas. Algunos de nuestros servidores son viejos, ya no son lo bastante potentes y tienen recursos de disco limitados para satisfacer las necesidades de los desarrolladores. Se tarda mucho en producir los RPM, lo que va en detrimento de la eficacia del mantenimiento y la actualización de la distribución. En resumen, las máquinas están bien amortizadas.

Es por eso que nuestra infraestructura está recibiendo un lavado de cara. Más adaptada a las nuevas tecnologías, permitirá a nuestros desarrolladores trabajar de forma más rápida y eficaz. ¿Cuál es el estado de esta nueva infraestructura? Hemos recibido 5 nuevos servidores:

· 2 nuevos nodos de construcción de paquetes: HPE ProLiant DL 360 Gen10 – 2xXeon 6126 (12C/2.6GHz) – 256GB RAM – 2xSSD 3.8TB HW Raid 1 – 2x10Gb/s NICs.

· 2 servidores para reemplazar sucuk y duvel: HPE ProLiant DL 380 Gen10 – 2 Xeon 6126 (12C/2.6GHz) – 256GB RAM – 2xSSD 3.8TB HW Raid 1 – 10xHDD 12TB HW Raid 5 – 2x10Gb/s NICs.

· 1 servidor de despliegue y copia de seguridad: HPE ProLiant DL80 Gen9 – 2xXeon E5-2603v4 (6C/1.7GHz) – 256GB RAM – 6xHDD 6TB (una donación, con algunas partes renovadas)

· 1 switch Arista 7120T 20xRJ-45 10Gb/s 4xSFP+ 10Gb/s para interconectar las máquinas.

El plan es utilizar el último servidor para desplegar los nodos de construcción y el resto de máquinas de forma rápida y lo más automática posible. El método está listo para los nodos x86_64 y se está ultimando para los nodos ARM (servidores remotos). La preparación de los servidores lleva su tiempo, ya que nuestros equipos se anticipan al futuro y a los futuros desarrollos.

Una vez finalizada la preparación de nuestros servidores, el siguiente paso será integrarlos en el Centro de Datos. Por lo tanto, nos estamos tomando nuestro tiempo para hacer las cosas bien y poder asegurar el futuro y las futuras versiones de Mageia. Por el momento, no publicamos una fecha de lanzamiento provisional para Mageia 10.

Mientras tanto, ¡la futura versión 10 de Mageia sigue burbujeando en su caldero!

No dudes en unirte a nuestros equipos.

In Mageia/9/x86_64: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/9/aarch64: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/9/armv7hl: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/9/i586: Mesa is an OpenGL 4.6 compatible 3D graphics library.

In Mageia/cauldron/x86_64: Rachota is a portable application for timetracking different projects. It runs everywhere. It displays time data in diagram form, creates customized reports and invoices or analyses measured data and suggests hints to improve user's time usage. The totally portable yet personal timetracker.

In Mageia/cauldron/i586: Rachota is a portable application for timetracking different projects. It runs everywhere. It displays time data in diagram form, creates customized reports and invoices or analyses measured data and suggests hints to improve user's time usage. The totally portable yet personal timetracker.

In Mageia/cauldron/i586: A program to convert images from PPM format into the control language for the Alps Micro-Dry printers, at various times sold by Citizen, Alps and Okidata. This program drives the Alps Micro-Dry series of printers, including the Citizen Printiva series, Alps MD series, and Oki DP series (but not yet the DP-7000). In the current release, the program drives the standard mode fairly well; the dye sublimation mode very well; and the VPhoto mode reasonably well. It supports all the colours available up to the DP-5000, including the foil colours.

In Mageia/cauldron/x86_64: A program to convert images from PPM format into the control language for the Alps Micro-Dry printers, at various times sold by Citizen, Alps and Okidata. This program drives the Alps Micro-Dry series of printers, including the Citizen Printiva series, Alps MD series, and Oki DP series (but not yet the DP-7000). In the current release, the program drives the standard mode fairly well; the dye sublimation mode very well; and the VPhoto mode reasonably well. It supports all the colours available up to the DP-5000, including the foil colours.

In Mageia/cauldron/x86_64: This tool tries to recover JFIF (JPEG) pictures and MOV movies (using recovermov) from a peripheral. This may be useful if you mistakenly overwrite a partition or if a device such as a digital camera memory card is bogus.