Lector de Feeds

‎Contact the team: IRC howto sentence

← Older revision Revision as of 09:14, 17 January 2025 Line 16: Line 16:     * Subscribing to the [https://ml.mageia.org/l/info/qa-discuss QA-Discuss] mailing list and then send a mail message to it, to introduce yourself * Subscribing to the [https://ml.mageia.org/l/info/qa-discuss QA-Discuss] mailing list and then send a mail message to it, to introduce yourself −* By joining the [irc://irc.libera.chat/#mageia-qa #mageia-qa] IRC channel on libera.chat+* By joining the [irc://irc.libera.chat/#mageia-qa #mageia-qa] IRC channel on libera.chat. How: web browser using https://web.libera.chat/, or an IRC client such as for example {{prog|hexchat}} : choose network Libera.Chat, and menu Server > Join a channel > #mageia-qa     * Team  leader : Thomas J Andrews (MageiaTJ) - andrewsfarm AT gmail dot com * Team  leader : Thomas J Andrews (MageiaTJ) - andrewsfarm AT gmail dot com Morgano

Publication date: 16 Jan 2025
Type: security
Affected Mageia releases : 9
CVE: CVE-2024-56826 , CVE-2024-56827 Description Heap buffer overflow in bin/common/color.c. (CVE-2024-56826) Heap buffer overflow in lib/openjp2/j2k.c. (CVE-2024-56827) References

• https://bugs.mageia.org/show_bug.cgi?id=33905
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AWMGURRKWFOTMCKEBHYWF7HHDJSY7BTR/
• https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/message/XKBM37J7PMJ763EKO4IP3FLOLF4U26HW/
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56826
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56827

SRPMS 9/core

• openjpeg2-2.5.0-1.2.mga9

Publication date: 16 Jan 2025
Type: bugfix
Affected Mageia releases : 9
Description curl update that addresses a .netrc related issue that breaks git. References

• https://bugs.mageia.org/show_bug.cgi?id=33893
• https://github.com/curl/curl/issues/15496

SRPMS 9/core

• curl-7.88.1-4.6.mga9

Publication date: 16 Jan 2025
Type: bugfix
Affected Mageia releases : 9
Description Performances enhancements and other changes since our current version, References

• https://bugs.mageia.org/show_bug.cgi?id=33887
• https://developer.nvidia.com/blog/nvidia-cuda-toolkit-12-2-unleashes-powerful-features-for-boosting-applications/
• https://developer.nvidia.com/blog/cuda-toolkit-12-4-enhances-support-for-nvidia-grace-hopper-and-confidential-computing/

SRPMS 9/nonfree

• nvidia-cuda-toolkit-samples-bins-12.4.1-1.mga9.nonfree
• nvidia-cuda-toolkit-12.4.1-1.mga9.nonfree
• cuda-z-0.11.291-11.mga9.nonfree

Figured I'd post an update on how things are going with the new laptop (HP Omnibook Ultra 14, AMD Ryzen AI 9 365 "Strix Point", for the searchers) and with Silverblue.

I managed to work around the hub issue by swapping out the fancy $300 Thunderbolt hub for a $40 USB-C hub off Amazon. This comes with limitations - you're only going to get a single 4k 60Hz external display, and limited bandwidth for anything else - but it's sufficient for my needs, and makes me regret buying the fancy hub in the first place. It seems to work 100% reliably on startup, reboot and across suspend/resume. There's still clearly something wrong with Thunderbolt handling in the kernel, but it's not my problem any more.

The poor performance of some sites in Firefox turned out to be tied to the hanging problem - I'd disabled graphics acceleration in Firefox, which helped with the hanging, but was causing the appalling performance on Google sites and others. I've now cargo-culted a set of kernel args - amdgpu.dcdebugmask=0x800 amdgpu.lockup_timeout=100000 drm.vblankoffdelay=0 - which seem to be helping; I turned graphics acceleration back on in Firefox and it hasn't started hanging again. At least, I haven't had random hangs for the last few days, and this morning I played a video on youtube and the system has not hung since then. I've no idea how bad they are for battery life, but hey, they seem to be keeping things stable. So, the system is pretty workable at this point. I've been using it full-time, haven't had to go back to the old one.

I'm also feeling better about Silverblue as a main OS this time. A lot of things seem to have got better. The toolbox container experience is pretty smooth now. I managed to get adb working inside a container by putting these udev rules in /etc/udev/rules.d. It seems like I have to kill and re-start the adb server any time the phone disconnects or reboots - usually adb would keep seeing the phone just fine across those events - but it's a minor inconvenience. I had to print something yesterday, was worried for a moment that I'd have to figure out how to get hp-setup to do its thing, but then...Silverblue saw my ancient HP printer on the network, let me print to it, and it worked, all without any manual setup at all. It seems to be working over IPP, but I'm a bit surprised, as the printer is from 2010 or 2011 and I don't think it worked before. But I'm not complaining!

I haven't had any real issues with app availability so far. All the desktop apps I need to use are available as flatpaks, and the toolbox container handles CLI stuff. I'm running Firefox (baked-in version), Evolution, gedit, ptyxis (built-in), liferea, nheko, slack and vesktop (for discord) without any trouble. LibreOffice and GIMP flatpaks also work fine. Everything's really been pretty smooth.

I do have a couple of tweaks in my bashrc (I put them in a file in ~/.bashrc.d, which is a neat invention) that other Atomic users might find useful...

if [ -n "$container" ] then alias gedit="flatpak-spawn --host /var/lib/flatpak/exports/bin/org.gnome.gedit" alias xdg-open=flatpak-xdg-open else alias gedit=/var/lib/flatpak/exports/bin/org.gnome.gedit fi

the gedit aliases let me do gedit somefile either inside or outside a container, and the file just opens in my existing gedit instance. Can't really live without that. You can adapt it for anything that's a flatpak app on the host. The xdg-open alias within containers similar makes xdg-open somefile within the container do the same as it would outside the container.

So it's still early days, but I'm optimistic I'll keep this setup this time. I might try rebasing to the bootc build soon.

Escrito por el Equipo Atelier

Esto ha sido rápido, hace poco explicamos el motivo por el cual nuestra Base de Datos de Aplicaciones Mageia está fuera de servicio y ahora papoteur nos confirma que el nuevo MADb está listo.

Al abrir el sitio, la primera impresión será de que se ha conectado a la anterior versión del sitio, ya que la diferencias entre ambos son difíciles de notar (la primera imagen es del sitio anterior):

Pero eso solo es en apariencia, ya que las hojas de estilo (CSS) usadas tienen pocas modificaciones.

La herramienta anterior estaba escrita en PHP, ha sido completamente escrita desde cero utilizando Python, Flask, Jinja2 y DNF5. Papoteur mostró dos fragmentos de código como ejemplo de lo que ha cambiado (nuevamente el primero es de la versión anterior):

¡La diferencia es tanta como la de una página de un libro en Inglés comparada con una de un libro en Indonesio!

Se escribieron cerca de 3000 líneas de código para este nuevo MADb, que ahora está activo y listo para responder a sus búsquedas sobre aplicaciones de Mageia.

Les pedimos que mientras usen el sitio piensen sobre qué preguntas debería responder la función de ayuda integrada (aún no disponible), y también sobre lo que debería incluirse en la nueva página sobre MADb en el wiki. Por favor deje sus sugerencias en los comentarios en la versión en inglés del artículo, esta herramienta es para todos ustedes que hacen la comunidad de Mageia.

Un agradecimiento a la comunidad MLO por hospedar el nuevo MADb.

Traducido por katnatek de la publicación original de marja

Written by Atelier Team

That was fast: we have only just explained why our Mageia Application Database was offline and now papoteur tells us that new MADb is ready to be used.

Open the site and at first glance you might think you have somehow connected to the old site as the differences between it and the new one are hard to spot (the top one is the old site):

However, this is only the outward appearance, as the style sheets (CSS) were re-used with little modification.

The tool itself, previously written in PHP, has been completely rewritten from scratch, using Python, Flask, Jinja2 and DNF5, so the runtime code is entirely new. Papoteur showed two code snippets as an example of what really changed (again, the top one is old):

That is as different as a page from an English book compared to a page from its Indonesian translation!

About 3000 new lines of code were written for this new MADb, which is now live and ready to answer your queries about Mageia applications.

As you use the site, we ask you to think about what questions you feel an integrated help function (not yet available) should answer, and also what you feel we should include in a new wiki article about MADb. Please note your suggestions in the comments to this post, as you are all the Mageia community and this tool is for you.

Thanks to the MLO community for hosting new MADb.

ACTUALIZACIÓN: Ahora es posible visitar el nuevo MADb en https://madb.mageialinux-online.org/ , tomará algo más de tiempo que https://madb.mageia.org/ nos lleve ahí.

Escrito por aguador.

En Mageia, MADb, (Mageia App Db/Base de datos de Aplicaciones Mageia), ha sido una herramienta esencial, en particular para el equipo QA (Control de Calidad). es el sitio al cual dirigirse por información de aplicaciones en nuestros repositorios, con enlaces a reportes de fallos, importancia de las actualizaciones, comparación de versiones y más. Se puede buscar por versiones de Mageia, arquitectura de CPU, el sitio ha sido clave no solo para desarrolladores y QA, también para muchos usuarios que han encontrado en el una alternativa a nuestro CCM o la línea de comandos para la búsqueda de paquetes para hacer “lo que sea”.

Pero, “Houston, tenemos un problema.” Al dirigirse a MADb (https://madb.mageia.org/) ¡será redirigido a la versión en inglés de este artículo!

MADb no fue afectado por el traslado de los servidores de Mageia que fue anunciado anteriormente en este blog (https://blog.mageia.org/es/2024/10/08/la-mayoria-de-nuestros-servidores-estaran-fuera-de-linea-debido-a-su-traslado/), ya que al haber sido desarrollado años atras por dos de nuestros contribuidores, se encontraba en un sitio diferente. Mageia se hizo cargo del servidor rentado hace unos meses. Desafortunadamente, el servidor falleció, y debido a que la tecnología tras la anterior versión de MADb es incompatible con las nuevas infraestructuras (en especial con versiones recientes de php), no pudo ser regresado tal cual estaba. Sin embargo, no todo está perdido.

En abril, papoteur había enviado su trabajo inicial de una nueva versión de MADb para su evaluación, y desde entonces ha recibido numerosas revisiones y mejoras. Pero aún permanece “oculta” pata la mayoría de los usuarios, hasta que todos, pero en particular papoteur, estén seguros de que no solamente es una interfaz sólida, sino que además es mejor que nunca.

Dado que MADb ha desempeñado tan vital papel en Control de Calidad, la versión en desarrollo está disponible solo para los miembros del equipo QA y otros revisores. Es justo que ellos tengan la primicia de su uso dado todo el trabajo que han realizado para asegurarse de que Mageia siga siendo una distro de calidad. El resto de nosotros solo necesitamos tener un poco más de paciencia.

Y no olvidemos que además del traslado exitoso de los servidores, los servicios que fueron afectados están funcionando nuevamente, esperen más buenas noticias sobre nuestros servidores próximamente. Además, la mayoría de los espejos de Mageia (hospedados en servidores externos que no están bajo nuestro control) están en buen estado.

Traducido por katnatek de la publicación original de marja

UPDATE: It is now possible to visit the new MADb here https://madb.mageialinux-online.org/. It will take a bit longer for https://madb.mageia.org/ to link to it.

Written by aguador.

In Mageia, MADb, the Mageia App Db, has been an essential tool, particularly for QA (Quality Assurance) testers. It is the goto site for information on applications in our repositories with links to bug reports, priorities for updates, version comparisons and more. Searchable by Mageia version and CPU architecture, the site has not only been key for developers and testers, but many users as well who have found it an alternative to searching with our MCC control center or the command line when looking for a package to do (“whatever”).

But, er, “Houston, we have a problem.” If I go to MADb (https://madb.mageia.org/) all I got was the error message below and now a redirect to this post!

MADb was not affected by the move of Mageia’s servers announced on this blog (https://blog.mageia.org/en/2024/10/08/most-of-our-servers-will-be-offline-because-they-are-relocating/) early this month because it was originally developed by two of our contributors many years ago, and running on a different server. Mageia.Org took over ownership of their rented server a few months ago. Unfortunately, that server passed away and since the technology behind the old MADb is not compatible with newer infrastructure (mostly newer php-version), we cannot bring it back as it was. However, not all was lost!

Back in April, papoteur had submitted his initial work on a new version of MADb for testing…and since then it has undergone numerous revisions and improvements. However, it still remains “under wraps” for most users (like the author of this post!) until everyone, above all papoteur, is satisfied that it is not only a solid db interface for users, but is even better than before.

Since MADb has played such a vital role in testing, the development version is available to the QA team and other testers. It is only fair that they get the first look and use given all the work they do to assure that Mageia remains a quality distro. The rest of us simply need a bit more patience.

Ah, and not to forget the servers, not only was the move successful, with the other services affected now back up and running smoothly, but we expect to announce more good news about our servers, soon. Apart from that, most Mageia mirrors are in a good shape (they are all hosted on external servers, which we do not control).

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.