![[Valid RSS]](images/valid-rss.png "Valid RSS")
This is a valid RSS feed.
This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
line 3454, column 0: (8 occurrences) [help]
<svg height="12" width="12" xmlns="http://www ...
<?xml version="1.0"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns="http://purl.org/rss/1.0/"><channel rdf:about="https://fedoraproject.org/people/"> <title>Fedora People</title> <link>https://fedoraproject.org/people/</link> <description>Fedora People: http://fedoraplanet.org</description> <items> <rdf:Seq> <rdf:li rdf:resource="http://opensourcesecurity.io/?p=3372" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13612" /> <rdf:li rdf:resource="urn:md5:7626749cb59451b4d7832dc5e3a55972" /> <rdf:li rdf:resource="https://blog.kulakowski.fr/?p=30412" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13590" /> <rdf:li rdf:resource="urn:md5:b8572562648cde62eb706456bd5ffec6" /> <rdf:li rdf:resource="https://major.io/p/java-big-cursors-wayland/" /> <rdf:li rdf:resource="https://peter.czanik.hu/other/syslog-ng-using-on-multiple-platforms/" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=40186" /> <rdf:li rdf:resource="http://fossjon.wordpress.com/?p=5962" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=40232" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=40175" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=40214" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=39923" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13576" /> <rdf:li rdf:resource="https://badges.fedoraproject.org/badge/red-hat-summit-2024" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13577" /> <rdf:li rdf:resource="tag:neuroblog.fedoraproject.org,2024-04-22:/2024/04/22/next-open-neurofedora-meeting-22-april-1300-utc.html" /> <rdf:li rdf:resource="https://packit.dev/posts/weekly/2024/week-16" /> <rdf:li rdf:resource="http://opensourcesecurity.io/?p=3367" /> <rdf:li rdf:resource="https://gnu.wildebeest.org/blog/mjw/?p=1203" /> <rdf:li rdf:resource="https://www.jdieter.net/posts/2024/04/20/email-update/" /> <rdf:li rdf:resource="https://blog.kulakowski.fr/?p=30360" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13567" /> <rdf:li rdf:resource="tag:blogger.com,1999:blog-6112936277054198647.post-6156149132305853287" /> <rdf:li rdf:resource="https://major.io/p/fedora-cloud-init-dhcpcd/" /> <rdf:li rdf:resource="https://blog.kulakowski.fr/?p=15135" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=40137" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13271" /> <rdf:li rdf:resource="https://peter.czanik.hu/other/sudo-logging-pretty-json_compact/" /> <rdf:li rdf:resource="https://peter.czanik.hu/other/syslog-ng-sudo-json_compact-logs/" /> <rdf:li rdf:resource="http://fossjon.wordpress.com/?p=5945" /> <rdf:li rdf:resource="https://major.io/p/texas-linux-fest-2024-recap/" /> <rdf:li rdf:resource="https://adam.younglogic.com/?p=11101" /> <rdf:li rdf:resource="https://avi.alkalay.net/?p=4399" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=40118" /> <rdf:li rdf:resource="https://packit.dev/posts/weekly/2024/week-15" /> <rdf:li rdf:resource="http://opensourcesecurity.io/?p=3363" /> <rdf:li rdf:resource="https://blogs.gnome.org/otte/?p=6916" /> <rdf:li rdf:resource="urn:md5:64d278e5b08180fa7791da9dfda9aeec" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13533" /> <rdf:li rdf:resource="https://avi.alkalay.net/?p=4390" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13477" /> <rdf:li rdf:resource="tag:status.fedoraproject.org,2024-04-10:/2024-04-10-datacenter-network.html" /> <rdf:li rdf:resource="https://fedoramagazine.org/?p=40083" /> <rdf:li rdf:resource="https://communityblog.fedoraproject.org/?p=13505" /> <rdf:li rdf:resource="tag:github.com,2008:Repository/123299/8.1.0" /> <rdf:li rdf:resource="http://sgallagh.wordpress.com/?p=2100" /> <rdf:li rdf:resource="https://badges.fedoraproject.org/badge/fedora-42-coreos-test-day" /> <rdf:li rdf:resource="https://badges.fedoraproject.org/badge/fedora-41-coreos-test-day" /> </rdf:Seq> </items></channel> <item rdf:about="http://opensourcesecurity.io/?p=3372"> <title>Josh Bressers: Episode 426 – Automatically exploiting CVEs with AI</title> <link>https://opensourcesecurity.io/2024/04/28/episode-426-automatically-exploiting-cves-with-ai/</link> <content:encoded><p><a href="https://infosec.exchange/@joshbressers">Josh</a> and <a href="https://infosec.exchange/@kurtseifried">Kurt</a> talk about a paper describing using a LLM to automatically create exploits for CVEs. The idea is probably already happening in many spaces such as pen testing and intelligence services. We can’t keep up with the number of vulnerabilities we have, there’s no way we can possibly keep up with a glut of LLM generated vulnerabilities. We really need to rethink how we handle vulnerabilities.</p> &lt;audio class="wp-audio-shortcode" controls="controls" id="audio-3372-1" preload="none" style="width: 100%;"&gt;&lt;source src="https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_426_Automatically_exploiting_CVEs_with_AI.mp3?_=1" type="audio/mpeg"&gt;<a href="https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_426_Automatically_exploiting_CVEs_with_AI.mp3">https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_426_Automatically_exploiting_CVEs_with_AI.mp3</a>&lt;/audio&gt; <h2 class="wp-block-heading">Show Notes</h2> <ul><li><a href="https://www.theregister.com/2024/04/17/gpt4_can_exploit_real_vulnerabilities/">OpenAI’s GPT-4 can exploit real vulnerabilities by reading security advisories</a></li> <li><a href="https://arxiv.org/abs/2404.08144">paper: LLM Agents can Autonomously Exploit One-day Vulnerabilities</a></li> <li><a href="https://news.ycombinator.com/item?id=19507225">Cisco Fixes RV320/RV325 Vulnerability by Banning “curl” in User-Agent</a></li> <li><a href="https://github.com/CloudSecurityAlliance/webfinger.io.git">Episode 219 – Chat with Larry Cashdollar</a></li> <li><a href="https://locusmag.com/2023/12/commentary-cory-doctorow-what-kind-of-bubble-is-ai/">Cory Doctorow: What Kind of Bubble is AI?</a></li></ul></content:encoded> <dc:date>2024-04-29T00:00:00+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13612"> <title>Fedora Community Blog: Fedora Ops Architect Weekly</title> <link>https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-7/</link> <content:encoded><p>I hope you are all enjoying F40 and for some information on a few upcoming important stuff ‘n’ things in Fedora, read on <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f642.png" style="height: 1em;" class="wp-smiley" alt="🙂" /></p> <span id="more-13612"></span> <h2 class="wp-block-heading">Flock to Fedora CfP Closes Soon</h2> <p>If you have not already submitted a talk/workshop/whatever you have been thinking about doing to the <a href="https://cfp.fedoraproject.org/flock-2024/cfp">Flock to Fedora cfp</a>, you are in luck – submission closes tomorrow, <strong>April 29th</strong> so you have one more day to get that great idea of yours into us.</p> <p>Flock to Fedora is set for August 7th – 10th in Rochester, NY, USA. Check out the <a href="https://flocktofedora.org/">website</a> for more details on our annual contributors conference.</p> <h2 class="wp-block-heading">Fedora 40 Elections Now Open</h2> <p>The Fedora Linux 40 elections cycle has now begun, and our nominations period is open! You can nominate yourself, or someone you think would be a great fit (with their permission of course), to the <a href="https://docs.fedoraproject.org/en-US/council/">Fedora Council</a>, <a href="https://docs.fedoraproject.org/en-US/mindshare-committee/">Fedora Mindshare Committee</a>, <a href="https://docs.fedoraproject.org/en-US/fesco/">Fedora Engineering Steering Committee</a> or the <a href="https://docs.fedoraproject.org/en-US/epel/">EPEL Steering Committee</a> until May 8th.</p> <p>To nominate yourself or someone else, you just need to visit the nominations page of whichever group you would like to be elected to and fill out your name and FAS ID in the nominations box at the end. A set of interview questions will then be shared with each candidate after the nominations period closes for them to answer, which will be published on the community blog a few weeks before voting opens.</p> <p>This term, the following seats are open:</p> <ul><li><a href="https://fedoraproject.org/wiki/Council/Nominations">Fedora Council</a> – x2 seats</li> <li><a href="https://fedoraproject.org/wiki/Mindshare/Nominations">Fedora Mindshare Committee</a> – x1 seat</li> <li><a href="https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations">Fedora Engineering Steering Committee (FESCo)</a> – x4 seats</li> <li><a href="https://fedoraproject.org/wiki/EPEL/Nominations">EPEL Steering Committee</a> – x4 seats</li></ul> <p>For more information on the elections process in Fedora, visit our <a href="https://docs.fedoraproject.org/en-US/program_management/elections/">docs site</a> and for other key dates, you can view the <a href="https://fedorapeople.org/groups/schedule/f-40/f-40-elections-tasks.html">elections schedule</a> too.</p> <h2 class="wp-block-heading">Fedora Linux 41 </h2> <p>Development is now underway (and has been for a while) on Fedora Linux 41 and our <a href="https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html">release schedule</a> is live. Here are some dates you should keep in mind if you have any changes you would like to propose for F41:</p> <ul><li>June 19th – Changes requiring infrastructure changes</li> <li>June 25th – Changes requiring mass rebuild</li> <li>June 25th – System Wide changes</li> <li>July 16th – Self Contained changes</li></ul> <p>If you are unsure of how to propose a change, there is some excellent <a href="https://docs.fedoraproject.org/en-US/program_management/changes_guide/">documentation</a> and <a href="https://www.youtube.com/watch?v=oERoxg-VYPo">video tutorial</a> to help, and you can always reach out directly to me too.</p> <p>Below are some recently announced changes for F41 and feedback is most welcome:</p> <ul><li><a href="https://fedoraproject.org/wiki/Changes/Drop_Mandatory_Requires_on_JRE">Changes/Drop Mandatory Requires on JRE</a></li> <li><a href="https://fedoraproject.org/wiki/Changes/FedoraMiracle">Changes/FedoraMiracle</a></li> <li><a href="https://fedoraproject.org/wiki/Changes/Nodejs22">Changes/Nodejs22</a></li> <li><a href="https://fedoraproject.org/wiki/Changes/perl5.40">Changes/perl5.40</a></li></ul> <h2 class="wp-block-heading">Hot Topics</h2> <p>There is a lot of conversations happening around Fedora, and it can be hard to keep track of them all! Below is the top two on my own list from both <a href="https://discussion.fedoraproject.org/">discussion.fpo</a> and <a href="mailto:devel@lists.fedoraproject.org">devel@lists.fedoraproject.org</a>, in case you need some inspiration <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f642.png" style="height: 1em;" class="wp-smiley" alt="🙂" /></p> <ul><li><a href="https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/7RT3PMMDEZTT6WHUUWUCQPMC5Q6C3YZQ/">Intent to start ARC investigation git-forge replacement</a></li> <li><a href="https://discussion.fedoraproject.org/t/we-need-to-come-up-with-a-consistent-approach-for-generating-and-publishing-containers-both-traditional-and-atomic-desktop-containers-both-stable-and-unstable-releases/109213">We need to come up with a consistent approach for generation and publishing containers: both ‘traditional’ and atomic desktop containers, both stable and unstable releases</a></li></ul> <h2 class="wp-block-heading">Help Wanted and FYIs</h2> <p>Did you know there is a weekly hack-athon on the Fedora Infra apps happening? Aurélien Bompard hosts a weekly stream on <a href="https://www.twitch.tv/ohwellien">twitch</a> every Friday (that hes available) where he goes through bugfixes. Turn on notifications to Aurélien’s <a href="https://www.twitch.tv/ohwellien">topic thread</a> on discourse and catch him on twitch on Fridays!</p> <p>As always, <a href="https://fedoraproject.org/PackageReviewStatus/">package reviews</a> are needed and welcome and if you would like to adopt any packages that have been orphaned, you can find the full list from the <a href="https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/ICJEPCQQH3ILCWR32LS6JIZPFD7VIYJG/">most recent email</a>, or visit the packager dashboard <a href="https://packager-dashboard.fedoraproject.org/dashboard?users=orphan">here</a>.</p><p>The post <a href="https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-7/">Fedora Ops Architect Weekly</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-28T21:30:07+00:00</dc:date></item><item rdf:about="urn:md5:7626749cb59451b4d7832dc5e3a55972"> <title>Charles-Antoine Couret: Fedora Linux 40 est disponible avec un nouveau GNOME et KDE Plasma !</title> <link>https://blog.fedora-fr.org/renault/post/Fedora-Linux-40-est-disponible-avec-un-nouveau-GNOME-et-KDE-Plasma-%21</link> <content:encoded><p>En ce mardi 23 avril, les utilisateurs du Projet Fedora seront ravis d'apprendre la disponibilité de la version Fedora Linux 40.</p> <p>Fedora Linux est une distribution communautaire développée par le projet Fedora et sponsorisée par Red Hat, qui lui fournit des développeurs ainsi que des moyens financiers et logistiques. Fedora Linux peut être vue comme une sorte de vitrine technologique pour le monde du logiciel libre, c’est pourquoi elle est prompte à inclure des nouveautés.</p> <p>Cette 40e édition propose principalement une mise à jour de son interface principale GNOME 46 et de son concurrent KDE Plasma 6 qui passe à Wayland par défaut au passage.</p> <p><img src="https://forums.fedora-fr.org/assets/files/2024-04-21/1713740258-703882-gnome-bureau-petit.png" alt="" /></p> <h3>Expérience utilisateur</h3> <p><strong>Passage à GNOME 46.</strong> Cette version se démarque par beaucoup d'améliorations pour son navigateur de fichiers nommé <em>Fichiers</em>. Il dispose dorénavant, en plus d'une recherche dans le dossier et sous-dossiers en cours, d'une recherche globale utilisable via le bouton dédié avec une icône de loupe ou par le raccourci clavier <q>Ctrl+Shift+F</q> (contrairement à la recherche locale qui se fait via le raccourci <q>Ctrl+F</q>). Il permet de chercher dans l'ensemble du répertoire utilisateur voire davantage selon les préférences de l'utilisateur.</p> <p>L'icône de loupe prend place où était l'icône de progression lors des opérations sur les fichiers comme les décompressions ou la copie de fichiers. De fait ces opérations sont affichées en bas de la barre latérale ce qui permet d'afficher plus d'informations en un coup d’œil. L'application bénéficie en outre d'améliorations de performances en particulier pour afficher de gros dossiers avec des images ou lors du passage d'une vue liste à une vue par icônes et vice-versa. Plus de périphériques sur le réseau peuvent être découverts automatiquement permettant notamment de parcourir leurs fichiers.</p> <p>GNOME prend en charge les comptes Microsoft OneDrive ce qui permet de facilement parcourir les fichiers sauvegardés avec ce service. Dans les comptes à distance, le protocole WebDAV est aussi pris en charge pour l'accès à des calendriers, listes de contacts et autres fichiers partagés. Pour l'authentification de ces comptes en ligne, le navigateur par défaut est utilisé dorénavant ce qui permet d'utiliser une plus grande diversité de moyens d'authentifications comme l'usage de périphériques USB dédiés.</p> <p>Pour les amateurs de la connexion distante, il est maintenant possible de se connecter à GNOME graphiquement à distance via le protocole RDP. Auparavant seulement une session ouverte pouvait être pilotée ainsi. Cette option est désactivée par défaut et nécessite des droits appropriés, tout se configure via le panneau de configuration tout comme le bureau distant.</p> <p>En parlant du panneau de configuration, ce dernier a été amélioré en regroupant plusieurs configurations par sections afin d'améliorer la clarté de l'application. La liste des menus devenait particulièrement importante et rendait difficile la localisation des éléments à configurer. De plus, la configuration du pavé tactile a été améliorée pour permettre de choisir entre le clic dans un coin ou le clic à deux doigts pour réaliser l'équivalent d'un clic droit avec ce périphérique.</p> <p>Côté accessibilité, le lecteur d'écran Orca a été modernisé pour le rendre plus performant, plus fiable et plus compatible avec les applications Wayland ou celles exécutées dans un bac à sable tel que Flatpak. Il est possible de couper temporairement Orca avec le raccourci clavier <q>Ctrl+Alt+Shift+Q</q> ce qui est particulièrement utile en cas de conflit entre deux lecteurs d'écran ou si une application utilise du son aussi.</p> <p>Les notifications dans GNOME indiquent par quelle application elles ont été émises. Il est maintenant possible d'étendre facilement la notification afin de pouvoir la visualiser en entier, utilisant une vue plus compacte par défaut.</p> <p>De manière plus générale, GNOME bénéfice d'améliorations de performances notamment pour son terminal, son moniteur système qui bénéficie aussi d'un graphe dédié aux entrées / sorties sur les espaces de stockage, pour l'enregistrement de l'écran, le visionneur d'images ou encore pour la recherche globale de GNOME. L'ensemble des applications GTK4 bénéficie d'un nouveau moteur de rendu qui améliore le rendu du texte mais aussi les performances.</p> <p><img src="https://forums.fedora-fr.org/assets/files/2024-04-21/1713740378-975721-plasma-bureau-petit.png" alt="" /></p> <p><strong>L'environnement de bureau KDE Plasma change de version majeure avec sa nouvelle version 6.</strong> Au passage Plasma 6 utilise Wayland par défaut, et s'il était prévu de supprimer totalement la possibilité de l'utiliser avec X11 pour simplifier la maintenance, des volontaires ont permis de repousser l'échéance pour l'instant.</p> <p>Sous le capot, cette version utilise la nouvelle bibliothèque majeure graphique qu'elle emploie à savoir Qt 6. C'était l'occasion par ailleurs de rationaliser les différentes couches techniques et APIs internes afin de supprimer ce qui n'était plus au goût du jour ou trop peu employé pour être maintenu.</p> <p>Cette version propose la prise en charge partielle du rendu des couleurs en HDR pour les applications et matériel compatibles, mais aussi un profil de couleur spécifique par écran afin d'avoir un rendu fidèle des couleurs. Dans cette thématique pour les personnes souffrant de daltonisme ou d'autres formes de maladies dichromatiques peuvent utiliser des filtres pour améliorer la lisibilité des applications et de leur contenu.</p> <p>Dans les changements plus classiques, la barre principale est par défaut en mode flottant comme pour beaucoup de docks d'autres environnement de bureaux ou systèmes d'exploitation. Il est bien sûr possible de changer tout cela dans les paramètres et plus encore concernant cette barre principale. Concernant l'affichage principal, l'effet cube en cas de changement de bureau virtuel est de nouveau disponible. Pour la capture d'écran, il est possible de choisir une zone arbitraire de l'écran, d'utiliser le codec VP9 pour les enregistrements vidéos et de choisir sa qualité.</p> <p>Le thème par défaut de l'environnement nommé Breeze bénéficie d'un rafraichissement, il utilise moins de cadres et a un affichage un peu plus compact.</p> <p>Comme pour GNOME, la recherche a bénéficié d'un effort important. En plus de permettre la conversion de fuseaux horaires ou de trier les résultats par type, les performances sont grandement améliorées : jusqu'à 200% plus rapide pour chercher des documents, jusqu'à 60% plus rapide pour trouver une application, le tout jusqu'à moins 30% d'usage du processeur. La recherche obtient les résultats pour les textes traduits dans votre langue ou en anglais pour les noms ou les descriptions d'applications par exemple.</p> <p>Il est dorénavant possible de s'authentifier par mot de passe ou par empreinte digitale en même temps, il n'est plus nécessaire de forcer l'une des deux options.</p> <p>Et tant d'autres changements encore.</p> <h3>Gestion du matériel</h3> <p><strong>Fourniture de ROCm 6 pour améliorer la prise en charge de l'IA et le calcul haute performance pour les cartes graphiques ou accélérateurs d'AMD.</strong> Il concerne notamment les puces AMD Instinct MI300A et MI300X, et fournit de nouveaux algorithmes optimisés du mécanisme d'attention et de bibliothèques de communication. Il permet l'usage de flottant 8 bits pour gagner en consommation mémoire au détriment de la précision du modèle pour PyTorch et hipblasLT. Via la plateforme AMD Infinity Hub, il est possible d'obtenir des paquets prêts à l'usage pour certains travaux en IA ou calculs haute performance notamment pour les calculs scientifiques.</p> <p><img src="https://forums.fedora-fr.org/assets/files/2024-04-21/1713740104-400837-gnome-nouvelles-notifications.png" alt="" /></p> <p><strong>Passage à l'étape 2 de la prise en charge du noyau unifié nommée UKI (donc unifiant noyau, initrd, ligne de commande du noyau et signature) pour les plateformes avec UEFI mais rien ne change par défaut à ce sujet.</strong> L'objectif dans cette phase est de pouvoir démarrer sur de tels noyaux directement sans chargeur de démarrage intermédiaire, tout en offrant la possibilité de démarrer sur d'autres noyaux et de passer automatiquement au noyau suivant par défaut suite à une mise à jour. Les machines Aarch64 (ARM 64 bits) peuvent également s'en servir maintenant. <a href="https://gitlab.com/kraxel/fedora-uki" hreflang="fr">Une image pour cette architecture et x86_64 doit également être fournie pour un contexte de virtualisation en étant basée sur ces fichiers kickstart.</a></p> <p>Si vous souhaitez tester cela sur un système existant, vous pouvez installer les paquets <q>virt-firmware</q>, <q>uki-direct</q> avant d'exécuter le script <q>sh /usr/share/doc/python3-virt-firmware/experimental/fixup-partitions-for-uki.sh</q> pour configurer les partitions proprement afin d'être découvrables par le système, puis enfin installer le paquet <q>kernel-uki-virt</q> pour qu'il installe le noyau proprement avec la nouvelle méthode. Il est préférable de tester cela sur une machine virtuelle ou si vous savez ce que vous faites avec du matériel standard type ahci / nvme pour le stockage principal. Bien sûr ce travail reste expérimental et est réservé à ceux qui savent comment faire pour réparer le système en cas de problèmes.</p> <h3>Internationalisation</h3> <p><strong>Le gestionnaire d'entrée de saisie IBus passe à la version 1.5.30.</strong> Les commandes pour lancer et relancer IBus fonctionnent depuis l'environnement Plasma Wayland dorénavant, et pour cet environnement aussi les préférences sont maintenant accessibles depuis le menu non contextuel.</p> <p><strong>Mise à jour de ibus-anthy 1.5.16 pour la saisie du japonais.</strong> Le principal changement est la conversion possible <em>d'ère japonaise</em> avec <em>2024</em>.</p> <h3>Administration système</h3> <p><strong>NetworkManager tente de détecter par défaut les conflits d'usage d'adresse IPv4 avec le protocole <em>Address Conflict Detection</em> (RFC 5227) avant de l'attribuer à la machine.</strong> En somme au moment de s'attribuer une adresse IP donnée, une requête ARP est envoyée au réseau concernant cette adresse. Si une réponse est obtenue, l'adresse est déjà utilisée et n'est donc pas exploitable sans perturber le réseau. Ce mécanisme existe pour les réseaux avec IP fixes ou même avec un serveur DHCP central car rien n'empêche la présence d'une machine configurée avec une IP fixe dans le réseau malgré tout. Si le réseau a un serveur DHCP et qu'un conflit est détecté, la réponse <em>DHCPDECLINE</em> sera envoyée pour obtenir peut être une autre adresse. En cas de conflit une erreur sera rapportée permettant à l'utilisateur de diagnostiquer le problème et d'y apporter une solution. Par défaut le système attendra 200 ms avant de décider qu'il n'y a aucune réponse. Pour l'IPv6 cela est inclus dans le standard RFC 4862 ce qui rend ce changement non nécessaire dans ce cas de figure.</p> <p><strong>NetworkManager va utiliser une adresse MAC aléatoire par défaut pour chaque réseau Wifi différent, et cette adresse sera stable pour un réseau donné.</strong> En effet, certains systèmes utilisent l'adresse Mac pour identifier les machines en déplacement de réseau en réseau permettant une pseudo géolocalisation ce qui nuit à la vie privée. Mais la méthode usuelle de changer d'adresse MAC aléatoirement à chaque connexion pose un problème en cas de réseau restreignant l'accès à certaines adresses MAC uniquement ou en changeant d'adresse IP à chaque reconnexion. Cette méthode est un compromis entre le respect de la vie privée et le confort d'utilisation. Cela est fait en ajoutant la configuration <q>wifi.cloned-mac-address="stable-ssid"</q> dans le nouveau fichier <q>/usr/lib/NetworkManager/conf.d/22-wifi-mac-addr.conf</q>.</p> <p><strong>Les entrées des politiques SELinux qui font référence au répertoire <q>/var/run</q> font maintenant référence au répertoire <q>/run</q>.</strong> Il y a dix ans déjà que le premier répertoire a bougé vers le deuxième chemin mais SELinux a gardé les vieilles règles en utilisant un lien d'équivalence entre eux pour permettre leur utilisation. Cependant certains outils comme <q>restorecon</q> ne gèrent pas bien cette situation tout comme les administrateurs systèmes qui ne sont pas sûrs de comment écrire proprement de nouvelles règles. Pour résoudre le problème le lien d'équivalence passe de <q>/run = /var/run</q> à <q>/var/run = /run</q>.</p> <p><img src="https://forums.fedora-fr.org/assets/files/2024-04-21/1713740104-630199-gnome-recherche-globale.png" alt="" /></p> <p><strong>L'outil SSSD ne prend plus en charge les fichiers permettant de gérer les utilisateurs locaux.</strong> Il pouvait exploiter les fichiers <q>/etc/passwd</q> et <q>/etc/group</q> via l'utilisation de l'option <q>id_provider=files</q>. Cependant cette option n'est plus proposée par le projet officiel et n'était à l'époque conservée que pour permettre l'authentification via des cartes à puce ou l'enregistrement de sessions. Mais dans les deux cas il est possible de passer à la méthode <em>proxy</em> via l'option <q>id_provider=proxy</q> pour le remplacer dans ces cas d'usage. <a href="https://sssd.io/docs/files-provider-deprecation.html" hreflang="fr">Un guide officiel est proposé pour effectuer la conversion pour ceux qui en ont besoin</a>.</p> <p><strong>DNF ne téléchargera plus par défaut la liste des fichiers fournie par les différents paquets.</strong> Jusqu'à présent il le faisait par défaut parmi d'autres métadonnées, mais cette information n'est en réalité nécessaire que dans certains cas précis qui ne concernent pas celui de la majorité des utilisateurs. Notamment pour quelques paquets ayant une dépendance envers un fichier particulier plutôt qu'un paquet donné ou si on cherche un paquet fournissant un fichier spécifique. Cela permet de réduire les ressources consommées chez les utilisateurs mais aussi au sein de l'infrastructure de Fedora car il n'est plus nécessaire de fournir ces données assez conséquentes de manière systématique.</p> <p><strong>L'outil fwupd pour mettre à jour les firmwares va utiliser passim comme cache pour partager sur le réseau local les métadonnées liées aux mises à jour disponibles pour les firmwares.</strong> Ce fichier qui représente environ 1 Mio est téléchargé quotidiennement parfois sur des liaisons coûteuses. Ainsi la pression est réduite sur les infrastructures notamment le CDN fwupd et la bande passante en utilisant localement la ressource quand elle est disponible. Passim utilise avahi pour signaler son service sur le réseau local qui est disponible via le port 27500 afin que les autres clients puissent identifier si des métadonnées sont disponibles localement.</p> <p><strong>Les systèmes Fedora Silverblue et Kinoite disposent de bootupd pour la mise à jour du chargeur de démarrage.</strong> Par conception les systèmes avec rpm-ostree comme ceux-ci n'ont pas le chargeur de démarrage qui se met à jour par ce biais car cela n'est pas une opération sûre. En effet, la mise à jour de ces systèmes repose sur le principe de transaction pour que le passage d'un état à un autre soit fiable, cependant ce mécanisme ne fonctionne pas bien pour le chargeur de démarrage qui est un composant distinct et critique. On retrouve la même problématique pour les systèmes utilisant un mécanisme de mise à jour basé sur une partition A et B et passant de l'un à l'autre. D'où la création de cet utilitaire qui est mis à disposition pour ceux qui le souhaitent, du moins pour les machines disposant d'un EFI. La mise à jour est pour le moment manuelle à la demande avec la commande <q>bootupctl update</q>. La mise à jour automatique sera prévue dans le futur.</p> <p><strong>Le paquet <q>libuser</q> est marqué en voie de suppression pour Fedora 41 alors que le paquet <q>passwd</q> est supprimé.</strong> La bibliothèque libuser sert à cacher les différences entre les utilisateurs locaux et distants via le protocole LDAP. Mais la prise en charge de ce protocole reste incomplet et il n'y a pas de plan pour aller plus loin, comme <q>sssd</q> peut la remplacer dans ce rôle, la décision de la supprimer prochainement de Fedora fait sens. Pour l'instant seuls les paquets <q>usermode</q> et <q>util-linux</q> en ont encore besoin. Le paquet <q>passwd</q> quant à lui disparaît pour se débarrasser de la dépendance à libuser. La commande pour changer de mot de passe ne change pas, mais est fournie par le paquet <q>shadow-utils</q>.</p> <p><strong>Le paquet <q>cyrus-sasl-ntlm</q> a été supprimé.</strong> Le protocole d'identification NTLM n'est plus maintenu, au profit du protocole Kerberos et ce composant dans SASL n'est plus maintenu depuis des années justifiant une telle décision.</p> <p><strong>La gestion des droits utilisateurs pam_userdb passe de la base de données BerkeleyDB à GDBM.</strong> BerkeleyDB 5.x fourni par Fedora n'est plus à jour ce qui pose des soucis en terme de bogues et de sécurité, d'autant plus avec le rôle de PAM dans le système. La licence de BerkeleyDB a changé dans la branche 6.x, passant de BSD à AGPL rendant impossible l'adoption de cette version plus à jour pour ce composant, les licences n'étant pas compatibles. Ainsi GDBM se pose comme une alternative pour résoudre ce problème. BerkeleyDB 5.x a débuté sa sortie du projet Fedora depuis Fedora 33, ceci est une étape de plus dans cette direction.</p> <p><strong>Le filtre antispam bogofilter utilise SQLite au lieu de BerkeleyDB pour gérer sa base de données interne.</strong> La raison est analogue au paragraphe précédent.</p> <p><strong>Le serveur LDAP 389 passe de la version 2.4.4 à la version 3.0.0.</strong> Le projet abandonne la prise en charge de BerkeleyDB pour sa base de données interne pour la même raison que précédemment. En dehors de cela qui introduit des incompatibilités, cette mise à jour est en réalité assez mineure sur les autres aspects en fournissant essentiellement des correctifs de bogues.</p> <p><strong>Le paquet <q>iotop</q> est remplacé par <q>iotop-c</q>.</strong> Si le nom du paquet change, celui du binaire installé ne change pas. iotop n'est plus vraiment maintenu depuis une dizaine d'années et est sévèrement concurrencé par iotop-c sur cet aspect qui bénéfice en plus d'une empreinte mémoire plus petite étant rédigé en C au lieu de Python. Il n'est pas pertinent aux yeux des mainteneurs de maintenir les deux ainsi.</p> <p><strong>L'orchestrateur de conteneurs Kubernetes évolue de la version 1.27 à la version 1.29.</strong> Ce changement est communiqué car Kubernetes déconseille le saut des versions ce que Fedora fait actuellement en passant à la version 1.28 en fournissant ainsi la dernière version disponible. Cette version propose aux utilisateurs la possibilité d'avoir un écart de version de n-2 à n-3 pour les versions mineures entre le nœud principal et le <em>plan de contrôle</em>. Il est également possible si un nœud est indisponible suite à une panne ou à un état non récupérable de démarrer les services qu'il gérait dans un autre nœud dans un état sain. Le mode d'accès aux données <q>ReadWriteOncePod</q> devient accessible sans restrictions, permettant de restreindre l'accès à des données à un seul pod à la fois plutôt qu'à un seul nœud, pour réduire le risque d'accès concurrents en particulier en écriture. De même le module <em>KMS v2</em> est disponible à tous pour réaliser les services de chiffrement pour vos APIs.</p> <p><strong>Par ailleurs les paquets de Kubernetes sont restructurés.</strong> L'objectif est de se rapprocher de l'organisation du projet upstream et de simplifier la vie des utilisateurs. Ainsi le paquet <q>kubernetes</q> récupère l'utilitaire <q>kubelet</q> qui avait son paquet dédié et les services fournis via l'ancien sous-paquet <q>kubernetes-master</q> sont renommés <q>kubernetes-systemd</q>. Les paquets <q>kubernetes-client</q> et <q>kubernetes-kubeadm</q> restent inchangés.</p> <p><strong>Pendant que podman est mis à jour vers la version 5.</strong> Cette version abandonne la prise en charge des cgroupv1 du noyau, de même que les plugins CNI ou la base de données clé / valeur Boltdb au profit de SQLite pour les nouvelles instances. Le format des fichiers de configuration pour les <em>podman machines</em> a été profondément remanié, rendant nécessaire la recréation des machines virtuelles concernées conçues avant cette version.</p> <p><strong>Le paquet <q>wget2</q> remplace le paquet }}wget}} en fournissant une nouvelle version.</strong> Cette version propose du code multithreadé et qui télécharge plus vite grâce à la prise en charge du protocole HTTP2 avec la compression ou le téléchargement parallèle. Il propose plus d'options, il a également plus de tests automatiques pour s'assurer de sa robustesse dans le temps. Sa réécriture dans un style plus moderne devrait faciliter l'adoption de nouveaux protocoles à l'avenir. Par contre les protocoles dépassés WARC et FTP sont moins bien pris en charge. La licence change pour GPLv3+, de même que sa bibliothèque libwget2 vers LGPLv3+.</p> <p><img src="https://forums.fedora-fr.org/assets/files/2024-04-21/1713740104-351611-gnome-moniteur-systeme.png" alt="" /></p> <p><strong>Le gestionnaire de base de données PostgreSQL migre vers sa 16e version.</strong> De part l'arrêt des modules, les paquets pour des versions alternatives sont également réintroduits. Ainsi les paquets <q>postgresql15*</q> font leur apparition pour la prise en charge de la version précédente, et les paquets <q>postgresql17*</q> seront proposés quand la 17e version sera disponible. En terme de changements apportés par cette nouvelle version, les jointures <q>FULL</q> ou <q>OUTER</q> sur des hash peuvent être parallélisées pour de meilleures performances. Il est dorénavant possible de répliquer des données depuis des serveurs dans un état <em>standby</em>, de même la réplication peut être appliquée en parallèle pour de larges transactions afin d'améliorer les performances de l'opération. La vue <q>pg_stat_io</q> fournit des informations statistiques concernant les entrées et sorties. SQL/JSON qui est introduit dans le standard SQL bénéficie de constructeurs dédiés pour créer des objets JSON mais aussi des fonctions identités pour connaître le type des clés. Et ce parmi de nombreuses corrections de bogues et d'amélioration de performances.</p> <p><strong>Les paquets MySQL et MariaDB sont remaniés et mis à jour vers la version 10.11 pour MariaDB.</strong> Le paquet <q>community-mysql</q> est renommé <q>mysql</q> tandis que le paquet <q>mariadb</q> ne fourni plus de binaires avec le nom <q>mysql</q>. En effet la décision à l'époque a été prise car il semblait convenu que MariaDB remplacerait MySQL tout comme LibreOffice a supplanté OpenOffice.org mais force est de constater que les deux projets vont cohabiter longtemps. Cela rend le tout plus simple pour l'utilisateur. Cependant, puisque ces logiciels évoluent séparément, ils deviennent peu à peu incompatibles et le mainteneur abandonne la possibilité d'utiliser MariaDB comme serveur avec MySQL comme client et vice-versa. Aucune autre distribution en fournissait une telle possibilité et cela devenait difficile à maintenir car cela était source de problèmes.</p> <p>En terme de nouvelles fonctionnalités pour MariaDB, il est possible de lire entièrement les tables Information Schema Parameters et Information Schema Routines tout en améliorant les performances dans la procédure. Il est possible de savoir combien de temps une requête passe dans l'optimiseur via l'option <q>ANALYZE FORMAT=JSON</q>. Les semi-jointures pour la mise à jour ou la suppression de données sont optimisées. Les privilèges <q>SUPER</q> et <q>READ ONLY ADMIN</q> sont dorénavant distincts, à ce sujet il est possible de fournir à tous les utilisateurs des droits spécifiques via la requête <q>GRANT &lt;privilege&gt; ON &lt;database&gt;.&lt;object&gt; TO PUBLIC</q>.</p> <h3>Développement</h3> <p><strong>Mise à jour de la suite de compilation GNU : GCC 14.0, binutils 2,41, glibc 2.39 et gdb 14.1.</strong></p> <p>Concernant la suite de compilateurs GCC, elle continue l'amélioration de la prise en charge des langages C23 et C<ins>23, alors que débute la prise en charge de la future norme C</ins>26. De nombreux modèles de puces Aarch64 et x86_64 bénéficient de micro-optimisations, tandis qu'il y a un début de prise en charge des nouvelles instructions pour l'architecture x86_64 d'Intel dénommées APX et AVX10. L'analyseur statique de code peut afficher visuellement les dépassements de tampons pour mieux comprendre ce qui se passe en mémoire.</p> <p>Pour la suite d'outils binutils, cela se concentre surtout sur la prise en charge plus étendue des instructions des architectures Aarch64, RISC-V et x86_64.</p> <p>Quant à la bibliothèque standard C glibc, cela se traduit par de nombreuses améliorations comme la prise en charge de la pile cachée pour éviter les attaques par modification d'adresse de retour, ce que Fedora Linux active par ailleurs. De même pour limiter certaines attaques, la glibc propose de pouvoir réécrire au lancement la PLT pour obtenir les adresses des fonctions des bibliothèques dynamiques plutôt que de les avoir lors du premier appel à chaque fonction. Le programme démarre plus lentement mais est plus sûr pour la suite. L'en-tête <q>&lt;stdbit.h&gt;</q> fait son apparition pour les manipulations sur les bits, opérations basées sur la norme de C20. Et une nouvelle fonction <q>posix_spawnattr_setcgroup_np</q> est ajoutée pour démarrer un processus dans un cgroup donné afin d'éviter des situations de concurrence entre le moment où le processus est démarré et où les restrictions s'appliquent.</p> <p>Enfin le débogueur gdb propose un début de prise en charge du protocole de Microsoft <em>Debugger Adapter Protocol</em> pour faire le lien entre les débogueurs et des IDEs ou éditeurs de code afin de faciliter leur intégration mutuelle. Il peut également gérer des entiers au delà de 64 bits, de même que d'appeler une commande shell avec l'instruction <q>$_shell</q> pour obtenir son résultat. Les instructions de l'architecture Aarch64 SME et SME2 commencent à être gérées et l'API Python est considérablement étoffée pour ceux qui veulent scripter le débogueur.</p> <p><strong>La suite de compilateurs LLVM est mise à jour à la version 18.</strong> Fedora en profite pour que CLang utilise des informations de débogage au format DWARF-5 au lieu de DWARF-4 par défaut comme appliqué par le projet amont. Pour simplifier la procédure de compilation de Fedora pour les paquets utilisant cette chaîne de compilation, le Fat-LTO sera employé pour permettre l'usage du LTO quand c'est possible comme cela était déjà le cas avec GCC. Jusqu'alors ces paquets étaient compilés avec LTO par défaut avec une éventuelle conversion vers ELF à la main si la compatibilité le nécessitait ce qui était particulièrement lourd. Par ailleurs les paquets de compatibilité des versions précédentes fournissent les binaires des différents utilitaires et non plus seulement les bibliothèques et en-têtes.</p> <p>Concernant les nouveautés apportées par le projet en lui même, comme pour la chaîne de compilation GNU, les architectures Aarch64, x86_64 ou RISC-V sont mieux gérées. Le compilateur CLang suit GCC avec du travail sur C<ins>20, C</ins>23 pour améliorer la compatibilité avec le standard et le début de prise en charge de la future norme C++26.</p> <p><strong>Mise à jour de la bibliothèque C++ Boost à la version 1.83.</strong> Depuis la version 1.81, cette bibliothèque propose un module pour communiquer avec les bases de données MySQL ou encore une bibliothèque <q>Compat:</q> pour fournir en code compatible C++11 des ajouts proposés par les standards ultérieurs.</p> <p><strong>Le langage Go passe à la version 1.22.</strong> La sémantique de la boucle <em>for</em> évolue un peu avec la création de la variable de boucle à chaque itération de boucle plutôt qu'à la première avec mise à jour à chaque passage. De plus il accepte l'usage des plages de valeurs basées sur des entiers. L'exécution des programmes gagne 1 à 3% grâce à l'optimisation de la localisation mémoire des métadonnées du ramasse miette. Les programmes compilés avec un profil d'optimisation peuvent gagner entre 2 et 14% de performances par rapport à la version précédente grâce à la possibilité d'appliquer la technique sur plus de fonctions qu'avant.</p> <p><strong>Le JDK de référence pour Java passe de la version 17 à 21.</strong> OpenJDK peut maintenant faire du filtrage par motif dans une instruction <q>switch</q>. Il est possible aussi d'affecter le résultat d'une identification de type dans une variable directement afin de pouvoir s'en servir immédiatement. Des fils d'exécution virtuels font leur apparition qui sont plus légers et performants, plutôt dédiés à des tâches courtes avec beaucoup d'attentes, ces tâches peuvent ainsi bénéficier de meilleure performance notamment en terme de latence. Il introduit également une API pour les collections d'objet en séquence (donc ordonnées). De même une nouvelle API pour manipuler les clés cryptographiques symétriques fait son entrée. Le ramasse miette Z Garbage Collector améliore ses performances.</p> <p><strong>Ruby 3.3 surveille sa syntaxe avec Prism.</strong> Prism est un gem introduisant un nouveau parseur très flexible qui a vocation à remplacer Ripper. Le compilateur juste à temps YJIT bénéficie de nombreuses améliorations comme de meilleures performances, une réduction de la consommation mémoire avec un code généré plus compact et avec moins de métadonnées et un temps de compilation plus court. Un concurrent RJIT fait son entrée, écrit en pur Ruby et non en C comme YJIT, il a plus vocation à servir de terrain d'expérimentation. Le ramasse miette est également plus performant.</p> <p><img src="https://forums.fedora-fr.org/assets/files/2024-04-21/1713740104-164436-gnome-connexion-a-distance.png" alt="" /></p> <p><strong>Le langage PHP utilise la version 8.3.</strong> Cette version permet de définir des classes constantes, il propose également un attribut <q>#<a href="https://blog.fedora-fr.org/renault/post/\Override" title="\Override">\Override</a></q> si une classe surcharge une méthode d'une classe parente. Une nouvelle fonction <q>json_validate</q> permet de vérifier la validité d'un JSON sans le décoder. Le <q>Randomizer</q> a plus de méthodes pour permettre de générer des noms ou nombres aléatoires suivant les besoins.</p> <p><strong>La boîte à outils pour le machine learning PyTorch fait son entrée dans Fedora.</strong> L'objectif est de fournir une meilleure expérience pour les développeurs de ce genre de solution. Un groupe de travail dédié s'est mis en place avec une réunion bi-hebdommadaire. Pour le moment l'architecture x86_64 est la seule prise en charge avec un effort important mis sur les solutions AMD.</p> <p><strong>Le paquet <q>python-sqlalchemy</q> utilise la nouvelle branche majeure 2.x du projet, le paquet python-sqlalchemy1.4 est proposé pour garder la compatibilité.</strong> Cette version apporte entre autre de l'annotation de type ce qui permet de construire des ORM sur un modèle déclaratif. Les opérations d'insertions sont aussi bien plus performantes quelque soit le gestionnaire de base de données derrière.</p> <p><strong>La bibliothèque de validation des données Pydantic utilise dorénavant la version 2.</strong> Outre l'amélioration des performances, il change radicalement son API ce qui coupe la compatibilité ascendante.</p> <p><strong>La bibliothèque Thread Building Blocks passe du fil 2020.3 au fil 2021.8.</strong> De même la compatibilité ascendante n'est pas garantie ce qui a rendu ce portage compliqué.</p> <p><strong>La bibliothèque OpenSSL 1.1 est supprimée ne laissant que la dernière version de la branche 3.x.</strong> Depuis Fedora 36 la branche 3 est employée par défaut dans Fedora. OpenSSL 1.1 n'est plus maintenue depuis fin de l'année dernière ce qui rend sa maintenance délicate et non sûre d'où son abandon malgré la faible compatibilité entre les deux versions pour ceux qui s'en servait encore.</p> <p><strong>Les bibliothèques zlib et minizip utilisent leur variante zlib-ng et minizip-ng dorénavant.</strong> Ces versions sont plus rapides grâce à l'emploi des instructions plus modernes des processeurs actuels tout en gardant la compatibilité par rapport à l'implémentation de référence.</p> <p><strong>Le langage Python ne bénéficie plus de la version 3.7.</strong> Depuis juin de l'année dernière cette version n'est plus maintenue et il n'y a pas de raison de poursuivre son maintien dans les dépôts en tant que version de compatibilité.</p> <h3>Projet Fedora</h3> <p><strong>L'édition Cloud sera construite avec l'utilitaire Kiwi dans Koji.</strong> L'utilitaire ImageFactory employé jusqu'à présent n'est plus maintenu. Les outils <q>mkosi</q> et <q>osbuild</q> ont été considérés mais non retenus, le premier car il manque de flexibilité pour fournir toutes les images souhaitées, tandis que le second est certes adopté par l'équipe de Fedora Workstation mais ne semble pas adapté aux besoins des images clouds qui reposent sur d'autres technologies dont rpm-ostree et doit fournir des délivrables plus variés également. En effet l'image cloud cible Vagrant, Azure, AWS, GCP et peut dorénavant viser aussi les images pour WSL2 ou pour conteneurs directement.</p> <p><strong>Tandis que l'édition Workstation aura son image ISO générée avec l'outil Image Builder.</strong> En effet ce dernier bien que déjà employé par Fedora Workstation bénéficie enfin de la prise en charge des images ISO live. Il remplace donc les outils lorax/livemedia-creator qui avaient beaucoup de problèmes. Il devient aussi plus simple pour quiconque de générer son image ISO avec un simple fichier TOML pour le décrire et quelques utilitaires en ligne de commande.</p> <p><strong>L'image minimale ARM sera construite avec l'outil OSBuild.</strong> Comme dans le cadre de l'édition Cloud, il remplace l'utilitaire ImageFactory qui montrait ses limites. L'objectif à terme est de pouvoir supprimer totalement ou partiellement les hacks nécessaires à ce jour pour utiliser cette image sur une grande variété de systèmes ARM.</p> <p><strong>Fedora IoT bénéficiera d'images pouvant démarrer dans des conteneurs.</strong> Ainsi il est possible de tester le système dans des conteneurs plutôt que via de la virtualisation classique ou sur des machines physiques. Cette flexibilité peut aider le test par les utilisateurs mais également par ses mainteneurs.</p> <p><strong>Il bénéficiera également des images Simplified Provisioning.</strong> Fedora IoT peut ainsi utiliser l'utilitaire <q>coreos-installer</q> pour l'installer sur le disque directement et ce en utilisant un argument noyau pour savoir sur quel disque l'installer. Ainsi pas besoin de fichier kickstart ou d’interaction avec l'utilisateur ce qui simplifie la procédure et son automatisation. Cela s'intègre parfaitement avec les dispositifs Fido Device Onboarding et Ignition pour la configuration de tels systèmes dans un environnement de production.</p> <p><strong>Et le tout sera construit en utilisant rpm-ostree unified core.</strong> L'ancien mode n'est en effet plus maintenu et moins testé. Le mode unifié permet au <em>compose server</em>, qui est l'image de base créée à partir de RPM, de fonctionner de manière similaire au <em>client</em> qui ajoute des commits par dessus pour personnaliser le contenu du système. Cela permet de simplifier la maintenance côté rpm-ostree mais aussi de résoudre certaines difficultés notamment pour la gestion du démarrage avec bootupd, les labels SELinux et l'utilisation de conteneurs pour les scriplets pré et post installations des paquets. Depuis Fedora Linux 39 où Silverblue et Kinoite ont amorcé la transition, l'édition IoT était la dernière variante à ne pas avoir franchi le pas.</p> <p><strong>Fedora sera construit avec DNF 5 en interne.</strong> Ainsi les outils Mock, Koji et Copr passent le cap, en attendant Fedora Linux 41 pour que cela soit le cas pour les utilisateurs de la distribution. L'objectif est ici double. Les développeurs de DNF auront un retour d'expérience grandeur nature sur cette version et permettra d'identifier d'éventuels problèmes. Pour l'infrastructure, DNF 5 est plus léger en mémoire, plus performant et consomme moins d'espace disque ce qui permettrait de gagner du temps dans la construction des RPM et des images et de réduire la pression sur le matériel employé à ces tâches.</p> <p><img src="https://forums.fedora-fr.org/assets/files/2024-04-21/1713740071-361482-plasma-applications.png" alt="" /></p> <p><strong>Les macros forge passent du paquet redhat-rpm-config à forge-srpm-macros.</strong> Ces projets sont maintenant distincts upstream et ce premier dépend maintenant du second. L'objectif est de simplifier la possibilité d'exécuter des tests automatiques sur ces macros afin d'améliorer leur fiabilité.</p> <p><strong>Phase 3 de l'usage généralisé des noms abrégés de licence provenant du projet SPDX pour la licence des paquets plutôt que des noms du projet Fedora.</strong> L'objectif de cette phase est de poursuivre le travail entamé dans les versions précédentes en convertissant l'essentiel des paquets RPM vers ce nouveau format. Cependant le travail devrait être achevé pour l'ensemble des paquets pour Fedora Linux 41.</p> <p><strong>La construction de certains paquets échouera si l'éditeur de lien détecte certaines classes de vulnérabilité dans le binaire en construction.</strong> C'est la macro <q>%{hardened_build</q>} qui est étendue pour fournir ce service, cela ne concerne que les paquets l'utilisant. Il peut ainsi générer une telle erreur s'il détecte une pile exécutable, un segment chargeable en mémoire avec des permissions en lecture, écriture et exécutable ou un fil d'exécution local ayant un segment exécutable. L'objectif est donc de renforcer le caractère non modifiable des sections mémoires exécutables pour limiter le risque de failles de sécurité. Cela est fait grâce à l'éditeur de lien BFD qui fournit de telles vérifications. Jusqu'à présent ces cas étaient détectés mais ne généraient que des avertissements qui étaient de fait ignorés.</p> <p><strong>Compilation des paquets en convertissant plus d'avertissements comme erreurs lors de la compilation des projets avec le langage C.</strong> L'objectif est de supprimer de plus en plus de code utilisant d'anciennes constructions qui sont source de bogues d'une part, mais qui seront aussi progressivement interdites par défaut avec les futures versions de GCC. Par ailleurs, certains de ces éléments pouvaient être bloquants pour l'adoption d'une nouvelle norme C de référence pour certains paquets.</p> <p>Voici la liste des changements opérés :</p> <ul><li>Suppression des déclarations implicites de fonctions : 54 paquets concernés ;</li><li>Suppression du type implicite <q>int</q> quand le type est omis : 5 paquets concernés ;</li><li>Obligation de mentionner les types dans les arguments lors de la déclaration de fonctions : aucun paquet concerné ;</li><li>Interdiction de conversions implicites entre entier et pointeurs : 100 paquets concernés ;</li><li>L'instruction <q>return</q> doit avoir les arguments qui correspondent au type de retour d'une fonction (donc pas d'argument si <q>void</q>, et non vide si un entier est attendu par exemple) : 13 paquets concernés ;</li><li>Interdiction des conversions implicites de pointeurs de types différents : 381 paquets concernés.</li></ul> <p>Certains changements devraient voir le jour dans le futur :</p> <ul><li>Interdiction des déclarations de fonctions dans le style pré-C89 ;</li><li>Interdiction d'utiliser des mots clés <q>bool</q>, <q>true</q> ou <q>false</q> avec des définitions locales plutôt que d'utiliser l'en-tête de la bibliothèque standard ;</li><li>Déclarer une fonction sans argument comme <q>void foo()</q> aurait le même sens qu'en C++, à savoir équivalent à <q>void foo(void)</q> plutôt qu'à accepter n'importe quel type d'arguments.</li></ul> <p><strong>Clap de fin pour la construction des mises à jour au format Delta RPM.</strong> Ils sont désactivés par défaut dans la configuration de DNF et Fedora ne les générera plus. Cette fonctionnalité permettait pour les mises à jour de ne télécharger que la différence entre le paquet déjà installé et celui à mettre à jour. Cela permettait de réduire la quantité de données à télécharger, la machine de l'utilisateur pouvait reconstruire le paquet à partir de ces informations et ainsi obtenir la nouvelle version. Mais en pratique la fonctionnalité se révèle de moins en moins pertinente. Tout d'abord le processus n'est pas fiable à 100%, parfois la reconstruction échoue et dans ce cas le nouveau paquet est totalement téléchargé à nouveau ce qui conduit à un gaspillage de ressources. De plus peu de paquets étaient concernés, les delta RPM étaient d'ailleurs construits en général que d'une version à une autre ce qui la rend fonctionnelle surtout pour ceux qui mettent à jour très régulièrement leur système. Et pour que cette fonctionnalité soit exploitable, ces fichiers delta rpm font partie des métadonnées que DNF télécharge. Sauf que c'est le cas même si les delta rpm sont désactivés par l'utilisateur, ou pour les systèmes reposant sur rpm-ostree ou utilisant un GUI comme GNOME Logiciels car PackageKit comme rpm-ostree ne se servent pas de ces métadonnées. Au final cela pénalise toute l'infrastructure qui doit générer et stocker ces données, et beaucoup d'utilisateurs qui subissent les inconvénients sans les avantages le tout pour un gain jugé marginal pour ceux qui s'en servent : moins de 8% de réduction de la taille des téléchargements en moyenne.</p> <p><strong>Les JDKs ne sont générés qu'une fois, et rempaquetés ainsi à toutes les variantes du système.</strong> Pour cela les paquets du JDK sont générés à partir de la version la plus ancienne de Fedora Linux encore maintenue, et le résultat est directement réutilisé pour former les paquets des autres versions du système. Cela réduit considérablement le temps de validation de chaque JDK car il y a cinq fois moins de versions différentes à gérer. Cela permettra aux mainteneurs de maintenir la diversité actuelle des JDK à savoir les versions 1.8.0, 11, 17 et la dernière (actuellement la version 20). Si ce résultat ne permet pas de libérer assez de temps aux mainteneurs, la réduction du nombre de JDK à l'avenir pourrait être considérée.</p> <p><strong>Les images immuables pour les systèmes personnels comme Silverblue seront nommées sous la dénomination Atomic pour éviter la référence au terme immuable qui est confus pour les utilisateurs.</strong> Les noms de variantes Silverblue, Kinoite, Sericea et Onyx vont être préservés, l'objectif est de donner une dénomination commune qui utilise le terme Atomic déjà employé par l'édition Cloud par exemple. Le terme immuable est en effet considéré comme peu clair car si le système principal est majoritairement en lecture seule, il ne l'est pas totalement notamment pour la configuration ou les parties dynamiques du système. Alors que le système repose sur le concept d'atomicité en ayant une approche par état du système, d'où la nécessité de redémarrer pour changer cet état notamment lors d'une mise à jour par ailleurs.</p> <p>L'objectif est donc purement au niveau de la communication autour de ces systèmes. Cependant les nouvelles variantes devraient utiliser ce terme dans ce nom comme par exemple <em>Fedora XCFE Atomic</em> si jamais cette variante prend vie un jour.</p> <h3>La communauté francophone</h3> <h4>L'association</h4> <p><img src="https://forums.fedora-fr.org/assets/files/2023-04-17/1681761626-950828-logo.png" alt="" /></p> <p><a href="https://www.borsalinux-fr.org/" hreflang="fr">Borsalinux-fr</a> est l'association qui gère la promotion de Fedora dans l'espace francophone. Nous constatons depuis quelques années une baisse progressive des membres à jour de cotisation et de volontaires pour prendre en main les activités dévolues à l'association.</p> <p><a href="https://forums.fedora-fr.org/d/73957-fedora-fr-a-besoin-de-vous" hreflang="fr">Nous lançons donc un appel à nous rejoindre afin de nous aider.</a></p> <p>L'association est en effet propriétaire du <a href="https://www.fedora-fr.org/" hreflang="fr">site officiel de la communauté francophone de Fedora</a>, organise des évènements promotionnels comme les Rencontres Fedora régulièrement et participe à l'ensemble des évènements majeurs concernant le libre à travers la France principalement.</p> <p>Si vous aimez Fedora, et que vous souhaitez que notre action perdure, vous pouvez :</p> <ul><li><a href="https://www.borsalinux-fr.org/pages/Adh%C3%A9rer" hreflang="fr">Adhérer à l'association</a> : les cotisations nous aident à produire des goodies, à nous déplacer pour les évènements, à payer le matériel ;</li><li>Participer sur le forum, les listes de diffusion, à la réfection de la documentation, représenter l'association sur différents évènements francophones ;</li><li>Concevoir des goodies ;</li><li>Organiser des évènements type Rencontres Fedora dans votre ville.</li></ul> <p>Nous serions ravis de vous accueillir et de vous aider dans vos démarches. Toute contribution, même minime, est appréciée.</p> <p>Si vous souhaitez avoir un aperçu de notre activité, vous pouvez participer à nos réunions mensuels chaque premier lundi soir du mois à 20h30 (heure de Paris). Pour plus de convivialité, nous l'avons mis en place <a href="https://meet.jit.si/Borsalinux-Fr" hreflang="fr">en visioconférence sur Jitsi</a>.</p> <h4>La documentation</h4> <p>Depuis juin 2017, un grand travail de nettoyage a été entrepris sur la documentation francophone de Fedora, pour rattraper les 5 années de retard accumulées sur le sujet.</p> <p>Le moins que l'on puisse dire, c'est que le travail abattu est important : près de 90 articles corrigés et remis au goût du jour.Un grand merci à Charles-Antoine Couret, Nicolas Berrehouc, Édouard Duliège et les autres contributeurs et relecteurs pour leurs contributions.</p> <p>La synchronisation du travail se passe sur le forum.</p> <p>Si vous avez des idées d'articles ou de corrections à effectuer, que vous avez une compétence technique à retransmettre, n'hésitez pas à participer.</p> <h3>Comment se procurer Fedora Linux 40 ?</h3> <p><img src="https://forums.fedora-fr.org/assets/files/2023-04-17/1681761671-79459-mediawriter-s.png" alt="" /></p> <p>Si vous avez déjà Fedora Linux 39 ou 38 sur votre machine, vous pouvez faire une <a href="https://doc.fedora-fr.org/wiki/Mise_%C3%A0_niveau_de_Fedora" hreflang="fr">mise à niveau vers Fedora Linux 40</a>. Cela consiste en une grosse mise à jour, vos applications et données sont préservées.</p> <p>Autrement, pas de panique, vous pouvez <a href="https://doc.fedora-fr.org/wiki/T%C3%A9l%C3%A9charger_Fedora" hreflang="fr">télécharger Fedora Linux</a> avant de <a href="https://doc.fedora-fr.org/wiki/Guide_d%27installation_de_Fedora_en_images" hreflang="fr">procéder à son installation</a>. La procédure ne prend que quelques minutes.</p> <p>Nous vous recommandons dans les deux cas de procéder à une sauvegarde de vos données au préalable.</p> <p>De plus, pour éviter les mauvaises surprises, nous vous recommandons aussi de lire au préalable <a href="https://fedoraproject.org/wiki/Common_F40_bugs" hreflang="fr">les bogues importants connus à ce jour pour Fedora Linux 40</a>.</p></content:encoded> <dc:date>2024-04-28T16:08:22+00:00</dc:date></item><item rdf:about="https://blog.kulakowski.fr/?p=30412"> <title>Guillaume Kulakowski: Optimiser mon cache DNS avec dnsmasq sous Debian</title> <link>https://blog.kulakowski.fr/post/optimiser-mon-cache-dns-avec-dnsmasq-sous-debian</link> <content:encoded><p>Étape 1 : le constat Depuis que j’ai mis en place AdGuard Home, je constate beaucoup de requêtes DNS venant de Jeedom. J’avais déjà constaté cela la dernière fois, mais la solution précédente ne peut plus marcher. En effet, maintenant AdGuard Home gère tous mes DNS à la place d’OpenWRT. De plus, je constate une […]</p><p>Cet article <a href="https://blog.kulakowski.fr/post/optimiser-mon-cache-dns-avec-dnsmasq-sous-debian">Optimiser mon cache DNS avec dnsmasq sous Debian</a> est apparu en premier sur <a href="https://blog.kulakowski.fr">Guillaume Kulakowski's blog</a>.</p></content:encoded> <dc:date>2024-04-26T17:15:15+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13590"> <title>Fedora Community Blog: Infra and RelEng Update – Week 17 2024</title> <link>https://communityblog.fedoraproject.org/infra-and-releng-update-week-17-2024/</link> <content:encoded><p>This is a weekly report from the I&amp;R (<a href="https://docs.fedoraproject.org/en-US/infra/">Infrastructure &amp; Release Engineering</a>) Team. It also contains updates for CPE (<a href="https://docs.fedoraproject.org/en-US/cpe/">Community Platform Engineering</a>) Team as the CPE initiatives are in most cases tied to I&amp;R work.</p> <p>We provide you with both an infographic and a text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in-depth details look at the infographic.</p> <p>Week: 22 April – 26 April 2024</p> <span id="more-13590"></span> &lt;figure class="wp-block-image size-full is-style-default"&gt;<img width="2448" alt="I&amp;R infographic" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/Week17_WeeklyReport-1-scaled.jpg" class="wp-image-13592" height="2560" />&lt;/figure&gt; <h2 class="wp-block-heading">Infrastructure &amp; Release Engineering</h2> <p>The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.<br />It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).<br /><a href="https://issues.redhat.com/issues/?filter=12428298">List of planned/in-progress issues</a></p> <h3 class="wp-block-heading">Fedora Infra</h3> <ul><li>In progress:<ul><li>Zabbix: putting missing configuration under source control.</li> <li>Zabbix: template for handling external hosts outside iad2.</li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11815">rhel7 EOL</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11543">Migration of registry.fedoraproject.org to quay.io</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11611">add monitoring for dnf countme</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11393">Replace Nagios with Zabbix in Fedora Infrastructure</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11687">notifications do not notify</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11714">DNF countme minor changes post migration</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11820">PDC retirement</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11715">Move from iptables to firewalld</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/10383">fedoraplanet.org: Upgrade Venus to Pluto</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/8455">Move mailman to newer release of Fedora or CentOS</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11726">Setup RISC-V builder(s) VM in Fedora Infrastructure</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11711">Update compose hosts to get latest pungi release (4.6.0)</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11505">Deploy new sign hardware/software</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11826">logrotate not working on proxy31</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11641">Commits don’t end up on the scm-commits list</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11144">Create monitoring tool for rabbitmq certificates</a></li></ul></li> <li>Done:<ul><li>Zabbix: prod hosts now correctly registered with fresh server install on vmhost-x86-05.</li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11755">vmhost-x86-copr02 hardware issues</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11891">Add dns entry for pyai.fedorainfracloud.org</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11886">FMN is not relaying messages (sending notifications)</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11885">: [Errno 28] No space left on device</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11882">Create AWS Policy and service subdomain for the AI/ML SIG</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11887">504 when authenticating through id.fedoraproject.org</a></li></ul></li></ul> <h3 class="wp-block-heading">CentOS Infra including CentOS CI</h3> <ul><li>In progress:<ul><li><a href="https://pagure.io/centos-infra/issue/1358">c8s/c7 EOL infrastructure planning</a></li> <li><a href="https://pagure.io/centos-infra/issue/1398">Review all our ansible infra roles pointing to mirror.centos.org</a></li> <li><a href="https://pagure.io/centos-infra/issue/1399">Keeping builds and reducing loads on mirror</a></li> <li><a href="https://issues.redhat.com/browse/CS-2087">Set up compose testing for c10s</a></li> <li><a href="https://issues.redhat.com/browse/CS-2090">koji set-build-volume throws errors for some builds</a></li></ul></li> <li>Done:<ul><li><a href="https://pagure.io/centos-infra/issue/1240">Convert our ansible hosts to RHEL and ansible-core new version</a></li> <li><a href="https://pagure.io/centos-infra/issue/1396">Expand multipath iscsi luns on secondary reference mirror</a></li> <li><a href="https://pagure.io/centos-infra/issue/1397">blogs.centos.org broken link to mailing lists in header</a></li> <li><a href="https://pagure.io/centos-infra/issue/1400">[CloudSIG] Remove cloud9s-openstack-bobcat-testing from inherited tags in cloud9s-openstack-caracal-el9s-build</a></li> <li><a href="https://pagure.io/centos-infra/issue/1401">Request: Admin access to openshift namespace / jenkins of pagure project</a></li> <li><a href="https://issues.redhat.com/browse/CS-2095">CentOS Stream HSM/Signing issue</a></li></ul></li></ul> <h3 class="wp-block-heading">Release Engineering</h3> <ul><li>In progress:<ul><li><a href="https://pagure.io/releng/issue/8601">Packages that fail to build SRPM are not reported during the mass rebuild bugzillas</a></li> <li><a href="https://pagure.io/releng/issue/11385">Silverblue aarch64 installer image compose always fails on F38 and Rawhide</a></li> <li><a href="https://pagure.io/releng/issue/11358">Sync RCs to alt/stg dl.fp.o</a></li> <li><a href="https://pagure.io/releng/issue/11531">i686 builders need to use 32-bit inode numbers</a></li> <li><a href="https://pagure.io/releng/issue/11673">Fixes for release-candidate.sh in pungi-fedora</a></li> <li><a href="https://pagure.io/releng/issue/8929">When orphaning packages, keep the original owner as co-maintainer</a></li> <li><a href="https://pagure.io/releng/issue/7337">Emit fedmsg when candidate composes are synced to stage</a></li> <li><a href="https://pagure.io/releng/issue/9880">Publish “latest” tag to quay.io/fedora/fedora</a></li> <li><a href="https://pagure.io/releng/issue/9153">Use an automated script to control checksums of compose images</a></li> <li><a href="https://pagure.io/releng/issue/9674">Create an ansible playbook to do the mass-branching</a></li> <li><a href="https://pagure.io/releng/issue/12028">Package retirements are broken in rawhide</a></li> <li><a href="https://pagure.io/releng/issue/11957">Implement checks on package retirements</a></li> <li><a href="https://pagure.io/fedpkg/issue/509">Support for self-service package un-retirement</a></li></ul></li> <li>Done:<ul><li><a href="https://pagure.io/releng/issue/12074">Please sign the Fedora-IoT-40-20240422.3 compose for F40 IoT Final</a></li> <li><a href="https://pagure.io/releng/issue/12072">Update ref (classic ostree) is not synced to stable for Fedora Atomic Desktops 40</a></li> <li><a href="https://pagure.io/releng/issue/12068">Creation of RPM repository for emacs-filesystem partially failed</a></li> <li>Fedora 40 release</li> <li><a href="https://pagure.io/releng/issue/12009">Lenovo: F39 official iso for X1 Carbon G12 preload</a></li> <li><a href="https://pagure.io/releng/issue/12071">40_Beta-1.10 partially overwriten in /pub/alt/stage/40_Beta-1.10</a></li></ul></li></ul> <h2 class="wp-block-heading">CPE Initiatives</h2> <h3 class="wp-block-heading">EPEL</h3> <p><a href="https://docs.fedoraproject.org/en-US/epel/">Extra Packages for Enterprise Linux</a> (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high-quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux (SL) and Oracle Linux (OL).</p> <h2 class="wp-block-heading">Updates</h2> <ul><li>EPEL 10 <a href="https://hackmd.io/q6TNkYjJT82EtzhlyPGpog">Work Tracker</a><ul><li>EPEL community involved</li></ul></li> <li>Docs Revamp in progress<ul><li>Landing page with links to more information</li> <li>Onboarding page with FAQ section</li></ul></li> <li>Working on getting Troy’s will-it project to run on <a href="https://github.com/dherrerace/willit-workflow">github-actions</a></li></ul> <h3 class="wp-block-heading">Community Design</h3> <p>CPE has a few members who are working as part of the Community Design Team. This team is working on anything related to design in the Fedora Community.</p> <h2 class="wp-block-heading">Updates</h2> <ul><li>Choose Your Own Adventure Sticker <a href="https://gitlab.com/fedora/design/community-design-team/issues/-/issues/159">#159</a> in progress</li> <li>Avocado-framework logo and website design <a href="https://gitlab.com/fedora/design/community-design-team/issues/-/issues/146">#146</a> in progress</li> <li>Various stickers created for Red Hat Summit related to Podman Desktop <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f9ad.png" style="height: 1em;" class="wp-smiley" alt="🦭" /></li></ul> <hr class="wp-block-separator has-alpha-channel-opacity" /> <p>If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on <a href="https://matrix.to/#/#redhat-cpe:matrix.org">matrix</a>.</p><p>The post <a href="https://communityblog.fedoraproject.org/infra-and-releng-update-week-17-2024/">Infra and RelEng Update – Week 17 2024</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-26T10:00:00+00:00</dc:date></item><item rdf:about="urn:md5:b8572562648cde62eb706456bd5ffec6"> <title>Remi Collet: PHP version 8.2.19RC1 and 8.3.7RC1</title> <link>https://blog.remirepo.net/post/2024/04/26/PHP-version-8.2.19RC1-and-8.3.7RC1</link> <content:encoded><p><em>Release Candidate</em> versions are available in the testing repository for <strong>Fedora</strong> and <strong>Enterprise Linux</strong> (RHEL / CentOS / Alma / Rocky and other clones) to allow more people to test them. They are available as <em>Software Collections</em>, for a parallel installation, the perfect solution for such tests, and also as base packages.</p> <p>RPMs of <strong>PHP version 8.3.7RC1</strong> are available</p> <ul> <li>as base packages <ul> <li>in the <strong>remi-modular-test </strong>for<strong> Fedora </strong><strong>38-40</strong> and <strong>Enterprise Linux</strong> <strong>≥ 8</strong></li> <li>in the <strong>remi-php83-test </strong>repository for <strong>Enterprise Linux 7</strong></li> </ul> </li> <li>as <strong>SCL </strong>in <strong>remi-test</strong> repository</li></ul> <p>RPMs of <strong>PHP version 8.2.19RC1</strong> are available</p> <ul> <li>as base packages <ul> <li>in the <strong>remi-modular-test </strong>for<strong> Fedora </strong><strong>38-40</strong> and <strong>Enterprise Linux</strong> <strong>≥ 8</strong></li> <li>in the <strong>remi-php82-test </strong>repository for <strong>Enterprise Linux 7</strong></li> </ul> </li> <li>as <strong>SCL </strong>in <strong>remi-test</strong> repository</li></ul> <p><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" /> The <strong>Fedora 39, 40</strong>, <strong>EL-8</strong> and <strong>EL-9</strong> packages (modules and SCL) are available for <strong>x86_64</strong> and <strong>aarch64</strong>.</p> <p><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" /><strong>PHP version 8.1</strong> is now in security mode only, so no more RC will be released.</p> <p><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" />Installation: follow the <a href="https://rpms.remirepo.net/wizard/">wizard</a> instructions.</p> <p><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" /> Announcements:</p> <ul> <li><a href="http://news-web.php.net/php.qa/69376">PHP 8.3.7RC1 available for testing</a></li> <li><a href="http://news-web.php.net/php.qa/69376">PHP 8.2.19RC1 available for testing</a></li></ul> <p><strong>Parallel installation</strong> of version <strong>8.3</strong> as Software Collection:</p> <pre>yum --enablerepo=remi-test install php83</pre> <p><strong>Parallel installation</strong> of version <strong>8.2</strong> as Software Collection:</p> <pre>yum --enablerepo=remi-test install php82</pre> <p><strong>Update</strong> of system version <strong>8.3</strong> (EL-7) :</p> <pre>yum --enablerepo=remi-php83,remi-php83-test update php\*</pre> <p>or, the <strong>modular</strong> way (Fedora and EL ≥ 8):</p> <pre>dnf module switch-to php:remi-8.3dnf --enablerepo=remi-modular-test update php\*</pre> <p><strong>Update</strong> of system version <strong>8.2</strong> (EL-7) :</p> <pre>yum --enablerepo=remi-php82,remi-php82-test update php\*</pre> <p>or, the <strong>modular</strong> way (Fedora and EL ≥ 8):</p> <pre>dnf module switch-to php:remi-8.2dnf --enablerepo=remi-modular-test update php\*</pre> <p><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" /> Notice:</p> <ul> <li>version <strong>8.3.7RC1</strong> is also in Fedora <em>rawhide</em> for <strong>QA</strong></li> <li>EL-9 packages are built using RHEL-<strong>9.3</strong></li> <li>EL-8 packages are built using RHEL-<strong>8.9</strong></li> <li>EL-7 packages are built using RHEL-<strong>7.9</strong></li> <li><strong>oci8</strong> extension uses the <strong>RPM</strong> of the <strong>Oracle Instant Client </strong>version<strong> 21.13</strong> on <strong>x86_64</strong> or <strong>19.19</strong> on <strong>aarch64</strong></li> <li><strong>intl </strong>extension uses <strong>libicu 73.2</strong></li> <li>RC version is usually the same as the <strong>final</strong> version (no change accepted after RC, exception for security fix).</li> <li>versions 8.2.18 and 8.3.5 are planed for <strong>April 11th</strong>, in 2 weeks.</li></ul> <p align="center"><strong>Software Collections</strong> (php82, php83)</p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php83-php-common&amp;version=8.3.7~RC1&amp;lang=en" style="margin: 1em auto; display: block;" alt="" /></p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php82-php-common&amp;version=8.2.19~RC1&amp;lang=en" style="margin: 1em auto; display: block;" alt="" /></p> <p align="center"><strong>Base packages</strong> (php)</p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php-common&amp;version=8.3.7~RC1&amp;lang=en" style="margin: 1em auto; display: block;" alt="" /></p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php-common&amp;version=8.2.19~RC1&amp;lang=en" style="margin: 1em auto; display: block;" alt="" /></p></content:encoded> <dc:date>2024-04-26T04:38:00+00:00</dc:date></item><item rdf:about="https://major.io/p/java-big-cursors-wayland/"> <title>Major Hayden: Fix big cursors in Java applications in Wayland</title> <link>https://major.io/p/java-big-cursors-wayland/</link> <content:encoded>Java applications under Wayland seemed to have all different sizes of cursors, butsome were way, way, too big. 🐘</content:encoded> <dc:date>2024-04-26T00:00:00+00:00</dc:date></item><item rdf:about="https://peter.czanik.hu/other/syslog-ng-using-on-multiple-platforms/"> <title>Peter Czanik: Using syslog-ng on multiple platforms</title> <link>https://peter.czanik.hu/other/syslog-ng-using-on-multiple-platforms/</link> <content:encoded><p>Your favorite Linux distribution is X. You test everything there. However, your colleagues use distro Y, and another team distro Z. Nightmares start here: the same commands install a different set of syslog-ng features, configuration defaults and use different object names in the default configuration. I ran into these problems while working with Gábor Samu on his <a href="https://www.gaborsamu.com/blog/turingpi_syslog-ng_lsf/">HPC logging blog</a>.</p><p>From this blog you can learn about some of the main differences in packaging and configuration of syslog-ng in various Linux distributions and FreeBSD, and how to recognize these when configuring syslog-ng on a different platform.</p><p><a href="https://www.syslog-ng.com/community/b/blog/posts/using-syslog-ng-on-multiple-platforms">https://www.syslog-ng.com/community/b/blog/posts/using-syslog-ng-on-multiple-platforms</a></p>&lt;figure&gt;<img src="https://peter.czanik.hu/images/syslog-ng-logo1.png" />&lt;figcaption&gt; <h4>syslog-ng logo</h4> &lt;/figcaption&gt;&lt;/figure&gt;</content:encoded> <dc:date>2024-04-24T12:07:52+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=40186"> <title>Fedora Magazine: How to rebase to Fedora Linux 40 on Silverblue</title> <link>https://fedoramagazine.org/how-to-rebase-to-fedora-linux-40-on-silverblue/</link> <content:encoded><p>Fedora Silverblue is <a href="https://docs.fedoraproject.org/en-US/fedora-silverblue/" target="_blank" rel="noreferrer noopener">an operating system for your desktop built on Fedora Linux</a>. It’s excellent for daily use, development, and container-based workflows. It offers <a href="https://fedoramagazine.org/give-fedora-silverblue-a-test-drive/" target="_blank" rel="noreferrer noopener">numerous advantages</a> such as being able to roll back in case of any problems. If you want to update or rebase to Fedora Linux 40 on your Fedora Silverblue system, this article tells you how. It not only shows you what to do, but also how to revert things if something unforeseen happens.</p> <span id="more-40186"></span> <h2 class="wp-block-heading">Update your existing system</h2> <p>Prior to actually doing the rebase to Fedora Linux 40, you should apply any pending updates. Enter the following in the terminal:</p> <pre class="wp-block-preformatted">$ rpm-ostree update</pre> <p>or install updates through GNOME Software and reboot.</p> <h2 class="wp-block-heading">Note</h2> <p>rpm-ostree is the underlying atomic technology that all the <a href="https://fedoramagazine.org/introducing-fedora-atomic-desktops/" target="_blank" rel="noreferrer noopener">Fedora Atomic Desktops</a> use. The techniques described here for Silverblue will apply to all of them with proper modifications for the appropriate desktop.</p> <h2 class="wp-block-heading">Rebasing using GNOME Software</h2> <p>GNOME Software shows you that there is new version of Fedora Linux available on the Updates screen.</p> &lt;figure class="wp-block-image size-full is-style-default"&gt;<a href="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46.png"><img width="1199" alt="GNOME_Software_download_screenshot" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-09-58-46.png" class="wp-image-40187" height="803" /></a>&lt;/figure&gt; <p>First thing to do is download the new image, so select the <em>Download</em> button. This will take some time. When it is done you will see that the update is ready to install.</p> &lt;figure class="wp-block-image size-full"&gt;<a href="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17.png"><img width="1199" alt="GNOME_Software_update_screenshot" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-19-10-05-17.png" class="wp-image-40188" height="803" /></a>&lt;/figure&gt; <p>Select the <em>Restart &amp; Upgrade</em> button. This step will take only a few moments and the computer will restart when the update is completed. After the restart you will end up in a new and shiny release of Fedora Linux 40. Easy, isn’t it?</p> <h2 class="wp-block-heading">Rebasing using terminal</h2> <p>If you prefer to do everything in a terminal, then this part of the guide is for you.</p> <p>Rebasing to Fedora Linux 40 using the terminal is easy. First, check if the 40 branch is available:</p> <pre class="wp-block-preformatted">$ ostree remote refs fedora</pre> <p>You should see the following in the output:</p> <pre class="wp-block-preformatted">fedora:fedora/40/x86_64/silverblue</pre> <p>If you want to pin the current deployment (meaning that this deployment will stay as an option in GRUB until you remove it), you can do this by running this command:</p> <pre class="wp-block-preformatted"># 0 is entry position in rpm-ostree status$ sudo ostree admin pin 0</pre> <p>To remove the pinned deployment use the following command:</p> <pre class="wp-block-preformatted"># 2 is entry position in rpm-ostree status $ sudo ostree admin pin --unpin 2</pre> <p>Next, rebase your system to the Fedora Linux 40 branch.</p> <pre class="wp-block-preformatted">$ rpm-ostree rebase fedora:fedora/40/x86_64/silverblue</pre> <p>Finally, the last thing to do is restart your computer and boot to Fedora Linux 40.</p> <h2 class="wp-block-heading">How to roll back</h2> <p>If anything bad happens (for instance, if you can’t boot to Fedora Linux 40 at all) it’s easy to go back. At boot time, pick the entry in the GRUB menu for the version prior to Fedora Linux 40 and your system will start in that previous version rather than Fedora Linux 40. If you don’t see the GRUB menu, try to press ESC during boot. To make the change to the previous version permanent, use the following command:</p> <pre class="wp-block-preformatted">$ rpm-ostree rollback</pre> <p>That’s it. Now you know how to rebase Fedora Silverblue to Fedora Linux 40 and roll back. So why not do it today?</p> <h2 class="wp-block-heading">FAQ</h2> <p>Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.</p> <p><strong>Question: Can I skip versions during rebase of Fedora? For example from Fedora 38 Silverblue to Fedora 40 Silverblue?</strong></p> <p>Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (38-&gt;39 for example) to avoid unnecessary errors.</p> <p><strong>Question: I have <a href="https://rpmfusion.org/" target="_blank" rel="noreferrer noopener">rpm-fusion</a> layered and I get errors during rebase. How should I do the rebase?</strong></p> <p>Answer: If you have <a href="https://rpmfusion.org/" target="_blank" rel="noreferrer noopener">rpm-fusion</a> layered on your Silverblue installation, you should do the following before rebase:</p> <pre class="wp-block-preformatted">$ rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release</pre> <p>After doing this you can follow the guide in this blog post.</p> <p><strong>Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?</strong></p> <p>Yes, you can follow the <em>Rebasing using the terminal</em> part of this guide for every Fedora Atomic Desktop. Just use the corresponding branch. For example, for Kinoite use <kbd>fedora:fedora/40/x86_64/kinoite</kbd></p> <p></p></content:encoded> <dc:date>2024-04-24T08:00:00+00:00</dc:date></item><item rdf:about="http://fossjon.wordpress.com/?p=5962"> <title>Jon Chiappetta: Mode Envoy Typing Sound</title> <link>https://fossjon.wordpress.com/2024/04/23/mode-envoy-typing-sound/</link> <content:encoded>&lt;figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"&gt;<div class="wp-block-embed__wrapper"><div class="embed-youtube">&lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen="allowfullscreen" frameborder="0" height="567" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/daL5D488w6M?feature=oembed" title="Mode Envoy Typing Sound" width="1008"&gt;&lt;/iframe&gt;</div></div>&lt;/figure&gt; <p>~</p> &lt;figure class="wp-block-image size-large"&gt;<a href="https://fossjon.files.wordpress.com/2024/04/envoy_tape.png"><img width="1024" alt="" src="https://fossjon.files.wordpress.com/2024/04/envoy_tape.png?w=1024" class="wp-image-5964" height="576" /></a>&lt;/figure&gt; <p>~</p> &lt;figure class="wp-block-image size-large"&gt;<a href="https://fossjon.files.wordpress.com/2024/04/envoy_screw.png"><img width="1024" alt="" src="https://fossjon.files.wordpress.com/2024/04/envoy_screw.png?w=1024" class="wp-image-5966" height="576" /></a>&lt;/figure&gt;</content:encoded> <dc:date>2024-04-24T00:48:22+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=40232"> <title>Fedora Magazine: OMG! We’re at forty! (Announcing the release of Fedora Linux 40)</title> <link>https://fedoramagazine.org/announcing-fedora-linux-40/</link> <content:encoded><p>Oh, wow. This feels like a big number! I’m proud to announce the 40th release of Fedora Linux, a community-built and community-maintained operating system that belongs to <em>all</em> of us. I’m also happy to note that we’re back on track with an on-time release. Thank you to all Fedora contributors who made that possible, and who have, yet again, made this our best one ever.</p> <span id="more-40232"></span> <p>This is also a <em>personally</em> exciting number for me, because this marks the <em>20th</em> release for which I’ve served as Fedora Project Leader. We’ve gone through a lot in this last decade, and I’m incredibly happy to see our community thrive and grow. In addition to many long-familiar names and faces, it’s exciting to see a new generation with new energy and ideas. In some cases, this is <em>literally </em>a new generation, as many of you have grown up with Fedora. But at whatever age, I’m proud we’ve built such a welcoming and friendly community, and that we continue to work at improving our inclusiveness, diversity, and accessibility.</p> <p>But anyway! Enough of that. Time to see what we’ve got for you in Fedora Linux 40! If you have a system already, <a href="https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/" target="_blank" rel="noreferrer noopener">Upgrading Fedora to a New Release</a> is easy. If you’re new, or just curious, head to <a href="https://fedoraproject.org" target="_blank" rel="noreferrer noopener">Get Fedora</a> for installation options.</p> <h2 class="wp-block-heading">Desktop news</h2> <p>Fedora Workstation Edition features the GNOME desktop environment, now updated to version 46. Check out <a href="https://fedoramagazine.org/whats-new-fedora-workstation-40" target="_blank" rel="noreferrer noopener">What’s New in Fedora Workstation 40?</a> for the highlights!</p> <p>The KDE Spin now includes KDE Plasma 6, and runs with Wayland out of the box. Read more about that and other KDE Spin updates at <a href="https://fedoramagazine.org/whats-new-in-fedora-kde-40">What’s New in Fedora KDE 40?</a></p> <p>We’re also officially reviving the “Fedora Atomic Desktop” brand for all of our variants which use ostree or image-based provisioning. Our technology isn’t really “immutable”, so this provides a better grouping. Read more about this at <a href="https://fedoramagazine.org/introducing-fedora-atomic-desktops/" target="_blank" rel="noreferrer noopener">Introducing Fedora Atomic Desktops</a> — but in short, Fedora Silverblue and Fedora Kinoite will remain, while the other desktop variants will become Fedora Sway Atomic and Fedora Budgie Atomic.</p> <h2 class="wp-block-heading">Tools for AI development</h2> <p>Fedora Linux 40 ships with our first-ever PyTorch package. PyTorch is a popular framework for deep learning, and it can be difficult to reliably install with the right versions of drivers and libraries and so on. The current package only supports running on the CPU, without GPU or NPU acceleration, but this is just the first step. Our aim is to produce a complete stack with PyTorch and other popular tools ready to use on a wide variety of hardware out-of-the-box.</p> <p>We’re also shipping with ROCm 6 — open-source software that provides acceleration support for AMD graphics cards. We plan to have that enabled for PyTorch in a future release.</p> <h2 class="wp-block-heading">Updates all around!</h2> <p>As usual, we’ve rebuilt everything in the distribution using updated compilers and libraries (and, of course, those updated tools are ready for developers to use). These updates bring bugfixes, security improvements, and performance gains.</p> <p>And, of course, hundreds of Fedora packagers and testers have worked to integrate the latest versions of open source software from thousands of upstream projects. Those projects, in turn, are made by an uncountable number of developers and contributors working on marketing, design, documentation, code, quality, translations, communications, events, governance, infrastructure, security, and so much more. Thank you again to everyone who makes Fedora amazing, and to everyone whose work has built this whole universe of free and open source software.</p> <h2 class="wp-block-heading">Speaking of updates…</h2> <p>There are several important release-day bugfix and security updates available today as well. If you upgrade from an earlier Fedora Linux release, you’ll get them as part of that. For new installations, please make sure to check for and apply updates as soon as possible.</p> <h2 class="wp-block-heading">In the unlikely event of a problem…</h2> <p>If you run into a problem, visit our<a href="https://ask.fedoraproject.org/" target="_blank" rel="noreferrer noopener"> Ask Fedora</a> user support forum. This includes a category for<a href="https://discussion.fedoraproject.org/tags/c/ask/common-issues/82/none/f40" target="_blank" rel="noreferrer noopener"> common issues</a>. </p> <h2 class="wp-block-heading">Or if you just want to say “hello”…</h2> <p>Drop by our<a href="https://discussion.fedoraproject.org/c/fun/8" target="_blank" rel="noreferrer noopener"> “virtual watercooler” on Fedora Discussion</a> and join a conversation, share something interesting, and introduce yourself.</p> <p>Also, remember that our annual contributor conference, <a href="https://flocktofedora.org/" target="_blank" rel="noreferrer noopener">Flock To Fedora</a>, is coming up! It’ll be in Rochester, New York this August. The <a href="https://communityblog.fedoraproject.org/flock-2024-cfp-until-april-21st/" target="_blank" rel="noreferrer noopener">call for session proposals</a> is still open, if you have something you’d like to share or work on. If you’re already a Fedora contributor, or are interested in being one, or think you might be, we’d love to see you there!</p></content:encoded> <dc:date>2024-04-23T14:00:00+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=40175"> <title>Fedora Magazine: Slimbook Fedora 2: New Ultrabooks for Fedora Linux 40</title> <link>https://fedoramagazine.org/slimbook-fedora-2-new-ultrabooks-for-fedora-linux-40/</link> <content:encoded><p>The response from the Fedora community to the Fedora Slimbook 16” and 14” has been great! More and more people are noticing the quality of these laptops. We’ve even had a demo unit at events like <strong>FOSDEM</strong> and <strong>SCaLE</strong> for community members to play with.</p> <p>To build on that excitement, Slimbook and the Fedora Project are announcing <a href="https://fedora.slimbook.com/" target="_blank" rel="noreferrer noopener"><strong>Slimbook Fedora 2</strong></a>!</p> <span id="more-40175"></span> <h2 class="wp-block-heading">Slimbook Fedora 2</h2> <p>The Slimbook Fedora 2 comes in the 14” and 16” models and brings with it fantastic new options.</p> <ul><li>Silver is popular, but how about a <strong>smooth black Magnesium chassis</strong>?</li> <li>For those who need it, you now have the option of a <strong>US ANSI keyboard layout</strong> so you can work without skipping a beat!</li> <li>CPU is being upgraded to <strong>Intel’s 13th Gen i7</strong> processor</li> <li>Take your work to the next level with the <strong>Nvidia RTX 4000 series</strong> graphics card in the 16” model</li></ul> <p>Of course we can’t forget that the Slimbook Fedora 2 will also come with the Fedora logo engraved on the lid, as well as on the super key. <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f609.png" style="height: 1em;" class="wp-smiley" alt="😉" /></p> <p>This hardware update comes with a software upgrade courtesy of Fedora’s latest release, <strong>Fedora Workstation 40</strong>. Featuring<strong> GNOME 46</strong> and numerous other enhancements, Slimbook Fedora 2 continues to be a great travel companion. Fedora Linux 40 also comes with the latest <strong>Nouveau</strong> drivers to give you a much better out of the box experience with the Nvidia graphics card in the 16” model.</p> <p>Slimbook is dedicated to supporting open source initiatives. As part of that, 3% of the proceeds from each Slimbook Fedora unit sold will continue to be donated to the <strong>GNOME Foundation</strong>.</p> <p>Besides that there is also the Fedora contributor discount which gives you an additional €100 off! If you’re a contributor to the Fedora Project you can find more info on how to get this discount from<a href="https://communityblog.fedoraproject.org/fedora-slimbook-contributor-discount/"> this Community Blog post</a>.</p> <p>Additionally, Slimbook offers a €150 discount for everyone on last year’s model. You can purchase the previous model with a discount through this link: <a href="https://fedora.slimbook.com" target="_blank" rel="noreferrer noopener">https://fedora.slimbook.com</a>.</p> &lt;figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex"&gt;&lt;figure class="wp-block-image size-large"&gt;<img width="1024" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_back-1024x768.jpg" class="wp-image-40176" height="768" />&lt;/figure&gt; &lt;figure class="wp-block-image size-large"&gt;<img width="1024" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black_front-1024x819.jpg" class="wp-image-40177" height="819" />&lt;/figure&gt; &lt;figure class="wp-block-image size-large"&gt;<img width="1024" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Fedora_Black-1024x819.jpg" class="wp-image-40178" height="819" />&lt;/figure&gt; &lt;figure class="wp-block-image size-large"&gt;<img width="1024" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Tecla-Fedora-Black-1024x682.png" class="wp-image-40179" height="682" />&lt;/figure&gt;&lt;/figure&gt; <p>More details below:</p> <h4 class="wp-block-heading">Slimbook Fedora 2, 16” Model</h4> <ul><li>Intel® Core<img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2122.png" style="height: 1em;" class="wp-smiley" alt="™" /> i7-13700H Processor</li> <li>NVIDIA GeForce RTX<img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2122.png" style="height: 1em;" class="wp-smiley" alt="™" /> 4060 GPU</li> <li>Sleek Color Options: Silver and Black (magnesium chassis)</li> <li>16-inch 16:10, 100% sRGB, 90Hz Display (2560 x 1600 Resolution)</li> <li>Versatile Keyboard Options: ISO and ANSI (Available in almost any language)</li> <li>Up to 64 GB SO-DIMM DDR5 RAM (removable)</li> <li>Up to 8 TB M.2 SSD NVMe Gen 4.0 (removable)</li> <li>Thunderbolt 4 &amp; USB-C 3.2 Gen2 10Gbps</li> <li>82 Wh Battery</li> <li>Lightweight Design: 1.6 kg (3.5 lbs)<br /></li></ul> <h4 class="wp-block-heading">Slimbook Fedora 2, 14” Model</h4> <ul><li>Intel® Core<img src="https://s.w.org/images/core/emoji/15.0.3/72x72/2122.png" style="height: 1em;" class="wp-smiley" alt="™" /> i7-13700H Processor</li> <li>Sleek Color Options: Silver and Black</li> <li>14-inch 16:10, 100% sRGB, 90Hz Display (2880 x 1800 Resolution)</li> <li>Versatile Keyboard Options: ISO and ANSI</li> <li>Up to 64 GB SO-DIMM DDR5 RAM (removable)</li> <li>Up to 8 TB M.2 SSD NVMe Gen 4.0 (removable)</li> <li>Thunderbolt 4 &amp; USB-C 3.2 Gen2 10Gbps</li> <li>99 Wh Battery</li> <li>Lightweight Design: 1.3 kg (2.8 lbs)</li></ul> <p>Check out both new Slimbook Fedora 2 models at <a href="https://fedora.slimbook.com/">https://fedora.slim</a><a href="https://fedora.slimbook.com/" target="_blank" rel="noreferrer noopener">b</a><a href="https://fedora.slimbook.com/">ook.com/</a>! </p> <p><strong>Additional Resources</strong></p> <ul><li>Learn more about<a href="https://fedora.slimbook.es/" target="_blank" rel="noreferrer noopener"> Slimbook Fedora</a></li> <li>Follow Slimbook on<a href="https://linuxrocks.online/@slimbook" target="_blank" rel="noreferrer noopener"> Mastodon</a></li> <li>Follow Slimbook on<a href="https://x.com/slimbook" target="_blank" rel="noreferrer noopener"> Twitter</a></li> <li>Follow Slimbook on<a href="https://www.instagram.com/slimbook/" target="_blank" rel="noreferrer noopener"> Instagram</a></li> <li>Follow Slimbook on<a href="https://www.facebook.com/slimbook.es" target="_blank" rel="noreferrer noopener"> Facebook</a></li> <li>Follow Slimbook on<a href="https://www.youtube.com/@slimbook-laptops" target="_blank" rel="noreferrer noopener"> YouTube</a></li> <li>Learn more about the<a href="https://fedoraproject.org/" target="_blank" rel="noreferrer noopener"> Fedora Project</a></li> <li>Follow the Fedora Project on<a href="https://fosstodon.org/@fedora" target="_blank" rel="noreferrer noopener"> Mastodon</a></li> <li>Follow the Fedora Project on<a href="https://twitter.com/fedora?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor" target="_blank" rel="noreferrer noopener"> Twitter</a></li> <li>Follow the Fedora Project on<a href="https://www.instagram.com/thefedoraproject/" target="_blank" rel="noreferrer noopener"> Instagram</a></li> <li>Follow the Fedora Project on<a href="https://www.facebook.com/fedoraproject.org/" target="_blank" rel="noreferrer noopener"> Facebook</a></li> <li>Follow the Fedora Project on <a href="https://www.linkedin.com/company/fedora-project" target="_blank" rel="noreferrer noopener">LinkedIn</a></li> <li>Subscribe to the Fedora Project on<a href="https://www.youtube.com/@fedora" target="_blank" rel="noreferrer noopener"> YouTube</a></li></ul></content:encoded> <dc:date>2024-04-23T13:58:00+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=40214"> <title>Fedora Magazine: What’s New in Fedora KDE 40?</title> <link>https://fedoramagazine.org/whats-new-in-fedora-kde-40/</link> <content:encoded><p>Fedora Linux is a community developed and maintained operating system. <a href="https://fedoraproject.org/spins/kde/">Fedora KDE</a> is one of our adaptations of Fedora Linux for your laptop or desktop. With this milestone release of Fedora KDE 40, we hope that you’ll be interested in trying an OS that belongs to you from start to finish, from install to first shut down, from UI customizations to major changes under the hood! </p> <span id="more-40214"></span> <h2 class="wp-block-heading">KDE Plasma 6</h2> <p>The all-encompassing change in Fedora KDE 40 is the introduction of KDE Plasma 6. It’s the first major release of the Plasma desktop environment in nine years! Additionally, Fedora KDE is one of the first major distros to ship Plasma 6, and we’re the first Fedora Linux desktop variant to ship Wayland-only (not to worry, we retain full support for X11 applications!), enabling the project to push forward improvements to Wayland for the benefit of the entire Linux community. This builds upon the work done in previous Fedora Linux releases to have Fedora KDE run in Wayland from login to shutdown by default.</p> &lt;figure class="wp-block-image size-large"&gt;<a href="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-21-16-42-00.png"><img width="1024" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/Screenshot-from-2024-04-21-16-42-00-1024x576.png" class="wp-image-40217" height="576" /></a>&lt;/figure&gt; <h3 class="wp-block-heading">Featured Highlights</h3> <ul><li>There’s a new Overview Effect for keeping tabs on all of your open applications across all your virtual desktops.</li> <li>Partial support for <a href="https://en.wikipedia.org/wiki/High_dynamic_range" target="_blank" rel="noreferrer noopener">HDR</a> is implemented in this release on the way to having full support.</li> <li>Accessibility improvements have been introduced with color blindness correction filters.</li> <li>A new look to the taskbar comes in the form of a floating panel! Plasma 6 also makes customizing panels easier than ever with an understandable UI to help users make the changes they want with minimal effort.</li> <li>The Breeze UI theme that has been a hallmark of Plasma for a while gets a refresh with simplifications and modernizations where needed.</li> <li>NeoChat, KDE’s Matrix client, is provided by default for you to try.</li> <li>The Cube has returned! The new Overview Effect is cool, but using the Cube to manage your virtual desktops is a fantastic party trick to impress your friends next time you’re sharing your screen. <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f609.png" style="height: 1em;" class="wp-smiley" alt="😉" /></li></ul> <p>You can find more changes and improvements in KDE Plasma 6 from their <a href="https://kde.org/announcements/megarelease/6/">megarelease page</a>!</p> <h3 class="wp-block-heading">A word about Kinoite…</h3> <p>If you have an interest in what all of the immutable / atomic / cloud-native / composable / image-based fuss is about, <a href="https://fedoramagazine.org/introducing-fedora-atomic-desktops/" target="_blank" rel="noreferrer noopener">Fedora Atomic Desktops</a> is a great entry point into that world. Case in point, check out <a href="https://fedoraproject.org/atomic-desktops/kinoite/">Fedora Kinoite 40</a>, an atomic implementation of Fedora KDE that also comes with Plasma 6!</p> <h2 class="wp-block-heading">Also check out…</h2> <p>All of the fun events Fedora has coming up! </p> <ul><li>Be on the lookout for dates for the Fedora 40 Release Party, a virtual, user-focused, two day conference all about the new things in Fedora and the exciting things happening from our contributors. Will (hopefully) happen in May.</li> <li><a href="http://devconf.cz" target="_blank" rel="noreferrer noopener">DevConf.CZ</a> on June 13-15.</li> <li><a href="https://flocktofedora.org/" target="_blank" rel="noreferrer noopener">Flock to Fedora</a>, our in-person, contributor-focused conference, will be happening on August 7-10. </li> <li><a href="http://devconf.us" target="_blank" rel="noreferrer noopener">DevConf.US</a> follows right after on August 14-16.</li> <li>KDE’s contributor conference, <a href="https://akademy.kde.org/2024/" target="_blank" rel="noreferrer noopener">Akademy</a>, will come to Germany on September 7-12.</li></ul> <p>Thanks for learning about Fedora KDE 40. We hope that it will continue to be the reliable and exciting desktop OS you know and love. Share your appreciation or feedback on social media with #FedoraKDE!</p> <p><a href="https://fedoraproject.org/spins/kde/" target="_blank" rel="noreferrer noopener">Try Fedora KDE 40 today!</a></p></content:encoded> <dc:date>2024-04-23T13:56:00+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=39923"> <title>Fedora Magazine: What’s new in Fedora Workstation 40</title> <link>https://fedoramagazine.org/whats-new-fedora-workstation-40/</link> <content:encoded><p>Fedora Workstation, the flagship open source Linux desktop OS from the Fedora Project, has reached a new milestone with the release of Fedora Workstation 40. This release has been made possible due to the contributions of our global community, including your contributions! Fedora Workstation 40 comes packed with new features and performance enhancements that promise a smoother and more responsive computing experience. Read on to learn about the latest features and improvements in the sections below. You can download Fedora Workstation 40 from the <a href="https://fedoraproject.org/workstation/" target="_blank" rel="noreferrer noopener">Fedora Workstation webpage</a>, or upgrade your existing install within the Software app or with <em><a href="https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/" target="_blank" rel="noreferrer noopener">dnf system-upgrade</a></em> in your favorite terminal emulator.</p> <span id="more-39923"></span> <h1 class="wp-block-heading">GNOME 46</h1> <p>Fedora Workstation 40 features GNOME 46, the latest version of the GNOME desktop environment. Key updates include a notable upgrade of the Files app, introducing new features and enhancements. Additionally, many aspects of accessibility have received improvements, ensuring a more inclusive user experience. The Settings app and other core apps have been refined for better usability. More details can be found in the <a href="https://release.gnome.org/46/" target="_blank" rel="noreferrer noopener">GNOME 46 release notes</a>.</p> <p>Many other improvements have been made throughout GNOME 46, such as:</p> <ul><li>Grouping of notifications by app. Now, each notification has a header. It shows the app’s name and icon. This makes it possible to see which app sent an alert. Notification now also has an expand button.</li></ul> <ul><li>You can now open a new window for apps pinned to the dash by adding the<em> Ctrl </em>modifier. For example: <em>Super</em>+<em>Ctrl</em>+<em>1 </em>opens a new window for the first app in the dash, complementing the existing shortcut of <em>Super</em>+<em>&lt;Number&gt;</em> that launches the app itself.</li></ul> <ul><li>By default, Tap to Click is now enabled for touchpad.</li></ul> <ul><li>GNOME 46 now features Remote Login option. You can remotely connect using RDP to a new dedicated desktop session when there isn’t an active session.</li></ul> <h1 class="wp-block-heading">Core apps</h1> <p>GNOME’s core applications have had significant improvements in the new version. Some of these include:</p> <h3 class="wp-block-heading">Settings</h3> <p>GNOME 46 comes with exciting updates to the Settings app, making it more user-friendly than ever. The latest version has more keyboard mnemonics which make navigation easier. It also has a sleek modern interface. The appearance settings load faster than before and with sharper previews. This new release provides more precise control of Wacom stylus pressure. </p> <p>In addition to the upgrades mentioned above, the Settings app has received major improvements that are worth mentioning:</p> <ul><li>The Settings app has a new system panel. It groups <em>Region &amp; Language</em>, <em>Date &amp; Time</em>, <em>Remote Desktop</em>, and<em> About</em> into one settings pane. This new design makes the app easier to navigate.</li></ul> <ul><li>GNOME 46 has updated touchpad settings with two new options. The first, called Secondary Click, lets you choose how to perform a right-click on the touchpad: either with two fingers or by clicking in a corner. The second option allows you to keep the touchpad active while typing, which helps in some apps and games where you need to use the keyboard and touchpad at the same time.</li></ul> <h3 class="wp-block-heading">Files</h3> <ul><li>One of the notable upgrades to Files is the introduction of a new global search feature. The global search feature lets you search files across all configured locations. You can search the contents of files, filter files by type and modification date, and search multiple locations at once. Click the icon next to the file path field to activate this feature.</li></ul> <ul><li>In GNOME 46, the sidebar dynamic progress section at the bottom allows you to monitor file operations more effectively with more details on their progress.</li></ul> <ul><li>Switching between list and grid views in Files now happens quickly. This fixes the lag noticed in prior versions.</li></ul> <p>Other changes to the Files app include a new search field within the Files preferences. It helps find specific settings. There’s now also an option to show date and time in a consistent format, and improved network discovery. These refinements make managing files more efficient.</p> <h3 class="wp-block-heading"><strong>Other core applications have also received upgrades</strong></h3> <ul><li>The Software app now displays verified badges for trusted Flathub apps, ensuring software authenticity. </li></ul> <ul><li>Maps app offers a new editing experience, support for dark mode, and expanded public transit routing. </li></ul> <ul><li>The Extensions and Calendar apps boast modernized designs and usability improvements. </li></ul> <ul><li>GNOME 46 upgrades Clocks and Contacts apps. It lets you set a timer quickly in Clocks. And, import multiple VCard files at once in Contacts.</li></ul> <ul><li>The Disks app has a new I/O resource graph for monitoring disk usage. </li></ul> <h1 class="wp-block-heading">Performance Improvements</h1> <p>GNOME 46 provides substantial under-the-hood improvements for a more efficient and polished experience. Key improvements include:</p> <ul><li>Reduced memory usage in search.</li></ul> <ul><li>Significant speed boosts in terminal apps. </li></ul> <ul><li>More appealing visuals as app interfaces appear sharper, text on the screen clearer, and UI elements more defined, particularly when using fractional display scales due to GTK’s new renders.</li></ul> <ul><li>Experimental support for Variable Refresh Rate (VRR) for smoother video performance. You can enable this feature with the command: <br /><kbd> <em>gsettings set org.gnome.mutter experimental-features "['variable-refresh-rate']"</em></kbd><br />Once enabled, the refresh rate can be set in the display settings.</li></ul> <h1 class="wp-block-heading">Under-the-hood changes in Fedora Linux 40</h1> <p>Fedora Linux 40 features many under-the-hood changes. Here are some notable ones:</p> <ul><li>IPV4 Address Conflict Detection is enabled by default in NetworkManager to address conflicts caused by duplicate IPV4 addresses in the same physical network.</li></ul> <ul><li>Fedora 40 integrates PyTorch directly into its software repository. This makes it easier for users to access the open source machine learning framework for their projects. Installation is now a breeze through a single command: <br /> <em>sudo dnf install python3-torch</em></li></ul> <ul><li>Starting with Fedora Linux 40, the term “immutable” will no longer be used to describe all rpm-ostree based variants of Fedora Linux (Silverblue, Kinoite, Sway and Budgie). Instead, they will be referred to as “Atomic” desktops with Sericea now known as Fedora Atomic Sway. This change is part of a rebranding aimed at simplifying the naming conventions for Fedora spins. <a href="https://fedoramagazine.org/introducing-fedora-atomic-desktops/" target="_blank" rel="noreferrer noopener">More information on this change may be found here.</a></li></ul> <h1 class="wp-block-heading">Also check out…</h1> <p>Cool happenings throughout the Fedora Project!</p> <p>Stay tuned and get ready to engage with the Fedora community at some upcoming events! In June, join us in Brno, Czechia, for the DevConf CZ conference — a gathering filled with insightful discussions, workshops, and the chance to meet fellow enthusiasts. </p> <p>Then, mark your calendars for August, when our flagship contributor conference, Flock, takes place. For more details on Flock 2024, check out this <a href="https://fedoramagazine.org/flock-2024-rochester-new-york/" target="_blank" rel="noreferrer noopener">post</a>.</p></content:encoded> <dc:date>2024-04-23T13:54:00+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13576"> <title>Fedora Community Blog: Fedora Ops Architect Weekly</title> <link>https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-6/</link> <content:encoded><p>And what a week it was! Fedora Linux 40 got the ‘GO’ at the Go/No-Go meeting on Thursday so that means a brand new release of Fedora Linux is arriving to you tomorrow, Tuesday 23rd April!</p> <p>Read on to hear about other exciting Fedora news <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f642.png" style="height: 1em;" class="wp-smiley" alt="🙂" /></p> <span id="more-13576"></span> <h2 class="wp-block-heading">CfPs &amp; Events</h2> <h4 class="wp-block-heading">Flock to Fedora</h4> <p>The CfP for <a href="https://flocktofedora.org/">Flock to Fedora</a> has been extended until <a href="https://communityblog.fedoraproject.org/flock-2024-cfp-extended-to-april-29th/">Monday April 29th</a>, so dont delay if you have been thinking about submitting something – here is your chance!</p> <h4 class="wp-block-heading">Devconf.us</h4> <p><a href="https://www.devconf.info/us/">Devconf.us</a> is returning this year in Boston, MA from August 14th – 16th. Their cfp is closing today, so get it in quick if you have had something in draft.</p> <h2 class="wp-block-heading">Fedora Linux 41</h2> <p>Now that F40 is releasing, attention will be on the development of F41 which has been happening for a while now. Here are some deadlines for all you change proposal enthusiasts, and for other key dates like the beginning of the Beta freeze and mass rebuild, please view the <a href="https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html">release schedule</a>.</p> <ul><li>June 19th – Changes requiring infrastructure changes</li> <li>June 25th – Changes requiring mass rebuild</li> <li>June 25th – System Wide changes</li> <li>July 16th – Self Contained changes</li></ul> <p>If you are unsure of how to propose a change, there is some excellent <a href="https://docs.fedoraproject.org/en-US/program_management/changes_guide/">documentation</a> and <a href="https://www.youtube.com/watch?v=oERoxg-VYPo">video tutorial</a> to help, and you can always reach out directly to me too.</p> <p>Changes currently in discussion are:</p> <ul><li><a href="https://fedoraproject.org/wiki/Changes/Python_built_with_gcc_O3">Changes/Python built with gcc O3</a><a href="https://fedoraproject.org/wiki/Changes/Replace_Redis_With_Valkey">Changes</a></li></ul> <ul><li><a href="https://fedoraproject.org/wiki/Changes/Replace_Redis_With_Valkey">Replace Redis With Valkey</a><a href="https://fedoraproject.org/wiki/Changes/ReproduciblePackageBuilds">Changes</a></li></ul> <ul><li><a href="https://fedoraproject.org/wiki/Changes/ReproduciblePackageBuilds">ReproduciblePackageBuilds</a></li></ul> <p>A full list of the already accepted changes for Fedora Linux 41 can be found on the <a href="https://fedoraproject.org/wiki/Releases/41/ChangeSet">change set page</a> too.</p> <h2 class="wp-block-heading">Elections</h2> <p>The <a href="https://fedorapeople.org/groups/schedule/f-40/f-40-elections-tasks.html">F40 elections </a>will begin soon! There are some changes to this cycle, which you can read about them in more detail in the Elections blog post coming later this week and do consider nominating yourself or someone you think would be a great person on Council, FESCo, Mindshare or EPEL when the nominations page is live. Please do make sure the person you are nominating is on board with their nomination too <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f642.png" style="height: 1em;" class="wp-smiley" alt="🙂" /></p> <h2 class="wp-block-heading">Help Wanted</h2> <p>Help is always greatly appreciated.We also have some packages needing some new maintainers and others needing reviews. See below links to adopt and review packages!</p> <ul><li><a href="https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/DYIYLRPXVYOQWQI36O5IIY5FZN7GHXD2/">Orphaned Packages looking for new maintainers</a></li> <li><a href="https://fedoraproject.org/PackageReviewStatus/">Package Reviews Needed</a></li></ul> <p></p><p>The post <a href="https://communityblog.fedoraproject.org/fedora-ops-architect-weekly-6/">Fedora Ops Architect Weekly</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-22T21:25:33+00:00</dc:date></item><item rdf:about="https://badges.fedoraproject.org/badge/red-hat-summit-2024"> <title>Fedora Badges: New badge: Red Hat Summit 2024 !</title> <link>https://badges.fedoraproject.org/badge/red-hat-summit-2024</link> <content:encoded><img src="https://infrastructure.fedoraproject.org/infra/badges/pngs/events-rhsummit2024.png" alt="Red Hat Summit 2024" />You visited Fedora at Red Hat Summit 2024</content:encoded> <dc:date>2024-04-22T21:19:31+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13577"> <title>Fedora Community Blog: Flock 2024 CFP extended to April 29th</title> <link>https://communityblog.fedoraproject.org/flock-2024-cfp-extended-to-april-29th/</link> <content:encoded><p>The Flock to Fedora 2024 call for proposals (CFP) is now <strong>extended to Monday, April 29th 2024 at 11:59 PM US Eastern</strong>. Now is the last chance to get your great idea or topic into the Flock 2024 CFP before it closes. This will be the only extension and the new deadline is final.</p> <p>See the <a href="https://communityblog.fedoraproject.org/flock-2024-cfp-until-april-21st/">previous announcement</a> for more details about the Flock 2024 CFP. You can also submit directly at <a href="https://cfp.fedoraproject.org/flock-2024/cfp" target="_blank" rel="noreferrer noopener">cfp.fedoraproject.org</a>. For general questions about Flock and the CFP, join the Fedora Chat room on Matrix, <em><a href="https://matrix.to/#/#flock:fedoraproject.org" target="_blank" rel="noreferrer noopener">#flock:fedoraproject.org</a></em>.</p><p>The post <a href="https://communityblog.fedoraproject.org/flock-2024-cfp-extended-to-april-29th/">Flock 2024 CFP extended to April 29th</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-22T16:20:29+00:00</dc:date></item><item rdf:about="tag:neuroblog.fedoraproject.org,2024-04-22:/2024/04/22/next-open-neurofedora-meeting-22-april-1300-utc.html"> <title>The NeuroFedora Blog: Next Open NeuroFedora meeting: 22 April 1300 UTC</title> <link>https://neuroblog.fedoraproject.org/2024/04/22/next-open-neurofedora-meeting-22-april-1300-utc.html</link> <content:encoded><center><div class="figure"><a href="https://neuroblog.fedoraproject.org/feeds/all.atom.xml" class="reference external image-reference"><img src="https://neuroblog.fedoraproject.org/images/20200112-image.jpg" style="width: 80%;" class="img-responsive" alt="Photo by William White on Unsplash" /></a><p class="caption">Photo by <a href="https://unsplash.com/@wrwhite3?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText" class="reference external">William White</a> on <a href="https://unsplash.com/s/photos/community?utm_source=unsplash&amp;amp;utm_medium=referral&amp;amp;utm_content=creditCopyText" class="reference external">Unsplash</a>.</p></div></center><br /><p>Please join us at the next regular Open NeuroFedora team meeting on Monday 22 April at 1300 UTC.The meeting is a public meeting, and open for everyone to attend.You can join us in the <a href="https://matrix.to/#/#meeting:fedoraproject.org" class="reference external">Fedora meeting channel on chat.fedoraproject.org (our Matrix instance)</a>.Note that you can also access this channel from other Matrix home severs, so you do not have to create a Fedora account just to attend the meeting.</p><p>You can use <a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting&amp;iso=20240422T13&amp;p1=1440&amp;ah=1" class="reference external">this link</a> to convert the meeting time to your local time.Or, you can also use this command in the terminal:</p><div class="highlight"><pre><span></span>$<span class="w"> </span>date<span class="w"> </span>-d<span class="w"> </span><span class="s1">'Monday, April 22, 2024 13:00 UTC'</span></pre></div><p>The meeting will be chaired by <a href="https://fedoraproject.org/wiki/User:Ankursinha" class="reference external">@ankursinha</a>.The agenda for the meeting is:</p><ul class="simple"><li>New introductions and roll call.</li><li><a href="https://meetbot.fedoraproject.org/latest/neurofedora" class="reference external">Tasks from last meeting</a>.</li><li><a href="https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&amp;tags=S%3A+Next+meeting" class="reference external">Open Pagure tickets</a>.</li><li><a href="https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig" class="reference external">Package health check</a>.</li><li><a href="https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro" class="reference external">Open package reviews check</a>.</li><li><a href="https://koji.fedoraproject.org/koji/packageinfo?packageID=30691" class="reference external">CompNeuro lab compose status check for Fedora 40/rawhide</a>.</li><li>Neuroscience query of the week</li><li>Next meeting day, and chair.</li><li>Open floor.</li></ul><p>We hope to see you there!</p></content:encoded> <dc:date>2024-04-22T09:49:03+00:00</dc:date></item><item rdf:about="https://packit.dev/posts/weekly/2024/week-16"> <title>Weekly status of Packit Team: Week 16 in Packit</title> <link>https://packit.dev/posts/weekly/2024/week-16</link> <content:encoded><h2 class="anchor anchorWithStickyNavbar_LWe7" id="week-16-april-16th--april-22nd">Week 16 (April 16th – April 22nd)<a href="https://packit.dev/posts/weekly/rss.xml#week-16-april-16th--april-22nd" class="hash-link" title="Direct link to Week 16 (April 16th – April 22nd)"></a></h2><ul><li><code>packit dist-git init</code> now allows specifying <code>--version-update-mask</code> option and also any arbitrary top-level configuration options. (<a href="https://github.com/packit/packit/pull/2288" target="_blank" rel="noopener noreferrer">packit#2288</a>)</li><li>We have fixed Packit auto-referencing Upstream Release Monitoring bug for release syncing to CentOS Stream. (<a href="https://github.com/packit/packit/pull/2284" target="_blank" rel="noopener noreferrer">packit#2284</a>)</li><li>We have changed the behaviour of <code>/packit test</code> comment command: in case there is a missing build for some target, the build will not be triggered anymore, it will just be reported to the user. We needed to make this change as with the increased complexity of the configuration (multiple test jobs), the previous implementation was prone to race conditions leading to wasting of resources of Copr and Testing Farm. (<a href="https://github.com/packit/packit-service/pull/2399" target="_blank" rel="noopener noreferrer">packit-service#2399</a>)</li></ul></content:encoded> <dc:date>2024-04-22T00:00:00+00:00</dc:date></item><item rdf:about="http://opensourcesecurity.io/?p=3367"> <title>Josh Bressers: Episode 425 – Video game cheaters, also pretendo</title> <link>https://opensourcesecurity.io/2024/04/21/episode-425-video-game-cheaters-also-pretendo/</link> <content:encoded><p><a href="https://infosec.exchange/@joshbressers">Josh</a> and <a href="https://infosec.exchange/@kurtseifried">Kurt</a> talk about a database of game cheaters. Cheating in games has many similarities to security problems. Anti cheat rootkits are also terrible. The clever thing however is using statistics to identify cheaters. Statistics don’t lie. Also, we discuss the Pretendo project sitting on a vulnerability for a year, is this ethical?</p> &lt;audio class="wp-audio-shortcode" controls="controls" id="audio-3367-2" preload="none" style="width: 100%;"&gt;&lt;source src="https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_425_Video_game_cheaters_also_pretendo.mp3?_=2" type="audio/mpeg"&gt;<a href="https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_425_Video_game_cheaters_also_pretendo.mp3">https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_425_Video_game_cheaters_also_pretendo.mp3</a>&lt;/audio&gt; <h2 class="wp-block-heading">Show Notes</h2> <ul><li><a href="https://news.ycombinator.com/item?id=40017918">Hacker News searchable database</a></li> <li><a href="https://en.wikipedia.org/wiki/Benford%27s_law">Benford’s law</a></li> <li><a href="https://www.youtube.com/watch?v=bVIsnOfNfCo">John Oliver Medicaid</a></li> <li><a href="https://www.youtube.com/watch?v=YsXCVsDFiXA">Mario64 invisible walls</a></li> <li><a href="https://pretendo.network/">Pretendo</a></li> <li><a href="https://mastodon.pretendo.network/@pretendo/112238381209517548">Pretendo exploit</a></li></ul></content:encoded> <dc:date>2024-04-22T00:00:00+00:00</dc:date></item><item rdf:about="https://gnu.wildebeest.org/blog/mjw/?p=1203"> <title>Mark J. Wielaard: Valgrind 3.23.0-RC1</title> <link>https://gnu.wildebeest.org/blog/mjw/2024/04/21/valgrind-3-23-0-rc1/</link> <content:encoded><p><a href="https://sourceforge.net/p/valgrind/mailman/message/58762496/">Valgrind 3.23.0-RC1</a>. Please help test.</p><p>FreeBSD arm64 support. <tt>--track-fds=yes</tt> now warns against double close, generates (suppressible) errors and supports XML output. s390x supports more z16 instructions. More accurate x86_64-v3 instruction support. Wrappers for <tt>wcpncpy</tt>, <tt>memccpy</tt>, <tt>strlcat</tt> and <tt>strlcpy</tt>. Support Linux syscalls <tt>mlock2</tt>, <tt>fchmodat2</tt>, <tt>pidfd_getfd</tt>. And much more. 50+ bug fixes, 280+ commits by 14 developers since 3.22.0.</p><p>Fedora rawhide binary packages are <a href="https://bodhi.fedoraproject.org/updates/FEDORA-2024-a5e6dd3146">available</a> for aarch64, i686, ppc64le, s390x and s390x.</p></content:encoded> <dc:date>2024-04-21T15:15:34+00:00</dc:date></item><item rdf:about="https://www.jdieter.net/posts/2024/04/20/email-update/"> <title>Jonathan Dieter: Email update</title> <link>https://www.jdieter.net/posts/2024/04/20/email-update/</link> <content:encoded><br /> <a href="https://www.jdieter.net/posts/2024/04/20/email-update/stone_fort.jpg"> <img width="260" src="https://www.jdieter.net/posts/2024/04/20/email-update/stone_fort_hud86f4f8ef58e934d346b80f1d60cb358_2994248_0x200_resize_q75_box.jpg" height="200" /> </a> <p>This is just a quick update that I’m updating my primary email address. A year or so ago, I bought the domain <code>dieter.ie</code> (since I’m resident in Ireland, it seemed like a good choice), and it seemed time to put it to good use. My blog will continue to be hosted on <a href="https://www.jdieter.net">jdieter.net</a>, but my primary email address is now <a href="mailto:jonathan@dieter.ie">jonathan@dieter.ie</a>. My previous Gmail address will continue to work and I’m not giving it up any time soon.</p><p>I’m also very aware that it’s been a while since I last posted. The company I work for, Spearline, was acquired just over a year ago by <a href="https://cyara.com">Cyara</a>, and life has been unusually hectic over the last year. Hopefully I’ll have some time to post a bit more frequently in the near future. In the meantime, I’ve included a picture I took yesterday of an old ringfort nearby. West Cork is beautiful when the weather’s nice!</p></content:encoded> <dc:date>2024-04-20T21:36:17+00:00</dc:date></item><item rdf:about="https://blog.kulakowski.fr/?p=30360"> <title>Guillaume Kulakowski: OpenWRT: Ad Guard Home, anti-pub, DoH & Contrôle parental</title> <link>https://blog.kulakowski.fr/post/openwrt-ad-guard-home-anti-pub-doh-controle-parental</link> <content:encoded><p>Depuis plusieurs années, j’ai utilisé OpenWRT, mais je n’étais pas pleinement satisfait de ma solution de contrôle parental. C’était principalement à cause de l’utilisation des services d’OpenDNS, qui était nécessaire en raison de mes deux routeurs Redmi AC2100 ayant une capacité mémoire limitée (seulement 128 Mo). J’ai, depuis peu, fait l’achat d’un routeur Redmi AX6000 […]</p><p>Cet article <a href="https://blog.kulakowski.fr/post/openwrt-ad-guard-home-anti-pub-doh-controle-parental">OpenWRT: Ad Guard Home, anti-pub, DoH &amp; Contrôle parental</a> est apparu en premier sur <a href="https://blog.kulakowski.fr">Guillaume Kulakowski's blog</a>.</p></content:encoded> <dc:date>2024-04-19T11:50:00+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13567"> <title>Fedora Community Blog: Infra and RelEng Update – Week 16, 2024</title> <link>https://communityblog.fedoraproject.org/infra-and-releng-update-week-16-2024/</link> <content:encoded><p>This is a weekly report from the I&amp;R (<a href="https://docs.fedoraproject.org/en-US/infra/">Infrastructure &amp; Release Engineering</a>) Team. It also contains updates for the CPE (<a href="https://docs.fedoraproject.org/en-US/cpe/">Community Platform Engineering</a>) Team as the CPE initiatives are in most cases tied to I&amp;R work.</p> <p>We provide you both an infographic and a text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in-depth details look at the infographic.</p> <p>Week: 15 April – 19 April 2024</p> <span id="more-13567"></span> &lt;figure class="wp-block-image size-full"&gt;<img width="2447" alt="I&amp;R infographic" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/Weekly-Report-Template-23-scaled.jpg" class="wp-image-13568" height="2560" />&lt;/figure&gt; <h2 class="wp-block-heading">Infrastructure &amp; Release Engineering</h2> <p>The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.<br />It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces, etc.).<br /><a href="https://issues.redhat.com/issues/?filter=12428298">List of planned/in-progress issues</a></p> <h3 class="wp-block-heading">Fedora Infra</h3> <ul><li>In progress:<ul><li><a href="https://pagure.io/fedora-infrastructure/issue/11815">rhel7 EOL</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11543">Migration of registry.fedoraproject.org to quay.io</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11611">add monitoring for dnf countme</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11393">Replace Nagios with Zabbix in Fedora Infrastructure</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11687">notifications do not notify</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11714">DNF countme minor changes post migration</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11755">vmhost-x86-copr02 hardware issues</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11820">PDC retirement</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11715">Move from iptables to firewalld</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/10383">fedoraplanet.org: Upgrade Venus to Pluto</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/8455">Move mailman to newer release of Fedora or CentOS</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11726">Setup RISC-V builder(s) VM in Fedora Infrastructure</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11711">Update compose hosts to get latest pungi release (4.6.0)</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11505">Deploy new sign hardware/software</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11826">logrotate not working on proxy31</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11641">Commits don’t end up on the scm-commits list</a></li></ul></li> <li>Done:<ul><li>Migrated zabbix01 prod to vmhost: vmhost-x86-05</li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11838">AWS S3 bucket permissions for openQA cloud enablement</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11881">503 Service unavailable for koji.fp.o</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11877">Secrets storage: Blockerbugs stg/api key</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11878">please archive security and security-team mailing lists</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11876">My nfs-utils repo fork cannot be accessed</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11873">discourse2fedmsg.fedoraproject.org webhook failing again</a></li> <li><a href="https://mdapi.stg.fedoraproject.org/">HOTFIX deployed to STAGING</a> – <a href="https://pypi.org/project/mdapi/3.1.6a1/">MDAPI v3.1.6a1</a> on PyPI</li></ul></li></ul> <h3 class="wp-block-heading">CentOS Infra including CentOS CI</h3> <ul><li>In progress:<ul><li><a href="https://pagure.io/centos-infra/issue/1358">c8s/c7 EOL infrastructure planning</a></li> <li><a href="https://pagure.io/centos-infra/issue/1240">Convert our ansible hosts to RHEL and ansible-core new version</a></li></ul></li> <li>Done:<ul><li><a href="https://issues.redhat.com/browse/CS-2028">rebalance ppc64le kojid workload</a></li> <li><a href="https://pagure.io/centos-infra/issue/1391">decommission two sponsored machine, used for testing</a></li> <li><a href="https://pagure.io/centos-infra/issue/1392">Duffy seems to be inaccessible from CentOS CI OCP #3</a></li> <li><a href="https://pagure.io/centos-infra/issue/1395">New Build Targets and Tags for the Kmods SIG</a></li></ul></li></ul> <h3 class="wp-block-heading">Release Engineering</h3> <ul><li>In progress:<ul><li><a href="https://pagure.io/releng/issue/8601">Packages that fail to build SRPM are not reported during the mass rebuild bugzillas</a></li> <li><a href="https://pagure.io/releng/issue/11385">Silverblue aarch64 installer image compose always fails on F38 and Rawhide</a></li> <li><a href="https://pagure.io/releng/issue/11358">Sync RCs to alt/stg dl.fp.o</a></li> <li><a href="https://pagure.io/releng/issue/11531">i686 builders need to use 32-bit inode numbers</a></li> <li><a href="https://pagure.io/releng/issue/11673">Fixes for release-candidate.sh in pungi-fedora</a></li> <li><a href="https://pagure.io/releng/issue/8929">When orphaning packages, keep the original owner as co-maintainer</a></li> <li><a href="https://pagure.io/releng/issue/7337">Emit fedmsg when candidate composes are synced to stage</a></li> <li><a href="https://pagure.io/releng/issue/9880">Publish “latest” tag to quay.io/fedora/fedora</a></li> <li><a href="https://pagure.io/releng/issue/9153">Use an automated script to control checksums of compose images</a></li> <li><a href="https://pagure.io/releng/issue/9674">Create an ansible playbook to do the mass-branching</a></li> <li><a href="https://pagure.io/releng/issue/12028">Package retirements are broken in rawhide</a></li> <li><a href="https://pagure.io/releng/issue/11957">Implement checks on package retirements</a></li></ul></li> <li>Done:<ul><li><a href="https://pagure.io/releng/issue/12030">adjust torrent_hashes.py to non bittorrent world</a></li> <li><a href="https://pagure.io/releng/issue/12063">Repo request failed for rpms/golang-github-jackc-pgx5</a></li> <li><a href="https://pagure.io/releng/issue/12064">Incomplete dist-git repo creation due to toddler crash: rpms/rust-async_zip</a></li> <li><a href="https://pagure.io/releng/issue/12060">Create Fedora 40 Final candidates</a></li></ul></li></ul> <h2 class="wp-block-heading">CPE Initiatives</h2> <h3 class="wp-block-heading">EPEL</h3> <p><a href="https://docs.fedoraproject.org/en-US/epel/">Extra Packages for Enterprise Linux</a> (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux (SL) and Oracle Linux (OL).</p> <h2 class="wp-block-heading">Updates</h2> <ul><li>Texas Linux Fest (TXLF) was held from 12-13 April<ul><li>Carl gave talk on the state of EPEL</li> <li>Also manned the EPEL and Fedora booth</li></ul></li> <li>EPEL docs are being reworked to include onboarding processes<ul><li>Also including an overall cleanup, better UI/UX</li></ul></li></ul> <h3 class="wp-block-heading">Community Design</h3> <p>CPE has few members that are working as part of <a href="https://fedoraproject.org/wiki/Design">Community Design Team</a>. This team is working on anything related to design in Fedora Community.</p> <h2 class="wp-block-heading">Updates</h2> <ul><li><a href="https://gitlab.com/groups/fedora/design/-/epics/32">F40 Wallpaper</a></li> <li>BootC logo complete <a href="https://gitlab.com/fedora/design/community-design-team/issues/-/issues/158">#158</a></li> <li>Working with contributors for design assets for Fedora Week of Diversity and Fedora Mentor Summit</li></ul> <p>If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on <a href="https://matrix.to/#/#redhat-cpe:matrix.org">matrix</a>.</p><p>The post <a href="https://communityblog.fedoraproject.org/infra-and-releng-update-week-16-2024/">Infra and RelEng Update – Week 16, 2024</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-19T10:00:00+00:00</dc:date></item><item rdf:about="tag:blogger.com,1999:blog-6112936277054198647.post-6156149132305853287"> <title>Peter Hutterer: udev-hid-bpf: quickstart tooling to fix your HID devices with eBPF</title> <link>http://who-t.blogspot.com/2024/04/udev-hid-bpf-quickstart-tooling-to-fix.html</link> <content:encoded><p> For the last few months, Benjamin Tissoires and I have been working on and polishing a little tool called <a href="https://libevdev.pages.freedesktop.org/udev-hid-bpf/index.html">udev-hid-bpf</a> [1]. This is the scaffolding required quickly and easily write, test and eventually fix your HID input devices (mouse, keyboard, etc.) via a BPF program instead of a full-blown custom kernel driver or a semi-full-blown kernel patch. To understand how it works, you need to know two things: HID and BPF [2]. </p><h2>Why BPF for HID?</h2><p> HID is the Human Interface Device standard and the most common way input devices communicate with the host (HID over USB, HID over Bluetooth, etc.). It has two core components: the "report descriptor" and "reports", both of which are byte arrays. The report descriptor is a fixed burnt-in-ROM byte array that (in rather convoluted terms) tells us what we'll find in the reports. Things like "bits 16 through to 24 is the delta x coordinate" or "bit 5 is the binary button state for button 3 in degrees celcius". The reports themselves are sent at (usually) regular intervals and contain the data in the described format, as the devices perceives reality. If you're interested in more details, see <a href="https://who-t.blogspot.com/2018/12/understanding-hid-report-descriptors.html" target="_blank">Understanding HID report descriptors</a>.</p><p> BPF or more correctly eBPF is a Linux kernel technology to write programs in a subset of C, compile it and load it into the kernel. The magic thing here is that the kernel will <a href="https://docs.kernel.org/bpf/verifier.html">verify it</a>, so once loaded, the program is "safe". And because it's safe it can be run in kernel space which means it's fast. eBPF was originally written for network packet filters but as of kernel v6.3 and thanks to Benjamin, we have BPF in the HID subsystem. HID actually lends itself really well to BPF because, well, we have a byte array and to fix our devices we need to do complicated things like "toggle that bit to zero" or "swap those two values".</p><p> If we want to fix our devices we usually need to do one of two things: fix the report descriptor to enable/disable/change some of the values the device pretends to support. For example, we can say we support 5 buttons instead of the supposed 8. Or we need to fix the report by e.g. inverting the y value for the device. This can be done in a custom kernel driver but a HID BPF program is quite a lot more convenient.</p> <h2>HID-BPF programs</h2><p> For illustration purposes, here's the example program to flip the y coordinate. HID BPF programs are usually device specific, we need to know that the e.g. the y coordinate is 16 bits and sits in bytes 3 and 4 (little endian): </p><pre>SEC("fmod_ret/hid_bpf_device_event")int BPF_PROG(hid_y_event, struct hid_bpf_ctx *hctx){ s16 y; __u8 *data = hid_bpf_get_data(hctx, 0 /* offset */, 9 /* size */); if (!data) return 0; /* EPERM check */ y = data[3] | (data[4] &lt;&lt; 8); y = -y; data[3] = y &amp; 0xFF; data[4] = (y &gt;&gt; 8) &amp; 0xFF; return 0;} </pre>That's it. HID-BPF is invoked before the kernel handles the HID report/report descriptor so to the kernel the modified report looks as if it came from the device.<p></p><p> As said above, this is device specific because where the coordinates is in the report depends on the device (the report descriptor will tell us). In this example we want to ensure the BPF program is only loaded for our device (vid/pid of 04d9/a09f), and for extra safety we also double-check that the report descriptor matches.</p><pre>// The bpf.o will only be loaded for devices in this listHID_BPF_CONFIG( HID_DEVICE(BUS_USB, HID_GROUP_GENERIC, 0x04D9, 0xA09F)); SEC("syscall")int probe(struct hid_bpf_probe_args *ctx){ /* * The device exports 3 interfaces. * The mouse interface has a report descriptor of length 71. * So if report descriptor size is not 71, mark as -EINVAL */ ctx-&gt;retval = ctx-&gt;rdesc_size != 71; if (ctx-&gt;retval) ctx-&gt;retval = -EINVAL; return 0;}</pre>Obviously the check in probe() can be as complicated as you want.<p></p><p> This is pretty much it, the <a href="https://gitlab.freedesktop.org/libevdev/udev-hid-bpf/-/blob/main/src/bpf/userhacks/10-mouse_invert_y.bpf.c?ref_type=heads">full working program</a> only has a few extra includes and boilerplate. So it mostly comes down to compiling and running it, and this is where udev-hid-bpf comes in.</p> <h2>udev-hid-bpf as loader</h2><p> udev-hid-bpf is a tool to make the <i>development and testing</i> of HID BPF programs simple, and collect HID BPF programs. You basically run <i>meson compile</i> and <i>meson install</i> and voila, whatever BPF program applies to your devices will be auto-loaded next time you plug those in. If you just want to test a single bpf.o file you can <i>udev-hid-bpf install /path/to/foo.bpf.o</i> and it will install the required udev rule for it to get loaded whenever the device is plugged in. If you don't know how to compile, you can grab a tarball from our CI and test the pre-compiled bpf.o. Hooray, even simpler.</p><p> udev-hid-bpf is written in Rust but you don't need to know Rust, it's just the scaffolding. The BPF programs are all in C. Rust just gives us a relatively easy way to provide a static binary that will work on most tester's machines.</p><p> The documentation for udev-hid-bpf is <a href="https://libevdev.pages.freedesktop.org/udev-hid-bpf/">here</a>. So if you have a device that needs a hardware quirk or just has an annoying behaviour that you always wanted to fix, well, now's the time. Fixing your device has never been easier! [3].</p><p> <small> [1] Yes, the name is meh but you're welcome to come up with a better one and go back in time to suggest it a few months ago. <br /> [2] Because I'm lazy the terms eBPF and BPF will be used interchangeably in this article. Because the difference doesn't really matter in this context, it's all eBPF anyway but nobody has the time to type that extra "e".<br /> [3] Citation needed </small></p></content:encoded> <dc:date>2024-04-18T04:17:38+00:00</dc:date></item><item rdf:about="https://major.io/p/fedora-cloud-init-dhcpcd/"> <title>Major Hayden: cloud-init and dhcpcd</title> <link>https://major.io/p/fedora-cloud-init-dhcpcd/</link> <content:encoded>Fedora’s cloud-init package now uses dhcpcd in place of dhclient, which went end of life in 2022. 💀</content:encoded> <dc:date>2024-04-18T00:00:00+00:00</dc:date></item><item rdf:about="https://blog.kulakowski.fr/?p=15135"> <title>Guillaume Kulakowski: OpenWRT derrière une Freebox: IPv6, DMZ et Bridge</title> <link>https://blog.kulakowski.fr/post/openwrt-derriere-une-freebox-ipv6-dmz-et-bridge</link> <content:encoded><p>Article mise à jour le 17/04/2024 pour tenir compte des spécificités d’OpenWRT 23.05. Bien que je sois le très récent et heureux possesseur d’une Freebox Pop, j’ai fait le choix de continuer à déléguer la gestion de mon réseau ainsi que de mon partage Wi-Fi, non pas à la Pop, mais à OpenWRT. Les avantages […]</p><p>Cet article <a href="https://blog.kulakowski.fr/post/openwrt-derriere-une-freebox-ipv6-dmz-et-bridge">OpenWRT derrière une Freebox: IPv6, DMZ et Bridge</a> est apparu en premier sur <a href="https://blog.kulakowski.fr">Guillaume Kulakowski's blog</a>.</p></content:encoded> <dc:date>2024-04-17T18:10:00+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=40137"> <title>Fedora Magazine: Fedora Chat: Your Gateway to Matrix</title> <link>https://fedoramagazine.org/fedora-chat-your-gateway-to-matrix/</link> <content:encoded><h2 class="wp-block-heading"><strong>What is Matrix?</strong></h2> <p><a href="https://matrix.org/" target="_blank" rel="noreferrer noopener">Matrix</a> is an open protocol for decentralized, secure communications built on the principles of interoperability and decentralization. You can create an account on a home server and then join channels across different home servers. This means if you have an account through Matrix.org, you can use it to join our community spaces! One of those is Fedora Chat.</p> <span id="more-40137"></span> <p><a href="https://matrix.org/about/" target="_blank" rel="noreferrer noopener">The Matrix Foundation</a> acts as the guardian of the Matrix protocol, ensuring it remains a free and open standard for secure, decentralized communication. It’s responsible for developing and maintaining the <a href="https://spec.matrix.org/latest/" target="_blank" rel="noreferrer noopener">Matrix Specification</a> along with working closely with the community to enhance interoperability and innovation.</p> <h2 class="wp-block-heading"><strong>What is Fedora Chat?</strong></h2> <p>Fedora Chat is what we call our Matrix homeserver instance. It is a set of two homeservers, one for our community rooms as fedoraproject.org as well as the fedora.im homeserver which provides accounts for our users to join the fedoraproject.org rooms. Both of these are hosted by Element Matrix Services (“EMS”) thanks to our sponsorship from Red Hat.</p> <p>You can use your fedora.im account to join other Matrix homeservers as well and collaborate with other communities, including <a href="https://wiki.gnome.org/GettingInTouch/Matrix" target="_blank" rel="noreferrer noopener">Gnome</a>, <a href="https://wiki.mozilla.org/Matrix" target="_blank" rel="noreferrer noopener">Mozilla</a>, and <a href="https://ubuntu.com/community/communications/matrix" target="_blank" rel="noreferrer noopener">Ubuntu</a>!</p> <h3 class="wp-block-heading"><strong>Getting Started on Fedora Chat</strong></h3> <p>Ready to jump into Fedora Chat? If you do not have a Matrix account already, you can use the fedora.im homeserver to get an account and join our community space! If you already have Matrix – <a href="https://matrix.to/#/#fedora-space:fedoraproject.org" target="_blank" rel="noreferrer noopener">you can join our Fedora space through this link</a>.</p> <ol><li>Visit<a href="https://chat.fedoraproject.org" target="_blank" rel="noreferrer noopener"> https://chat.fedoraproject.org</a> and click the blue “Sign in” and then “Continue with your Fedora Account” to login with your FAS account. </li> <li>You should be added to our Space automatically which is a collection of rooms, but if not, join the room here <a href="https://matrix.to/#/#fedora-space:fedoraproject.org" target="_blank" rel="noreferrer noopener">#fedora-space:fedoraproject.org</a></li> <li>You can then choose different rooms in the menu in which to say hello. Find a room and then say hello!</li></ol> <h2 class="wp-block-heading"><strong>Exploring Other Matrix Clients</strong></h2> <p>While Fedora Chat uses the hosted Element client, the Matrix universe is vast. Explore other clients that suit your needs, from desktop apps to mobile solutions. Each offers unique features, allowing you to tailor your experience. You can find an updated list of <a href="https://matrix.org/ecosystem/clients/" target="_blank" rel="noreferrer noopener">different clients on the Matrix.org website</a>.</p> <h2 class="wp-block-heading"><strong>Understanding Encryption, Keys, and Device Verification</strong></h2> <p>Matrix’s end-to-end encryption ensures that only the communicating users in a room can read messages. Some rooms are end-to-end encrypted, but most public rooms are not. Most rooms in Fedora community spaces are not end-to-end encrypted, and you can see the history. However, if you directly message another user or join an E2E room, your messages will be encrypted by default. This is achieved through the management of cryptographic keys that secure each conversation. The encryption process involves generating unique keys your client stores on your behalf.</p> <p>Protecting your encryption keys is essential, and your Recovery Key is critical to keep. The Recovery Key allows you to restore access to your encrypted conversations if you lose access to your primary key backup. Keep your Recovery Key in a safe location.</p> <p>Session verification further enhances security by allowing users to verify their identity across multiple devices, ensuring that verified devices can only read encrypted messages.</p> <p><a href="https://element.io/help#encryption" target="_blank" rel="noreferrer noopener">Element provides a great FAQ on how to create and manage your key backups</a>, but this will vary based on the client you choose to use. If you use chat.fedoraproject.org, it is a great resource.</p> <h2 class="wp-block-heading"><strong>What’s Next</strong></h2> <p>Join <a href="https://matrix.to/#/#fedora-space:fedoraproject.org" target="_blank" rel="noreferrer noopener">#fedora-space:fedoraproject.org</a> and say hello in <a href="https://matrix.to/#/#intros:fedoraproject.org" target="_blank" rel="noreferrer noopener">#intros:fedoraproject.org</a> – and welcome to the Matrix-verse!</p></content:encoded> <dc:date>2024-04-17T08:00:00+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13271"> <title>Fedora Community Blog: Fedora @ SCaLE 21x 2024</title> <link>https://communityblog.fedoraproject.org/scale-21x-2024/</link> <content:encoded><p>Our ambassadors delivered support, outreach, and swag items via Fedora @ SCaLE 21x Linux Conference – a 2024 community event.</p> &lt;figure class="wp-block-image size-full"&gt;<img width="499" alt="Life-size entrance gateway to SCaLE 21x. Shows expo hours and various sponsors" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240314_231613208-1-edited.jpg" class="wp-image-13555" height="333" />&lt;figcaption class="wp-element-caption"&gt;Portal to Linux wonder: SCaLE 21x.&lt;/figcaption&gt;&lt;/figure&gt; <h2 class="wp-block-heading">At a Glance</h2> <ul><li>What: A community-run open-source and free software conference in Pasadena, California</li> <li>Where: Pasadena Convention Center</li> <li>When: 14 – 17 March 2024</li></ul> <span id="more-13271"></span> &lt;figure class="wp-block-image size-large is-resized"&gt;<img src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240314_180114770-1-1024x771.jpg" style="width: 594px; height: auto;" height="771" width="1024" alt="The front of the main building of the Pasadena Convention Center with a large banner for SCaLE. Photo by Carl George." class="wp-image-13510" />&lt;figcaption class="wp-element-caption"&gt;Where SCaLE begins…The front of the main building of the Pasadena Convention Center. <br />Photo by Carl George.&lt;/figcaption&gt;&lt;/figure&gt; <h2 class="wp-block-heading">Our Team in the Field</h2> <p>This reports the activities of the following Ambassadors / Red Hatters at the Fedora @ SCaLE 21x Linux Conference:</p> <ul><li>Alejandro “Alex” Acosta (FAS: <a href="https://fedoraproject.org/wiki/User:Aacosta" target="_blank" rel="noreferrer noopener">aacosta</a>)</li> <li>Brian Monroe (FAS: <a href="https://fedoraproject.org/wiki/User:Paradoxguitarist" target="_blank" rel="noreferrer noopener">paradoxguitarist</a>)</li> <li>Scott Williams (FAS: <a href="https://fedoraproject.org/wiki/User:Vwbusguy" target="_blank" rel="noreferrer noopener">vwbusguy</a>)</li> <li>Perry Rivera (FAS: <a href="https://fedoraproject.org/wiki/User:Lajuggler" target="_blank" rel="noreferrer noopener">lajuggler</a>)</li> <li>Matthew Miller (FAS: <a href="https://fedoraproject.org/wiki/User:Mattdm">mattdm</a>)</li> <li>Brian Proffitt (FAS: <a href="https://fedoraproject.org/wiki/User:Bproffit">Bproffit</a>)</li> <li>Justin W. Flory (FAS: <a href="https://fedoraproject.org/wiki/User:Jflory7" target="_blank" rel="noreferrer noopener">Jflory7</a>) [remote support]</li></ul> <h2 class="wp-block-heading">What is SCaLE 21x?</h2> <p>The SCaLE (The Southern California Linux Expo) community Linux event delivered an iconic experience with four days of open source training, exhibits, and general presentations. This year’s conference took place in Pasadena (Los Angeles) area.</p> <p>This expo drew worldwide guests to discuss AI, Linux, security, embedded, IoT, and more. The Conference Chair, Mr. Ilan Rabinovitch, and Technical Committee Chairperson, Owen Delong paved the way for a smooth registration.</p> &lt;figure class="wp-block-image size-large is-resized"&gt;<img src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240317_220310621-1-576x1024.jpg" style="width: 343px; height: auto;" height="1024" width="576" alt="Ilan Rabinovitch onstage introducing a keynote" class="wp-image-13465" />&lt;figcaption class="wp-element-caption"&gt;Ilan Rabinovitch&lt;/figcaption&gt;&lt;/figure&gt; <h2 class="wp-block-heading">Conference Highlights</h2> <h3 class="wp-block-heading">Fedora @ SCaLE 21x Linux Conference – Ready, Set, Go!</h3> <p>Justin Flory arranged and shipped hand-selected swag and marketing items to Brian Monroe. Items include: pens, stickers, commuter mugs, badge ribbons, badge lanyards, and more.</p> <p>Furthermore, the ambassadors gathered up supplies for the conference. </p> <h3 class="wp-block-heading">Day 1: Thursday 14 March</h3> <p>Red Hatter Brian Proffitt carefully delivered our marketing notebook system. </p> <p>In addition, Perry brought the following:</p> <ul><li>Dry-board markers</li> <li>Dry-board flipchart easel</li> <li>Opportunity drawing tickets</li> <li>Leftover ribbons, mini-swag from 19x event</li> <li>Safety scissors</li> <li>Gaffers tape</li> <li>Glue</li> <li>And more!</li></ul> <p>Some of our ambassadors travelled in the morning, to catch earlier events and workshops. Others, however, arrived later to factor in traffic. </p> <div class="wp-block-jetpack-slideshow aligncenter"><div class="wp-block-jetpack-slideshow_container swiper-container"><ul class="wp-block-jetpack-slideshow_swiper-wrapper swiper-wrapper"><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240314_231826444-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13466" height="1440" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Portal to New Linux Ideas&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="picture of the back of the Fedora booth-a sheet wall" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240317_202658909-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13398" height="1440" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;The back of the Fedora booth this year…a sheet wall..&lt;/figcaption&gt;&lt;/figure&gt;</li></ul><a class="wp-block-jetpack-slideshow_button-prev swiper-button-prev swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-next swiper-button-next swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-pause"></a><div class="wp-block-jetpack-slideshow_pagination swiper-pagination swiper-pagination-white"></div></div></div> <p>We met in the exhibit hall to check out the booth and to discuss strategy. Henceforth, we thought about our discussions and engagement to attract visitors. In contrast to <a href="https://communityblog.fedoraproject.org/fedora-at-scale-20x-community-linux-event/">SCaLE 20x</a>, our booth was some distance away from the Red Hat booth. </p> <p>The booth did not receive any free-standing banners this year. Thus, aside from our table cover, swag, and flip chart, we had few items to work with which had large Fedora branding. Soon, we discovered that some guests had initial challenges trouble locating our booth.</p> <p>Upon dropping things off, some of us reconvened at the <a href="https://www.kwaai.ai/summit">KWAAI Summit</a>, new for 2024. Matt Small, Reza Rassool, Román Pineda, Khai Pham, John Willis, and others closed out the the event with an engaging Q&amp;A, introductions, wrap up, and reception, for example.</p> <p>Afterwards, Fedora joined the Red Hat and CentOS teams and others for a meal at the Yard House.</p> &lt;figure class="wp-block-image size-large is-resized"&gt;<img src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240315_043657597-1-1024x576.jpg" style="width: 584px; height: auto;" height="576" width="1024" alt="Matt Miller, Shaun McCance, Perry Rivera, and Carl George around a table at Yard House Pasadena" class="wp-image-13399" />&lt;figcaption class="wp-element-caption"&gt;From L to R: Matthew Miller, Shaun McCance, Perry Rivera, and Carl George&lt;/figcaption&gt;&lt;/figure&gt; <h3 class="wp-block-heading">Day 2: Friday 15 March</h3> <h4 class="wp-block-heading">Checking in on the other variants…</h4> <p>Alejandro and I set out for breakfast Friday and discussed booth and expo plans for the days ahead. Eventually, we headed off to the NixCon track co-located in SCaLE 21x to learn about Nix. We were surprised to find a very packed workshop.</p> <h4 class="wp-block-heading">Booth Setup</h4> <p>After a brief look into these OSes, we returned to the Expo Hall to begin putting our booth together. For example, Scott arrived to install a notebook system that he configured with Flatpak pinball game running atop Universal Blue.</p> <div class="wp-block-jetpack-slideshow aligncenter"><div class="wp-block-jetpack-slideshow_container swiper-container"><ul class="wp-block-jetpack-slideshow_swiper-wrapper swiper-wrapper"><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1440" alt="" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_000820663-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13413" height="2560" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;A guest re-discovers pinball on an immutable desktop&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_000755170-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13415" height="1440" />&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1920" alt="Red Hatters setting up a booth" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240315_171856128-1.jpg" class="wp-block-jetpack-slideshow_image wp-image-13400" height="1080" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Red Hatters setting up a booth&lt;/figcaption&gt;&lt;/figure&gt;</li></ul><a class="wp-block-jetpack-slideshow_button-prev swiper-button-prev swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-next swiper-button-next swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-pause"></a><div class="wp-block-jetpack-slideshow_pagination swiper-pagination swiper-pagination-white"></div></div></div> <p>Next, Perry set up a Fedora flip chart and pasted in a handy QR that Alejandro generated for guests to claim a <a href="https://badges.fedoraproject.org/badge/scale-21x-attendee">Fedora badge</a>. Then, Alejandro later wrote in our Fedora scheduled talks, which was handy for guests to take pictures of as they stopped by. Concurrently, Brian strategically set up swag items and carefully routed power within the booth.</p> <p>Perry later stopped by the Red Hat booth to help raise the 5-person banner. It’s not heavy, however, but it is awkward and difficult to stand up with fewer than 5-people in attendance.</p> <h4 class="wp-block-heading">What an Exhibit at Fedora @ SCaLE 21x Linux Conference</h4> <p>At 10am, the Exhibit Hall opened. As a result, we had a steady stream of community throughout the reminder of the conference. Then, we took turns for breaks from time to time; however, as we were down a person, things felt a bit busier this year. We definitely missed not having <a href="https://fedoraproject.org/wiki/User:Ichavero">Iván Chavero</a> there. </p> <p>We greeted approximately 400+ this day.</p> <p>One of the many highlights from today was discovering a vending machine that dispenses temporary VMs. The buttons were quite amusing.</p> &lt;figure class="wp-block-gallery has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex"&gt;&lt;figure class="wp-block-image size-full"&gt;<img width="1440" alt="picture of a vending machine with googly eyes" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_002855389-1-scaled.jpg" class="wp-image-13416" height="2560" />&lt;figcaption class="wp-element-caption"&gt;Eye-deal VM Vending Re-use.&lt;/figcaption&gt;&lt;/figure&gt; &lt;figure class="wp-block-image size-full"&gt;<img width="1440" alt="zoomed in picture of vending machine buttons" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_002919644-1-scaled.jpg" class="wp-image-13417" height="2560" />&lt;/figure&gt;&lt;/figure&gt; <p>At length, a few of us met up with Red Hat, CentOS, at El Portal Restaurant for dinner. </p> <div class="wp-block-jetpack-slideshow aligncenter"><div class="wp-block-jetpack-slideshow_container swiper-container"><ul class="wp-block-jetpack-slideshow_swiper-wrapper swiper-wrapper"><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="picture of food from El Portal restaurant" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_032134710-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13401" height="1440" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;El Portal Restaurant for dinner.&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="548" alt="Rob McBryde singing karaoke" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_051744257-ANIMATION.gif" class="wp-block-jetpack-slideshow_image wp-image-13402" height="972" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Rob McBryde: Coordinator of Karaoke goodness.&lt;/figcaption&gt;&lt;/figure&gt;</li></ul><a class="wp-block-jetpack-slideshow_button-prev swiper-button-prev swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-next swiper-button-next swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-pause"></a><div class="wp-block-jetpack-slideshow_pagination swiper-pagination swiper-pagination-white"></div></div></div> <p>Subsequently, we met up with Red Hat and CentOS later at Barney’s Beanery to enjoy karaoke and merriment.</p> <h3 class="wp-block-heading">Day 3: Saturday 16 March</h3> <p>Specifically, Brian Monroe, Scott, and Perry met up early Saturday morning to go over slide logistics for our <a href="https://www.socallinuxexpo.org/scale/21x/presentations/exploring-immutable-linux-desktops-fedora" target="_blank" rel="noreferrer noopener">Exploring Immutable Linux Desktops with Fedora</a> presentation later that day. Afterward, we caught up with Alejandro at the booth to continue engaging with guests and greeted approximately 500+ this day.</p> <p>Perry dropped in on a Digital Art / Krita open-source application workshop that went over how the fundamentals of using this tool. They gave pointers on how they use the app in their workflow, for instance.</p> <div class="wp-block-jetpack-slideshow aligncenter"><div class="wp-block-jetpack-slideshow_container swiper-container"><ul class="wp-block-jetpack-slideshow_swiper-wrapper swiper-wrapper"><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="Nicholas Maramba and Helen Ortiz presenting" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_181656861-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13408" height="1440" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Nicholas Maramba and Helen Ortiz present “Digital Art Makes You Smart”&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1440" alt="Lucky winner holding up a Fedora commuter tumbler" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_230204548-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13369" height="2560" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Humberto Macias, lucky winner of a Fedora commuter tumbler.&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1225" alt="sign to a reproducible and immutable desktop presentation" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_2113175172-1.jpg" class="wp-block-jetpack-slideshow_image wp-image-13403" height="2050" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Portal to the endless wonder of immutable desktops..&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="guests engaging in an Immutable Desktop presentation" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240316_214744681-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13404" height="1440" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Guests listened attentively at the Immutable Desktop presentation&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="Scott Williams chats with Joshua Loscar at the Red Hat Booth" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240317_185643698-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13418" height="1440" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Scott Williams chats with Joshua Loscar at the Red Hat Booth&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="Jeff Carlson playing solitaire" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240317_061138779-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13406" height="1440" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Jeff Carlson ponders his next move..&lt;/figcaption&gt;&lt;/figure&gt;</li></ul><a class="wp-block-jetpack-slideshow_button-prev swiper-button-prev swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-next swiper-button-next swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-pause"></a><div class="wp-block-jetpack-slideshow_pagination swiper-pagination swiper-pagination-white"></div></div></div> <p>We also held opportunity drawings throughout the week to beckon more booth interest. Indeed, this proved a success. 40+ people stopped by for each draw. </p> <p>Comparatively, Perry, Brian Monroe, and Scott later delivered their presentation to 45+ guests.</p> <p>Thereafter, we re-joined Alejandro to finish up meeting our community at the booth for the expo day. We ate a late linner at the Dog Haus to reflect on the week’s events.</p> <p>Soon, SCaLE 21x held their annual game night event. Next, we reunited with friends and associates to catch up and enjoy.</p> <h3 class="wp-block-heading">Day 4: Sunday 17 March</h3> <p>All of us packed up our rooms early Sunday. Naturally, Alejandro and I re-joined up at the Cordova Cafe for breakfast. </p> <p>Consequently, we made our way over to the Exhibit Hall to finish up a final day with guests. Altogether, we had a little breather to visit the CentOS booth and say hello.</p> &lt;figure class="wp-block-image size-large is-resized"&gt;<img src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240317_194121257-1-1024x576.jpg" style="width: 602px; height: auto;" height="576" width="1024" alt="Shaun McCance and Carl George exhibiting at the CentOS booth" class="wp-image-13411" />&lt;figcaption class="wp-element-caption"&gt;Shaun McCance and Carl George exhibiting at the CentOS booth&lt;/figcaption&gt;&lt;/figure&gt; <p>The final exhibit day brought in about 250 guests to our booth. Following, our team packed up the booth for transport.</p> <p>Ultimately, to complete a fine Sunday, we attentively listened to an excellent closing <a href="https://www.youtube.com/watch?v=V_sqiff41gs" target="_blank" rel="noreferrer noopener">keynote</a> provided by Bill Cheswick.</p> <h4 class="wp-block-heading">Suggestion / Feedback Box Items for Fedora @ SCaLE 21x Linux Conference</h4> <p>In addition, we had a booth sign-in sheet for visitors to help collect feedback and suggestions about Fedora and related efforts.</p> <p>From data compiled, we summarize these key highlights:</p> <ul><li><strong>Marketing</strong>: Many requests for Fedora new logo swag and shirts. Could use stuffed animals, socks, or something different, USB stick. More creative ideas, sticker ideas (hex are popular), floor banners with new logo, DEI stickers were very popular. Portable swag (small and travel-ready) is great for travelers.</li> <li><strong>Marketing</strong>: One guest suggested a Fedora merch store where community could purchase Fedora logo swag/stickets/items. Above all, proceeds ideally would funnel back to Fedora community where needed.</li> <li><strong>Cross</strong>: One Debian guest continues prefers Debian for consistency, but wouldn’t mind using Fedora if a consistent spin was available. Potentially opportunity for immutable education or Debian/Ubuntu/NixOS etc. to Fedora presentations.</li> <li><strong>Info</strong>: Another Debian guest wanted to know key differences between Debian and Fedora. Ultimately, potential opportunity for explainer or migrating presentation or Why Use Fedora vs. ________?</li> <li><strong>Usage</strong>: One mentioned they are a Rawhide user.</li> <li><strong>Info</strong>: One requested more <a href="https://docs.fedoraproject.org/en-US/neurofedora/overview/#_join_us">information</a> about NeuroFedora. In other words, clearer information about what it is and the status of that Special Interest Group (SIG). Explainer card might be helpful at the booth.</li> <li><strong>Usage</strong>: One guest enjoys QT packages with DX build.</li> <li><strong>Licensing/Booth Info</strong>: One guest wanted clearer definition of the licensing relationship and sponsorship between Fedora / RHEL, if any.</li> <li><strong>Fedora Activity Day</strong>: It might be advantageous for Fedora to identify an organizer for a Fedora Activity Day (or two). For example, possible topics include: Debian to Fedora, command-line, Gnome, KDE, Immutable, Ambassadoring, Why Use Fedora vs. X?, etc.</li> <li><strong>Other</strong>: Changes for CentOS and Red Hat were points of concern and confusion for some guests.</li> <li><strong>Comm</strong>: Connect with Universal Blue folks, Lutris, Nobaro (sp?). Bazzite quality badges</li> <li><strong>Booth</strong>: Engagement with community at the table, opportunity drawing seems to be a success. Let’s get people in the front door of Fedora…for SCaLE 22x, provide challenge or engaging gimmick.</li></ul> &lt;figure class="wp-block-image size-large is-resized"&gt;<img src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240316_204224198-1-1024x576.jpg" style="width: 565px; height: auto;" height="576" width="1024" alt="Brian Monroe chats with a guest" class="wp-image-13463" />&lt;figcaption class="wp-element-caption"&gt;Brian Monroe chats with a guest&lt;/figcaption&gt;&lt;/figure&gt; <h4 class="wp-block-heading">Fedora 39 specific suggestions/comments:</h4> <ul><li><strong>Usage</strong>: Runs great on Dell Lat 7390</li> <li><strong>Usage</strong>: It’s awesome</li> <li><strong>Usage</strong>: (I) want to try it!</li> <li><strong>Marketing/Immutable/Porting</strong>: Cool retro (pinball) demo [at SCaLE 21x]</li> <li><strong>Thank You/Derivative</strong>: <a href="https://ultramarine-linux.org/">Ultramarine</a> user says thank you for Fedora.</li> <li><strong>Thank You/Support</strong>: Thank you for Data Transit (GTFS) support</li> <li><a href="https://www.reddit.com/r/Fedora/comments/z5souk/magicwormhole/">Magic Wormhol</a><a href="https://github.com/magic-wormhole">e</a> and Fedora are great. Ultimately, we referred this guest to Matthew Miller.</li> <li>One guest tracking 39 and 40 Beta packaging and kernel. Definitely, this visitor expressed interest in helping with general or immutable. Additionally, we referred this guest.</li></ul> <p>In conclusion, we look forward to seeing you at next year’s SCaLE!</p> <h2 class="wp-block-heading">Snaps from Fedora @ SCaLE 21x Linux Conference</h2> <div class="wp-block-jetpack-slideshow aligncenter"><div class="wp-block-jetpack-slideshow_container swiper-container"><ul class="wp-block-jetpack-slideshow_swiper-wrapper swiper-wrapper"><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1920" alt="picture of Perry Rivera and Kevin Howell. Kevin gives a thumbs up." src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240317_180630739-1.jpg" class="wp-block-jetpack-slideshow_image wp-image-13409" height="1080" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Perry Rivera and Kevin Howell&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="top-down view of the first floor of the Pasadena Conference Center from the second floor balcony. a picture of 40+ people chatting and/or working on laptops" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240314_180335378-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13508" height="1928" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Conference Center Conversation Flows. Photo by Carl George&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1920" alt="Patrick Finie and Perry Rivera" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240317_190831500-1.jpg" class="wp-block-jetpack-slideshow_image wp-image-13410" height="1080" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Patrick Finie and Perry Rivera&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="Photo of Neil Gompa, Shaun McCance at the podium presenting a kernels talk. Photo taken by Carl George." src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240314_213816223-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13509" height="1928" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;An engaging kernels workshop by Neil Gompa, Shaun McCance, and Carl George. Photo by Carl George.&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1920" alt="Ana Ma and Perry Rivera" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240315_235359129-1.jpg" class="wp-block-jetpack-slideshow_image wp-image-13420" height="1080" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Ana Ma and Perry Rivera&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1440" alt="Romy Meyerson SuSe stops by to visit to say hello" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/PXL_20240317_201053541-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13412" height="2560" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Romy Meyerson@SuSe stops by to visit to say hello..&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="Rob McBryde, Jaime Burwood, Katherine Nnanwubar, Perry Rivera, and Brian Proffitt" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/IMG_2151-1-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13446" height="1920" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Rob McBryde, Jaime Burwood, Katherine Nnanwubar, Perry Rivera, and Brian Proffitt&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1920" alt="Perry Rivera and Siggy" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240316_190900134-1.jpg" class="wp-block-jetpack-slideshow_image wp-image-13467" height="1080" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Perry Rivera and Siggy&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1920" alt="Perry Rivera and Marc Provitt" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240317_064024465-1.jpg" class="wp-block-jetpack-slideshow_image wp-image-13468" height="1080" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Perry Rivera and Marc Provitt from SCaLE 21x’s Game Night event.&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="At a round table: Scott Williams, Brian Monroe, Shaun McCance, and Carl George with notebook systems." src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/PXL_20240314_184928529-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13511" height="1920" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Discussing SCaLE strategies. L to R: Scott Williams, Brian Monroe, Shaun McCance, and Carl George.&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="1260" alt="Perry Rivera and Bill Cheswick" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/03/received_678173191004005.jpeg" class="wp-block-jetpack-slideshow_image wp-image-13439" height="994" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Perry Rivera and Bill Cheswick&lt;/figcaption&gt;&lt;/figure&gt;</li><li class="wp-block-jetpack-slideshow_slide swiper-slide">&lt;figure&gt;<img width="2560" alt="Fedora and Red Hatters having dim sum around table" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/img_5868-1-scaled.jpg" class="wp-block-jetpack-slideshow_image wp-image-13464" height="1920" />&lt;figcaption class="wp-block-jetpack-slideshow_caption gallery-caption"&gt;Clockwise, L to R: Joshua Loscar, Shaun McCance, Brian Proffitt, Cali Dolfi, Perry Rivera, Alex Acosta, Carl George, and Joshua’s oldest son discussing SCaLE week highlights at Lunasia Dim Sum House…&lt;/figcaption&gt;&lt;/figure&gt;</li></ul><a class="wp-block-jetpack-slideshow_button-prev swiper-button-prev swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-next swiper-button-next swiper-button-white"></a><a class="wp-block-jetpack-slideshow_button-pause"></a><div class="wp-block-jetpack-slideshow_pagination swiper-pagination swiper-pagination-white"></div></div></div> <h2 class="wp-block-heading">Related Posts</h2> <ul><li>Bill Cheswick – <a href="https://www.youtube.com/watch?v=V_sqiff41gs">Keynote at SCaLE</a>, <a href="https://www.cheswick.com/ches/">Bill’s Homepage</a>, <a href="https://en.wikipedia.org/wiki/William_Cheswick">Wikipedia Page</a></li> <li>UpSCaLE – <a href="https://www.socallinuxexpo.org/scale/21x/presentations/upscale">SCaLE 21x lightning talks</a></li></ul><p>The post <a href="https://communityblog.fedoraproject.org/scale-21x-2024/">Fedora @ SCaLE 21x 2024</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-16T12:28:48+00:00</dc:date></item><item rdf:about="https://peter.czanik.hu/other/sudo-logging-pretty-json_compact/"> <title>Peter Czanik: When it comes to sudo logging, pretty is not always better</title> <link>https://peter.czanik.hu/other/sudo-logging-pretty-json_compact/</link> <content:encoded><p>Version 1.9.16 of sudo will introduce a new logging option: json_compact. This does not affect logging to syslog, only logging to files. Previously, sudo created human-readable JSON log files. With this new setting enabled, logs are no longer pretty but can be easily read by logging software.</p><p>As I am writing this blog, version 1.9.16 is not yet released, not even a beta. For now, if you want to test this feature, you will have to compile sudo yourself from source. Once 1.9.16 is released, it will be available here on the sudo website as ready to install package for major Linux and UNIX variants. And eventually it will officially become available in various operating systems, FreeBSD and rolling Linux distros first.</p><p>Read more at <a href="https://www.sudo.ws/posts/2024/04/when-it-comes-to-sudo-logging-pretty-is-not-always-better/">https://www.sudo.ws/posts/2024/04/when-it-comes-to-sudo-logging-pretty-is-not-always-better/</a></p>&lt;figure&gt;<img src="https://peter.czanik.hu/images/sudo-logo1.png" />&lt;figcaption&gt; <h4>Sudo logo</h4> &lt;/figcaption&gt;&lt;/figure&gt;</content:encoded> <dc:date>2024-04-16T11:47:15+00:00</dc:date></item><item rdf:about="https://peter.czanik.hu/other/syslog-ng-sudo-json_compact-logs/"> <title>Peter Czanik: Working with sudo’s json_compact logs in syslog-ng</title> <link>https://peter.czanik.hu/other/syslog-ng-sudo-json_compact-logs/</link> <content:encoded><p>Version 1.9.16 of sudo will feature a new option for logging: json_compact. Why is this important? This new format can easily be read and parsed by a log management software, like syslog-ng.</p><p>Note that in this blog I am showing you a sudo feature which has not yet been released officially. You have to compile sudo yourself. By all means, if you have any other application writing JSON-formatted log messages, you can apply most of what you read here with slight modifications.</p><p>Read the rest at <a href="https://www.syslog-ng.com/community/b/blog/posts/working-with-sudo-s-json_5f00_compact-logs-in-syslog-ng">https://www.syslog-ng.com/community/b/blog/posts/working-with-sudo-s-json_5f00_compact-logs-in-syslog-ng</a></p>&lt;figure&gt;<img src="https://peter.czanik.hu/images/syslog-ng-logo1.png" />&lt;figcaption&gt; <h4>syslog-ng logo</h4> &lt;/figcaption&gt;&lt;/figure&gt;</content:encoded> <dc:date>2024-04-16T11:41:07+00:00</dc:date></item><item rdf:about="http://fossjon.wordpress.com/?p=5945"> <title>Jon Chiappetta: Thank you Python for years of service and reliability so far (and the ctypes module!)</title> <link>https://fossjon.wordpress.com/2024/04/16/thank-you-python-for-years-of-service-and-reliability-so-far-and-the-ctypes-module/</link> <content:encoded><p>So I’ve run into this issue in the past but I finally started looking into why Python is soo slow at running basic math operations in a long loop, for example, simple stream cipher operations. You’ll see lots of suggestions to use numpy instead, however, I didn’t find this to be the most helpful. Since I like writing/reading C, I remembered that Python has a built-in ctypes module which is very helpful and useful if you are in need of specialized and optimized code paths. You can pretty easily pass in integer and byte array pointers with little complexity! </p> <p>For example:</p> &lt;figure class="wp-block-image size-large"&gt;<a href="https://fossjon.files.wordpress.com/2024/04/p_c-1.png"><img width="1024" alt="" src="https://fossjon.files.wordpress.com/2024/04/p_c-1.png?w=1024" class="wp-image-5955" height="512" /></a>&lt;/figure&gt; <p>~</p> &lt;figure class="wp-block-image size-large"&gt;<a href="https://fossjon.files.wordpress.com/2024/04/p_y-4.png"><img width="1024" alt="" src="https://fossjon.files.wordpress.com/2024/04/p_y-4.png?w=1024" class="wp-image-5970" height="638" /></a>&lt;/figure&gt;</content:encoded> <dc:date>2024-04-16T11:04:51+00:00</dc:date></item><item rdf:about="https://major.io/p/texas-linux-fest-2024-recap/"> <title>Major Hayden: Texas Linux Fest 2024 recap 🤠</title> <link>https://major.io/p/texas-linux-fest-2024-recap/</link> <content:encoded>I gave two talks at this year’s event and ran into lots of old friends and colleagues. 🐧</content:encoded> <dc:date>2024-04-16T00:00:00+00:00</dc:date></item><item rdf:about="https://adam.younglogic.com/?p=11101"> <title>Adam Young: Running Keystone in development mode on Ubuntu 22.04</title> <link>http://adam.younglogic.com/2024/04/running-keystone-in-development-mode-on-ubuntu-22-04/</link> <content:encoded><p>Things have diverged a bit from <a href="https://docs.openstack.org/keystone/latest/contributor/set-up-keystone.html">the docs.</a> Just want to document here what I got working:<br /><br />I had already checked out Keystone and run the unit tests.<br /><br />I needed uwsgi</p> <pre class="wp-block-code"><code>sudo apt install uwsgi-coresudo apt install uwsgi-plugin-python3</code></pre> <p><br />Then a modified command line to run the server:</p> <pre class="wp-block-code"><code>uwsgi --http-socket 127.0.0.1:5000 --plugin /usr/lib/uwsgi/plugins/python3_plugin.so --wsgi-file $(which keystone-wsgi-public)</code></pre> <p></p> <p>This got me the last part</p> <p><a href="https://stackoverflow.com/questions/31330905/uwsgi-options-wsgi-file-and-module-not-recognized">https://stackoverflow.com/questions/31330905/uwsgi-options-wsgi-file-and-module-not-recognized</a></p></content:encoded> <dc:date>2024-04-15T18:30:08+00:00</dc:date></item><item rdf:about="https://avi.alkalay.net/?p=4399"> <title>! Avi Alkalay ¡: A Frequência Cardíaca de Yuja Wang</title> <link>https://avi.alkalay.net/2024/04/experimento-yuja-wang.html</link> <content:encoded><p>Chamando todos os cientistas de dados, sobretudo os que lidam com séries temporais, como eu, para ver um experimento.</p> <span id="more-4399"></span> &lt;figure class="wp-block-image size-large"&gt;<img width="1024" alt="" src="https://avi.alkalay.net/articlefiles/2024/04/img_1217-1-1024x576.jpg" class="wp-image-4408" height="576" />&lt;/figure&gt; <p>Mediram a frequência cardíaca de <a href="https://musicbrainz.org/artist/841236a2-176d-4032-a371-b2539f18ddca" target="_blank" rel="noreferrer noopener">Yuja Wang</a>, a pianista erudita mais badalada do momento — e a mais gata também <img src="https://s.w.org/images/core/emoji/14.0.0/72x72/2764.png" style="height: 1em;" class="wp-smiley" alt="❤" /> — enquanto executava uma façanha sem precedentes: tocar todos os 5 concertos de piano de Rachamninoff em uma única apresentação de mais de 4 horas de duração. Mediram também a frequência cardíaca do regente <a href="https://musicbrainz.org/artist/84c4f3ea-1897-4649-befb-ccbc013910ed" target="_blank" rel="noreferrer noopener">Yannick Nézet-Séguin</a>, de alguns músicos da orquestra, e também de ouvintes na platéia, no Carnegie Hall de Nova York, em 28 de janeiro de 2023.</p> <p>Os <a href="https://musicbrainz.org/series/4750bfe9-daf5-4691-bc62-7e107ab113af" target="_blank" rel="noreferrer noopener">concertos de piano de Rachmaninoff</a> não são qualquer obra. Conhecidos pela sua beleza e dificuldade, são frequentemente tratados como alguns dos pilares emocionais da humanidade. São 4 os concertos; e o “quinto” é um <a href="https://musicbrainz.org/work/17eea09b-0497-370c-a0a2-4f7f2d49300f" target="_blank" rel="noreferrer noopener">conjunto de variações, compostas por Rachmaninoff, sobre um tema de Paganini</a>.</p> <p>Entrevistas, explicações e análises de dados podem ser vistas no <a href="https://youtu.be/SuA9l77ODbs" target="_blank" rel="noreferrer noopener">vídeo do Carnegie Hall</a>. Algumas revelações dos dados coletados são óbvias: devido ao esforço físico, o coração de Yuja dispara conforme a densidade da partitura aumenta. Mas outras constatações são também muito interessantes, como o sincronismo cardíaco — ou emocional — entre a pianista, público e músicos.</p> <p>Um experimento multi-disciplinar absolutamente lindo, inédito e necessário.</p> &lt;figure class="wp-block-image size-large"&gt;<img width="1024" alt="" src="https://avi.alkalay.net/articlefiles/2024/04/img_1221-1-1024x576.jpg" class="wp-image-4411" height="576" />&lt;/figure&gt; &lt;figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"&gt;<div class="wp-block-embed__wrapper">&lt;iframe allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen="allowfullscreen" frameborder="0" height="365" referrerpolicy="strict-origin-when-cross-origin" src="https://www.youtube.com/embed/SuA9l77ODbs?feature=oembed" title="Tracking Yuja Wang’s Heartbeats During Her Rachmaninoff Marathon | Carnegie Hall" width="648"&gt;&lt;/iframe&gt;</div>&lt;/figure&gt;</content:encoded> <dc:date>2024-04-15T12:37:16+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=40118"> <title>Fedora Magazine: CVE-2024-3094: All Clear</title> <link>https://fedoramagazine.org/cve-2024-3094-all-clear/</link> <content:encoded><p>It’s official — CVE-2024-3094 is the “<a href="https://www.schneier.com/blog/archives/2024/04/backdoor-in-xz-utils-that-almost-happened.html" target="_blank" rel="noreferrer noopener">Backdoor in XZ Utils That Almost Happened</a>“. Fortunately, the malware was detected before we released the compromised version as an official update. If you are using a Fedora Linux 38 or 39, or an up-to-date Fedora Linux 40 Beta, you should be all set, and the upcoming Fedora Linux 40 final release is not affected.</p> <span id="more-40118"></span> <p>The XZ backdoor is a devious piece of work. It affects the SSH remote login protocol, which has a feature where users can be authenticated using a public-private key pair. The exploit sneaks a public key right into the allow-list, so someone out there with the corresponding key could log in to a compromised machine with full root access — without a trace. We have no evidence that the attackers ever got a chance to take advantage of this, but if the malware had slipped by undetected, it could have been devastating.</p> <p>Fortunately, the plot was foiled by Andres Freund while doing volunteer work in his spare time. He noticed that there was a slight change in performance, and decided to investigate. One of my Fedora friends quoted <a href="https://youtu.be/X1htrUN4ckk?si=DNOxf6F9w56nSMGQ&amp;t=38" target="_blank" rel="noreferrer noopener nofollow">John Denver</a>: “What one man can do is change the world and make it work again! Here you see what one man can do.”</p> <p>If you have a system with the Fedora Linux 40 Beta or Fedora Rawhide, and you applied updates during the time the compromised package was in our updates-testing repository, you should check to make sure that it is now reverted, and apply current updates if not. (You should have xz-5.4.6, as of this post.) On Fedora Workstation systems, the ssh daemon does not run by default, which additionally limits possible risk. However, if you did have the bad update on a system, or think you might have, we recommend a full reinstall out of an abundance of caution.<br /><br />Fedora Linux 38 and 39 never had even a candidate update for the compromised package, and we pulled the test update for 40, so it was never merged into the release.<br /><br /></p></content:encoded> <dc:date>2024-04-15T09:00:00+00:00</dc:date></item><item rdf:about="https://packit.dev/posts/weekly/2024/week-15"> <title>Weekly status of Packit Team: Week 15 in Packit</title> <link>https://packit.dev/posts/weekly/2024/week-15</link> <content:encoded><h2 class="anchor anchorWithStickyNavbar_LWe7" id="week-15-april-9th--april-15th">Week 15 (April 9th – April 15th)<a href="https://packit.dev/posts/weekly/rss.xml#week-15-april-9th--april-15th" class="hash-link" title="Direct link to Week 15 (April 9th – April 15th)"></a></h2><ul><li>We have planned the work for the next quarter, curious about what will come next? You can find it <a href="https://github.com/orgs/packit/projects/7/views/29" target="_blank" rel="noopener noreferrer">here</a>.</li></ul></content:encoded> <dc:date>2024-04-15T00:00:00+00:00</dc:date></item><item rdf:about="http://opensourcesecurity.io/?p=3363"> <title>Josh Bressers: Episode 424 – The Notepad++ Parasite Website</title> <link>https://opensourcesecurity.io/2024/04/14/episode-424-the-notepad-parasite-website/</link> <content:encoded><p><a href="https://infosec.exchange/@joshbressers">Josh</a> and <a href="https://infosec.exchange/@kurtseifried">Kurt</a> talk about a Notepad++ fake website. It’s possibly not illegal, but it’s certainly ethically wrong. We also end up discussing why it seems like all these weird and wild things keep happening. It’s probably due to the massive size of open source (and everything) now. Things have gotten gigantic and we didn’t really notice.</p> &lt;audio class="wp-audio-shortcode" controls="controls" id="audio-3363-3" preload="none" style="width: 100%;"&gt;&lt;source src="https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_424_The_Notepad_Parasite_Website.mp3?_=3" type="audio/mpeg"&gt;<a href="https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_424_The_Notepad_Parasite_Website.mp3">https://traffic.libsyn.com/opensourcesecuritypodcast/Episode_424_The_Notepad_Parasite_Website.mp3</a>&lt;/audio&gt; <h2 class="wp-block-heading">Show Notes</h2> <ul><li><a href="https://notepad-plus-plus.org/news/help-to-take-down-parasite-site/">Help us to take down the parasite website</a></li> <li><a href="https://docs.google.com/presentation/d/1exE08fUUra34FtlGaAk_kD4GSFuOftxej7DtQib_lus/edit#slide=id.g249ebc07193_0_20">Open Source is bigger than you can imagine</a></li> <li><a href="https://en.wikipedia.org/wiki/Toronto_Pearson_International_Airport_heist">Toronto Pearson International Airport heist</a></li></ul></content:encoded> <dc:date>2024-04-15T00:00:00+00:00</dc:date></item><item rdf:about="https://blogs.gnome.org/otte/?p=6916"> <title>Benjamin Otte: Making GTK graphics offloading work</title> <link>https://blogs.gnome.org/otte/2024/04/14/making-gtk-graphics-offloading-work/</link> <content:encoded><p>(I need to put that somewhere because people ask about it and having a little post to explain it is nice.)</p><p>What’s it about?<br /><a href="https://blog.gtk.org/2023/11/15/introducing-graphics-offload/">GTK recently introduced the ability to offload graphics rendering</a>, but it needs rather recent everything to work well for offloading video decoding.</p><p>So, what do you need to make sure this works?</p><p>First, you of course need a video to test. On a modern desktop computer, you want a 4k 60fps video or better to have something that pushes your CPU to the limits so you know when it doesn’t work. Of course, the recommendation has to be <a href="http://bbb3d.renderfarming.net/download.html">Big Buck Bunny at the highest of qualities</a> – be aware that the most excellent 4000×2250 @ 60fps encoding is 850MB. On my Intel TigerLake, that occasionally drops frames when I play that with software decoding, and I can definitely hear the fan turn on.<br />When selecting a video file, keep in mind that the format matters.</p><p>Second, you need hardware decoding. That is provided by libva and can be queried using the <code>vainfo</code> tool (which comes in the `libva-utils` package in Fedora). If that prints a long list of formats (it’s about 40 for me), you’re good. If it doesn’t, you’ll need to go hunt for the drivers – due to the patent madness surrounding video formats that may be more complicated than you wish. For example, on my Intel laptop on Fedora, I need the <code>intel-media-driver</code> package which is hidden in the nonfree <a href="https://rpmfusion.org/Configuration/">RPMFusion repository</a>.<br />If you look at the list from <code>vainfo</code>, the format names give some hints – usually VP9 and MPEG2 exist. H264 and HEVC aka H265 are the patent madness, and recent GPUs can sometimes do AV1. The Big Buck Bunny video from above is H264, so if you’re following along, make sure that works.</p><p>Now you need a working video player. I’ll be using <code>gtk4-demo</code> (which is in the <code>gtk4-devel-tools</code> package, but you already have that installed of course) and its video player example because I know it works there. A shoutout goes out to <a href="https://github.com/agx/livi">livi</a> which was the first non-demo video player to have a release that supports graphics offloading. You need GTK 4.14 and GStreamer 1.24 for this to work. At the time of writing, this is only available in Fedora rawhide, but hopefully Fedora 40 will gain the packages soon.</p><p>If you installed new packages above, now is a good time to check if GStreamer picked up all the hardware decoders. <code>gst-inspect-1.0 va</code> will list all the elements with libva support. If it didn’t pick up decoders for all the formats it should have (there should be a <code>vah264dec</code> listed for H264 if you want to decode the video above), then the easiest way to get them is to delete GStreamer’s registry cache in <code>~/.cache/gstreamer-1.0</code>.</p><p>If you want to make sure GStreamer does the right thing, you can run the video player with <code>GST_DEBUG=GST_ELEMENT_FACTORY:4</code>. It will print out debug messages about all the elements it is creating for playback. If that includes a line for an element from the previous list (like `vah264dec` in our example) things are working. If it picks something else (like `avdec_h264` or `openh264dec`) then they are not.</p><p>Finally you need a compositor that supports YUV formats. Most compositors do – gnome-shell does since version 45 for example – but checking can’t hurt: If <code>wayland-info</code> (in the <code>wayland-utils</code> package in Fedora) lists the NV12 format, you’re good.</p><p>And now everything works.<br />If you have a 2nd monitor you can marvel at what goes on behind the scenes by running the video player with <code>GDK_DEBUG=dmabuf,offload</code> and GTK will tell you what it does for every frame, and you can see it dynamically switching between offloading or not as you fullscreen (or not), click on the controls (or not) and so on. Or you could have used it previously to see why things didn’t work.<br />You can also look at the <code>top</code> and <code>gputop</code> variant of your choice and you will see that the video player takes a bit of CPU to drive the video decoding engine and inform the compositor about new frames and the compositor takes a bit of CPU telling the 3D engine to composite things and send them to the monitor. With the video above it’s around 10% on my laptop for the CPU usage each and about 20% GPU usage.</p><p>And before anyone starts complaining that this is way too complicated: If you read carefully, all of this should work out of the box in the near future. This post just lists the tools to troubleshoot what went wrong while developing a fast video player.</p></content:encoded> <dc:date>2024-04-14T16:37:14+00:00</dc:date></item><item rdf:about="urn:md5:64d278e5b08180fa7791da9dfda9aeec"> <title>Remi Collet: PHP version 8.1.28, 8.2.18 and 8.3.6</title> <link>https://blog.remirepo.net/post/2024/04/12/PHP-version-8.1.28-8.2.18-and-8.3.6</link> <content:encoded><p>RPMs of <strong>PHP version 8.3.6</strong> are available in the <strong>remi-modular</strong> repository for <strong>Fedora</strong> ≥ 38 and <strong>Enterprise Linux</strong> ≥ 8 (RHEL, Alma, CentOS, Rocky...) and in the <strong>remi-php83</strong> repository for EL 7.</p> <p>RPMs of <strong>PHP version 8.2.18</strong> are available in the <strong>remi-modular</strong> repository for <strong>Fedora</strong> ≥ 38 and <strong>Enterprise Linux</strong> ≥ 8 (RHEL, Alma, CentOS, Rocky...) and in the <strong>remi-php82</strong> repository for EL 7.</p> <p>RPMs of <strong>PHP version 8.1.28</strong> are available in the <strong>remi-modular</strong> repository for <strong>Fedora</strong> ≥ 38 and <strong>Enterprise Linux</strong> ≥ 8 (RHEL, Alma, CentOS, Rocky...) and in the <strong>remi-php81</strong> repository for EL 7.</p> <p><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" /> The <strong>Fedora 39</strong>, <strong>40</strong>, <strong>EL-8</strong> and <strong>EL-9</strong> packages (modules and SCL) are available for <strong>x86_64</strong> and <strong>aarch64</strong>.</p> <p><img src="https://blog.remirepo.net/public/icons/emblem-important-2-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-important-2-24.png" /><a href="https://blog.remirepo.net/post/2023/11/27/PHP-8.0-is-retired" class="ref-post">PHP version 8.0</a> has reached its end of life and is no longer maintained by the <a href="https://php.net/supported-versions.php">PHP project</a>.</p> <p>These versions are also available as <em>Software Collections</em> in the <strong>remi-safe</strong> repository.</p> <p><img src="https://blog.remirepo.net/public/icons/security-medium-2-32.png" style="float: left; margin: 0 1em 0 0;" alt="security-medium-2-24.png" />These Versions fix 3 security bugs (<strong>CVE-2024-2756</strong>, <strong>CVE-2024-3096</strong> and <strong>CVE-2024-2757</strong>), so update is strongly recommended.</p> <p>Version announcements:</p> <ul> <li><a href="https://www.php.net/releases/8_3_6.php">PHP 8.3.6 Release Annoucement</a></li> <li><a href="https://www.php.net/releases/8_2_18.php">PHP 8.2.18 Release Annoucement</a></li> <li><a href="https://www.php.net/releases/8_1_28.php">PHP 8.1.28 Release Annoucement</a></li></ul> <p><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" />Installation: use the <a href="https://rpms.remirepo.net/wizard/">Configuration Wizard</a> and choose your version and installation mode.</p> <p><strong>Replacement</strong> of default PHP by version <strong>8.3</strong> installation (<strong>simplest</strong>):</p> <pre>dnf module switch-to php:remi-8.3/common</pre> <p>or, the old <strong>EL-7</strong> way:</p> <pre>yum-config-manager --enable remi-php83yum update php\*</pre> <p><strong>Parallel installation</strong> of version <strong>8.3</strong> as <a href="https://blog.remirepo.net/post/2023/06/06/PHP-8.3-as-Software-Collection" class="ref-post">Software Collection</a></p> <pre>yum install php83</pre> <p><strong>Replacement</strong> of default PHP by version <strong>8.2</strong> installation (<strong>simplest</strong>):</p> <pre>dnf module switch-to php:remi-8.2/common</pre> <p>or, the old <strong>EL-7</strong> way:</p> <pre>yum-config-manager --enable remi-php82yum update</pre> <p><strong>Parallel installation</strong> of version <strong>8.2</strong> as <a href="https://blog.remirepo.net/post/2022/06/10/PHP-8.2-as-Software-Collection" class="ref-post">Software Collection</a></p> <pre>yum install php82</pre> <p>And soon in the official updates:</p> <ul> <li>Fedora <strong>Rawhide</strong> now has PHP version <strong>8.3.6</strong></li> <li><a href="https://bodhi.fedoraproject.org/updates/FEDORA-2024-f21ed8861c">Fedora 40 - PHP 8.3.6</a></li> <li><a href="https://bodhi.fedoraproject.org/updates/FEDORA-2024-b46619f761">Fedora 39 - PHP 8.2.18</a></li> <li><a href="https://bodhi.fedoraproject.org/updates/FEDORA-2024-39d50cc975">Fedora 38 - PHP 8.2.18</a></li></ul> <p><strong><img src="https://blog.remirepo.net/public/icons/emblem-important-2-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-important-2-24.png" />To be noticed : </strong></p> <ul> <li>EL-9 RPMs are built using RHEL-<strong>9.3</strong></li> <li>EL-8 RPMs are built using RHEL-<strong>8.9</strong></li> <li>EL-7 RPMs are built using RHEL-<strong>7.9</strong></li> <li><strong>intl</strong> extension now uses <strong>libicu73 </strong>(version<strong> 73.2</strong>)</li> <li><strong>mbstring</strong> extension (EL builds) now uses <strong>oniguruma5php</strong> (version <strong>6.9.9</strong>, instead of the outdated system library)</li> <li><strong>oci8</strong> extension now uses the <strong>RPM</strong> of <strong>Oracle Instant Client </strong>version<strong> 21.13 </strong>on x86_64, <strong>19.19</strong> on aarch64</li> <li>a lot of extensions are also available, see the <a href="https://blog.remirepo.net/pages/PECL-extensions-RPM-status">PHP extensions RPM status (from PECL and other sources)</a> page</li></ul> <p><strong><img src="https://blog.remirepo.net/public/icons/emblem-notice-24.png" style="float: left; margin: 0 1em 0 0;" alt="emblem-notice-24.png" />Information</strong>:</p> <ul> <li><a href="https://php.net/manual/en/migration81.php" hreflang="en">Migrating from PHP 8.0.x to PHP 8.1.x</a></li> <li><a href="https://php.net/manual/en/migration82.php" hreflang="en">Migrating from PHP 8.1.x to PHP 8.2.x</a></li> <li><a href="https://php.net/manual/en/migration83.php" hreflang="en">Migrating from PHP 8.2.x to PHP 8.3.x</a></li></ul> <p align="center"><strong>Base</strong> packages (php)</p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php-common&amp;version=8.3.6&amp;lang=en&amp;release=1" style="margin: 1em auto; display: block;" alt="" /></p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php-common&amp;version=8.2.18&amp;lang=en&amp;release=1" style="margin: 1em auto; display: block;" alt="" /></p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php-common&amp;version=8.1.28&amp;lang=en&amp;release=1" style="margin: 1em auto; display: block;" alt="" /></p> <p align="center"><strong>Software Collections</strong> (php81 / php82 / php83)</p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php83-php-common&amp;version=8.3.6&amp;lang=en&amp;release=1" style="margin: 1em auto; display: block;" alt="" /></p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php82-php-common&amp;version=8.2.18&amp;lang=en&amp;release=1" style="margin: 1em auto; display: block;" alt="" /></p> <p><img src="https://blog.remirepo.net/downcpt.php?name=php81-php-common&amp;version=8.1.28&amp;lang=en&amp;release=1" style="margin: 1em auto; display: block;" alt="" /></p></content:encoded> <dc:date>2024-04-12T15:59:00+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13533"> <title>Fedora Community Blog: Infra and RelEng Update – Week 15 2024</title> <link>https://communityblog.fedoraproject.org/infra-and-releng-update-week-15-2024/</link> <content:encoded><p>This is a weekly report from the I&amp;R (<a href="https://docs.fedoraproject.org/en-US/infra/">Infrastructure &amp; Release Engineering</a>) Team. It also contains updates for CPE (<a href="https://docs.fedoraproject.org/en-US/cpe/">Community Platform Engineering</a>) Team as the CPE initiatives are in most cases tied to I&amp;R work.</p> <p>We provide you both infographic and text version of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in depth details look below the infographic.</p> <p>Week: 08 April – 12 April 2024</p> <span id="more-13533"></span> &lt;figure class="wp-block-image size-full wp-lightbox-container" data-wp-context="{"uploadedSrc":"https:\/\/communityblog.fedoraproject.org\/wp-content\/uploads\/2024\/04\/IR_Weekly_15-scaled.jpg","figureClassNames":"wp-block-image size-full","figureStyles":null,"imgClassNames":"wp-image-13534","imgStyles":null,"targetWidth":2560,"targetHeight":2295,"scaleAttr":false,"ariaLabel":"Enlarge image: I\u0026R infographic`","alt":"I\u0026R infographic`"}" data-wp-interactive="core/image"&gt;<img width="2560" alt="I&amp;R infographic`" src="https://communityblog.fedoraproject.org/wp-content/uploads/2024/04/IR_Weekly_15-scaled.jpg" class="wp-image-13534" height="2295" /><button type="button" class="lightbox-trigger"> <svg height="12" width="12" xmlns="http://www.w3.org/2000/svg" fill="none"> <path d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" fill="#fff"> </path></svg> </button>&lt;/figure&gt; <h2 class="wp-block-heading">Infrastructure &amp; Release Engineering</h2> <p>The purpose of this team is to take care of day to day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.<br />It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).<br /><a href="https://issues.redhat.com/issues/?filter=12428298">List of planned/in-progress issues</a></p> <h3 class="wp-block-heading">Fedora Infra</h3> <ul><li>In progress:<ul><li>Adding template to handle monitoring of external hosts to zabbix</li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11815">rhel7 EOL</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11543">Migration of registry.fedoraproject.org to quay.io</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11611">add monitoring for dnf countme</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11393">Replace Nagios with Zabbix in Fedora Infrastructure</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11687">notifications do not notify</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11714">DNF countme minor changes post migration</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11755">vmhost-x86-copr02 hardware issues</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11820">PDC retirement</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11715">Move from iptables to firewalld</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/10383">fedoraplanet.org: Upgrade Venus to Pluto</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/8455">Move mailman to newer release of Fedora or CentOS</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11726">Setup RISC-V builder(s) VM in Fedora Infrastructure</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11711">Update compose hosts to get latest pungi release (4.6.0)</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11505">Deploy new sign hardware/software</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11826">logrotate not working on proxy31</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11641">Commits don’t end up on the scm-commits list</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11838">AWS S3 bucket permissions for openQA cloud enablement</a></li></ul></li> <li>Done:<ul><li><a href="https://github.com/fedora-infra/mdapi/pull/256">Fixing tests for MDAPI</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11874">Update rpm-ostree on compose hosts with fixes for CVE-2024-2905</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11866">Request for OpenScanHub mailing list</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11865">Request for access to central syslog host</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11864">Request for access to NFS storage for redis</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11852">Request for access to NFS storage</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11799">investigate ipsilon hangs</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11795">Create Gitlab group for the Go SIG</a></li> <li><a href="https://pagure.io/fedora-infrastructure/issue/11870">MirrorManager + mirrorlist returning mirrors that don’t have the arch requested</a></li> <li><a href="https://pagure.io/fedora-infra/arc/issue/162">Revise the webhook2fedoramessaging investigation</a></li> <li>Outreachy Intern Selected for Webhook2FedoraMessaging – Announcement Soon!</li> <li><a href="https://pypi.org/project/mdapi/3.1.5/#files">MDAPI v3.1.5</a> is now available on <a href="https://mdapi.stg.fedoraproject.org/">staging environment</a> – TEST NOW!</li></ul></li></ul> <h3 class="wp-block-heading">CentOS Infra including CentOS CI</h3> <ul><li>In progress:<ul><li><a href="https://pagure.io/centos-infra/issue/1358">c8s/c7 EOL infrastructure planning</a></li></ul></li> <li>Done:<ul><li><a href="https://issues.redhat.com/browse/CS-2014">Update to Koji 1.34 to allow building Draft Builds</a></li> <li><a href="https://pagure.io/centos-infra/issue/1260">Migrate lists.centos.org</a></li> <li><a href="https://pagure.io/centos-infra/issue/1370">Migrate CBS kojid aarch64 builders to refreshed infra</a></li> <li><a href="https://pagure.io/centos-infra/issue/1384">Partial rsync of mirrors.c.o to OpenInfra</a></li> <li><a href="https://pagure.io/centos-infra/issue/1386">Extras CentOS7 reposync error : docker-debuginfo-1.13.1-210.git7d71120.el7.centos.x86_64.rpm</a></li> <li><a href="https://pagure.io/centos-infra/issue/1388">Random issues pulling packages in CBS builds</a></li> <li><a href="https://pagure.io/centos-infra/issue/1389">Cloning kernel repo from git.centos.org dies prematurely</a></li> <li><a href="https://issues.redhat.com/browse/CS-2056">Postgresql DB host under heavy load after koji 1.34 upgrade</a></li> <li><a href="https://pagure.io/centos-infra/issue/1390">Decommission last remanining centos 7 mirror.centos.org pool member</a></li></ul></li></ul> <h3 class="wp-block-heading">Release Engineering</h3> <ul><li>In progress:<ul><li><a href="https://pagure.io/releng/issue/8601">Packages that fail to build SRPM are not reported during the mass rebuild bugzillas</a></li> <li><a href="https://pagure.io/releng/issue/11385">Silverblue aarch64 installer image compose always fails on F38 and Rawhide</a></li> <li><a href="https://pagure.io/releng/issue/11358">Sync RCs to alt/stg dl.fp.o</a></li> <li><a href="https://pagure.io/releng/issue/11531">i686 builders need to use 32-bit inode numbers</a></li> <li><a href="https://pagure.io/releng/issue/11673">Fixes for release-candidate.sh in pungi-fedora</a></li> <li><a href="https://pagure.io/releng/issue/8929">When orphaning packages, keep the original owner as co-maintainer</a></li> <li><a href="https://pagure.io/releng/issue/12030">adjust torrent_hashes.py to non bittorrent world</a></li> <li><a href="https://pagure.io/releng/issue/7337">Emit fedmsg when candidate composes are synced to stage</a></li> <li><a href="https://pagure.io/releng/issue/9880">Publish “latest” tag to quay.io/fedora/fedora</a></li> <li><a href="https://pagure.io/releng/issue/9153">Use an automated script to control checksums of compose images</a></li> <li><a href="https://pagure.io/releng/issue/9674">Create an ansible playbook to do the mass-branching</a></li> <li><a href="https://pagure.io/releng/issue/12028">Package retirements are broken in rawhide</a></li> <li><a href="https://pagure.io/releng/issue/11957">Implement checks on package retirements</a></li></ul></li> <li>Done:<ul><li><a href="https://pagure.io/releng/issue/12051">buildhw-a64-23 is low on disk space</a></li> <li><a href="https://pagure.io/releng/issue/12047">Please add flatpak-runtime-config to f40-flatpak-runtime</a></li> <li><a href="https://pagure.io/pungi-fedora/pull-request/1270">Setup for F40 final rcs</a></li></ul></li></ul> <h2 class="wp-block-heading">CPE Initiatives</h2> <h3 class="wp-block-heading">EPEL</h3> <p><a href="https://docs.fedoraproject.org/en-US/epel/">Extra Packages for Enterprise Linux</a> (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS, Scientific Linux (SL) and Oracle Linux (OL).</p> <h2 class="wp-block-heading">Updates</h2> <ul><li>Fixing uninstallable <a href="https://src.fedoraproject.org/rpms/plplot/pull-request/7">plplot-qt-devel package</a></li> <li>Presentation for Texas Linux Fest giving overview of Fedora, CentOS, RHEL, and EPEL</li></ul> <h3 class="wp-block-heading">Community Design</h3> <p>CPE has few members that are working as part of <a href="https://fedoraproject.org/wiki/Design">Community Design Team</a>. This team is working on anything related to design in Fedora Community.</p> <h2 class="wp-block-heading">Updates</h2> <ul><li>Podman Desktop Interface<ul><li>Dashboard <a href="https://github.com/containers/podman-desktop/issues/6547">improvements</a></li></ul></li> <li>F40 Wallpaper<ul><li><a href="https://gitlab.com/groups/fedora/design/-/epics/32">Finished up </a>for the end of freeze next week</li></ul></li></ul> <h3 class="wp-block-heading">List of new releases of apps maintained by CPE</h3> <ul><li>Minor update of Bodhi from 8.0.2 to 8.1.0 on 2024-04-09: <a href="https://github.com/fedora-infra/bodhi/releases/tag/8.1.0">https://github.com/fedora-infra/bodhi/releases/tag/8.1.0</a></li> <li>Patch update of MD API from 3.1.4 to 3.1.5 on 2024-04-08: <a href="https://github.com/fedora-infra/mdapi/releases/tag/3.1.5">https://github.com/fedora-infra/mdapi/releases/tag/3.1.5</a></li> <li>Minor update of Bodhi from 2.1.2 to 2.2.0 on 2024-04-07: <a href="https://github.com/fedora-infra/bodhi/releases/tag/2.2.0">https://github.com/fedora-infra/bodhi/releases/tag/2.2.0</a></li></ul> <p>If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on <a href="https://matrix.to/#/#redhat-cpe:matrix.org">matrix</a>.</p><p>The post <a href="https://communityblog.fedoraproject.org/infra-and-releng-update-week-15-2024/">Infra and RelEng Update – Week 15 2024</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-12T10:00:00+00:00</dc:date></item><item rdf:about="https://avi.alkalay.net/?p=4390"> <title>! Avi Alkalay ¡: Profissionais high-tech preferem MacBook</title> <link>https://avi.alkalay.net/2024/04/macbook-para-high-tech.html</link> <content:encoded><p>Há mais de 10 anos, por todas as últimas empresas que passei — umas 3 ou 4 — MacBook é o laptop padrão que profissionais high-tech usam. </p> <p>E hoje em dia estranham quando só lhes deixam usar Windows. Mas não falam abertamente sobre isso por incorretamente acharem que é um assunto banal. Só que não é. Da perspectiva de RH e de ambiente de trabalho, no mínimo para o setor high-tech, equipamento de alta qualidade, moderno e adequado é ponto positivo de atração e retenção de talentos.</p> <span id="more-4390"></span> <p>MacBook é equipamento indiscutivelmente melhor do que um laptop médio baseado em Windows.</p> <ul><li>A <strong>tela de alta densidade</strong> (conhecida como Retina) é mais confortável aos olhos e faz caber mais informação.</li> <li>O equipamento é <strong>mais coeso, mais fino e mais leve</strong> para se carregar na mochila.</li> <li>A <strong>bateria</strong> dura muitas horas mais, parece que nunca acaba.</li> <li>O laptop <strong>esquenta menos</strong> por ter CPU mais eficiente e mais moderna que a de um laptop projetado para Windows.</li> <li>O <strong>teclado</strong> é melhor, permite mais possibilidades de escrita, correção e substituição de texto, e tem melhor suporte a Unicode.</li> <li>O <strong>trackpad</strong> é maior, mais ergonômico e tem mais funções.</li> <li>A qualidade da câmera, microfone, alto-falantes é a melhor possível.</li> <li>E o sistema operacional, baseado em Posix (Unix), é ambiente mais familiar para trabalhos tipicamente high-tech, por ser similar a ambientes de produção.</li></ul> <p>Repare que <strong>não entrei no mérito</strong> de segurança, facilidade de uso e nem boniteza do macOS. Isso é bem menos relevante para este contexto. E convenhamos que o Microsoft Windows não deixa a desejar, é igualmente bom em todos estes quesitos. <strong>A preferência por MacBook continua girando em torno do hardware</strong>, não do software.</p> <p>O conjunto citado e mais muitos outros pequenos detalhes faz do MacBook a plataforma preferida por profissionais high-tech, e outros também, que passam muitas horas do dia na frente de um computador.</p> <p>É por isso que quem experimenta dificilmente volta atrás para hardware mediano baseado em Windows.</p> <h4 class="wp-block-heading">MacBook é equipamento mais caro?</h4> <p>Se você procurar no mercado de laptops Windows as linhas com as mesmas características de tela, ergonomia, leveza, bateria, teclado etc, vai perceber que os equipamentos serão mais caros ainda do que um MacBook equivalente. Como referência, as linhas de alta qualidade de outros fabricantes são XPS da Dell, Spectre ou Envy da HP, X1 da Lenovo.</p> <p>O mercado de laptops Windows, por ser mais competitivo, inova no palavreado para vender refugo. Digo isso porque já fiz essa pesquisa e terminei frustrado. Eu considero refugo as linhas de laptops inferiores das citadas acima, por usarem componentes físicos obsoletos e de menor qualidade.</p> <p>Apesar de “ser mais caro”, a empresa opta ter escritório na Av. Paulista, ao invés de Alphaville.</p> <p>Apesar de “ser mais caro”, a empresa prefere instalar ar-condicionado, ao invés de ventiladores ou de manter janelas abertas.</p> <p>Pois então, optar por oferecer um laptop melhor aos funcionários que valorizam alta qualidade técnica é o mesmo tipo de escolha.</p> <p>Então não é uma questão monetária e sim de usar características mínimas para os padrões de hoje em dia.</p> <p>Este artigo é uma versão corporativa para outro artigo meu, titulado <a href="https://avi.alkalay.net/2021/07/como-escolher-um-laptop.html">Como Escolher e Comprar um Laptop</a>.</p> &lt;figure class="wp-block-embed is-type-wp-embed is-provider-avi-alkalay wp-block-embed-avi-alkalay"&gt;<div class="wp-block-embed__wrapper"><blockquote class="wp-embedded-content"><a href="https://avi.alkalay.net/2021/07/como-escolher-um-laptop.html">Como Escolher e Comprar um Laptop</a></blockquote>&lt;iframe class="wp-embedded-content" data-secret="YaE4flUjrE" frameborder="0" height="338" marginheight="0" marginwidth="0" sandbox="allow-scripts" scrolling="no" security="restricted" src="https://avi.alkalay.net/2021/07/como-escolher-um-laptop.html/embed#?secret=LKyLkIwGDp#?secret=YaE4flUjrE" title="“Como Escolher e Comprar um Laptop” — Avi Alkalay" width="600"&gt;&lt;/iframe&gt;</div>&lt;/figure&gt;</content:encoded> <dc:date>2024-04-11T10:53:26+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13477"> <title>Fedora Community Blog: Fedora DEI Team 2023 Q4: Appreciation Week and new members</title> <link>https://communityblog.fedoraproject.org/fedora-dei-team-2023-q4/</link> <content:encoded><p>The <a href="https://docs.fedoraproject.org/en-US/dei/" target="_blank" rel="noreferrer noopener">Fedora Diversity, Equity, &amp; Inclusion (DEI) Team</a> rounded out 2023 with a focus on celebrating the 20th anniversary of the Fedora Project and officially welcoming new team members. This post is a brief recap of the fourth quarter of 2023 (October to December) for the DEI Team. The end of the year is typically a slower time in Fedora due to holidays, but we had some major highlights in 2023 Q4 anyways:</p> <ul><li>Shifted our sprint planning from a monthly cadence to a quarterly cadence.</li> <li>Revived <a href="https://communityblog.fedoraproject.org/fedora-appreciation-week-2023/">Fedora Appreciation Week</a> after five years, to celebrate our 20th anniversary.</li> <li>Welcomed two new team members, <a href="https://emmakidney.wordpress.com/" target="_blank" rel="noreferrer noopener">Robert Wright</a> and <a href="https://emmakidney.wordpress.com/">Emma Kidney</a>.</li> <li>Fedora Pride was established, and represented at some of our virtual events.</li></ul> <p>This post summarizes these highlights and also paints a picture of what we were looking forward to in 2024 Q1. Read on to get the full scoop!</p> <span id="more-13477"></span> <h2 class="wp-block-heading">Shifting from monthly to quarterly planning</h2> <p>In our <a href="https://communityblog.fedoraproject.org/charting-the-vision-dei-team-october-2023/">previous sprint report</a>, the new GitLab-centered workflow was introduced. We originally launched with a monthly cadence. However, we quickly realized that a monthly cadence was not the right fit for our team. Many of our projects span many months, like planning an event. This means that a few things get done every month, but many ongoing tasks shift every month.</p> <p>Adopting a quarterly format worked better because that better matches the cadence at which the Fedora DEI Team operates. Event planning might span two to three months. This means that most events could fit into a three-month window. Some things still get shifted from quarter to quarter, but as long as we anticipate that, it works fine for us!</p> <p>Most importantly, a quarterly cadence means that we can always clearly describe what was accomplished, what we are working on, and we can speculate on the future. Our hope is that it also makes reports like this easier to read!</p> <h2 class="wp-block-heading">A successful Fedora Appreciation Week</h2> <p>The previous report mentioned that planning for the Fedora Appreciation Week was underway. And it successfully happened! For context, Fedora Appreciation Week first started <a href="https://communityblog.fedoraproject.org/tag/fedora-appreciation-week-2018/">in 2018</a> for the 15th anniversary of Fedora. Fedora Appreciation Week, abbreviated as FAW, is a week-long event organized by the Fedora DEI Team. It is dedicated to celebrating the efforts of Fedora Project contributors and expressing gratitude to one another. Fedora Appreciation Week happened from November 6–12, 2023.</p> <h3 class="wp-block-heading">At-a-glance statistics from Appreciation Week</h3> <p><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f680.png" style="height: 1em;" class="wp-smiley" alt="🚀" /> Here are some stats from FAW 2023:</p> <ul><li>12 <a href="https://communityblog.fedoraproject.org/tag/fedora-appreciation-week-2023/">Contributor Stories</a></li> <li>44 images shared <a href="https://discussion.fedoraproject.org/t/what-are-your-favorite-moments-from-the-fedora-community-share-them-in-photos/93646" target="_blank" rel="noreferrer noopener">on Fedora Discussion</a></li> <li>4 speakers who shared their Fedora Story at the Release Party: <strong>Chris Idoko, Emma Kidney, Kevin Fenzi, and Aoife Moloney</strong> <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f389.png" style="height: 1em;" class="wp-smiley" alt="🎉" /></li> <li>15 posts on social media with the #WeAreFedora hashtag</li> <li>lots of cookies <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f36a.png" style="height: 1em;" class="wp-smiley" alt="🍪" /></li></ul> <h3 class="wp-block-heading">Read the Contributor Stories</h3> <p><img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f4cd.png" style="height: 1em;" class="wp-smiley" alt="📍" /> You can check out all the articles highlighting what happened during FAW:</p> <ul><li><a href="https://communityblog.fedoraproject.org/appreciation-week-2023-day-1/">FAW Day 1</a></li> <li><a href="https://communityblog.fedoraproject.org/appreciation-week-2023-day-2/">FAW Day 2</a></li> <li><a href="https://communityblog.fedoraproject.org/appreciation-week-2023-day-3/">FAW Day 3</a></li> <li><a href="https://communityblog.fedoraproject.org/appreciation-week-2023-day-4/">FAW Day 4</a></li> <li><a href="https://communityblog.fedoraproject.org/appreciation-week-2023-day-5/">FAW Day 5</a></li> <li><a href="https://communityblog.fedoraproject.org/appreciation-week-2023-day-6/">FAW Day 6</a></li> <li><a href="https://communityblog.fedoraproject.org/appreciation-week-2023-day-7/">FAW Day 7</a></li></ul> <h3 class="wp-block-heading">Thank you to our contributors!</h3> <p>Thanks a lot to everyone who contributed to making Fedora Appreciation Week happen! <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f499.png" style="height: 1em;" class="wp-smiley" alt="💙" /> <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f389.png" style="height: 1em;" class="wp-smiley" alt="🎉" /> Your participation and contributions have made this event a truly special and memorable experience. As we move forward, let’s carry the spirit of gratitude with us and continue to acknowledge the exceptional efforts of our Fedora community.</p> <h2 class="wp-block-heading">Welcoming Robert and Emma to the DEI Team</h2> <p>Our Fedora DEI Team continues to grow! Although neither of these two names were new to us, we officially nominated and voted <a href="https://gitlab.com/fedora/dei/home/-/issues/24" target="_blank" rel="noreferrer noopener">Robert Wright</a> and <a href="https://gitlab.com/fedora/dei/home/-/issues/27" target="_blank" rel="noreferrer noopener">Emma Kidney</a> as the newest inductees to the Fedora DEI Team. Robert is an infrastructure contributor and co-lead to the <a href="https://fedoraproject.org/wiki/Initiatives/Community_Ops_2024_Reboot" target="_blank" rel="noreferrer noopener">Community Operations Community Initiative</a>. Emma is a Design Team member and she has been a key contributor for managing graphic design and brand identity for events like Fedora Flock and our release parties. She also <a href="https://emmakidney.com/2023/05/11/concept-generation/" target="_blank" rel="noreferrer noopener">designed our team logo</a>!</p> <p>We are so excited to have Robert and Emma join us as official team members! Although their contributions span before they were officially inducted, we cannot wait to see them continue to contribute and shine in our team. <img src="https://s.w.org/images/core/emoji/15.0.3/72x72/1f680.png" style="height: 1em;" class="wp-smiley" alt="🚀" /></p> <h2 class="wp-block-heading">Fedora Pride establishes as a Fedora DEI Community</h2> <p>In Q4 2023, Fedora Pride achieved several notable accomplishments:</p> <ul><li><strong>Successfully <a href="https://fedoraproject.org/wiki/User:Rwright/F39_Release_Party_Among_Us_Session" target="_blank" rel="noreferrer noopener">hosted a release party mini-event</a> for Fedora 39</strong>, featuring an engaging session of the game Among Us. This event fostered community engagement and celebrated the new release.</li> <li><strong>Held meetings in October 2023 (and a few months of 2023)</strong>. The session focused on strategizing future initiatives and strengthening community involvement.</li> <li><strong>Initiated the development of a <a href="https://gitlab.com/fedora/dei/pride/planning" target="_blank" rel="noreferrer noopener">new GitLab project</a></strong> to hold SIG identified issues.</li></ul> <h2 class="wp-block-heading">Looking ahead to 2024 Q1</h2> <p>At the time of publishing, this report is already coming out at the end of 2024 Q1. Oops! That means you can expect to see a 2024 Q1 article later this April. However, to give you an early sneak preview, this is a summary of what the DEI Team was working on from January to March 2024:</p> <ul><li><strong><a href="https://fedoraproject.org/wiki/Council/2024_Hackfest" target="_blank" rel="noreferrer noopener">Fedora Council Hackfest</a></strong>: The Fedora Council held its annual in-person hackfest in February 2024 for annual planning. The DEI Advisor, Jona Azizaj, represented the DEI Team in conversations about the Fedora Strategy and more. Look out for more about the Council Hackfest in future Community Blog posts.</li> <li><strong><a href="https://gitlab.com/fedora/dei/home/-/issues/19" target="_blank" rel="noreferrer noopener">Fedora Week of Diversity</a></strong>: Planning is already underway for the DEI Team’s next virtual in June 2024. Fedora Week of Diversity is the successor to Fedora Women’s Day, originally started in 2016 as a celebration of the diverse people who make up our Fedora community. Volunteers are needed! See the issue for more details.</li> <li><strong><a href="https://gitlab.com/fedora/dei/home/-/issues/31" target="_blank" rel="noreferrer noopener">GNOME collaboration</a></strong>: Following the initial meeting of some DEI Team members with the GNOME community at <a href="https://fedoraproject.org/wiki/GNOME_Asia_2023" target="_blank" rel="noreferrer noopener">GNOME Asia 2023</a>, we wanted to continue collaboration with the GNOME D&amp;I team. Jona Azizaj and Justin W. Flory continue to represent the Fedora community there upstream and provide guidance based on past experiences with the Fedora DEI Team.</li> <li><strong><a href="https://gitlab.com/fedora/dei/home/-/issues/33" target="_blank" rel="noreferrer noopener">Marketing Team collaboration</a></strong>: Following up on a request from Marketing Team member Daimar Stein, the DEI Team is working together with the Marketing Team to provide more perspectives and ideas to messaging campaigns. Since the issue was opened, we are working on an outreach timeline for Fedora Week of Diversity and collaborated on a post for World Autism Acceptance/Awareness Day.</li></ul> <p>Stay tuned for the full 2024 Q1 report in an upcoming article. In reflection, the end of 2023 was a busy ending to a year that saw the comeback of the DEI Team after a dormant period. As we continue building up our capacity and focusing in our <a href="https://docs.fedoraproject.org/en-US/dei/#vision" target="_blank" rel="noreferrer noopener">team vision and mission</a>, we are also slowly growing our team and exploring new ways to not just recognize, but also celebrate the unique diversity that makes up our global Fedora contributor community.</p> <p><strong>Want to get involved?</strong> Join the DEI Team <a href="https://matrix.to/#/#dei:fedoraproject.org" target="_blank" rel="noreferrer noopener">Matrix chat room</a> (<code>#dei:fedoraproject.org</code>) and follow the <a href="https://discussion.fedoraproject.org/tag/dei-team" target="_blank" rel="noreferrer noopener">Fedora Discussion tag</a>. We meet twice monthly. Our next meeting can be found <a href="https://calendar.fedoraproject.org/diversity-team/" target="_blank" rel="noreferrer noopener">on the Fedora Calendar</a>.</p><p>The post <a href="https://communityblog.fedoraproject.org/fedora-dei-team-2023-q4/">Fedora DEI Team 2023 Q4: Appreciation Week and new members</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-11T08:00:00+00:00</dc:date></item><item rdf:about="tag:status.fedoraproject.org,2024-04-10:/2024-04-10-datacenter-network.html"> <title>Fedora Infrastructure Status: Network outage in datacenter</title> <link>https://status.fedoraproject.org/2024-04-10-datacenter-network.html</link> <content:encoded><p>One of our datacenters primary network link is down.A secondary link is up, but some providers are stilltrying to route over the down link, resulting inconnectivity problems.</p><p>Affected fedora resources include:</p><ul><li>pagure.io</li><li>download-cc-rdu01</li></ul><p>The provider is looking for the outage cause and networkingis working on …</p></content:encoded> <dc:date>2024-04-10T18:00:00+00:00</dc:date></item><item rdf:about="https://fedoramagazine.org/?p=40083"> <title>Fedora Magazine: Automation through Accessibility</title> <link>https://fedoramagazine.org/automation-through-accessibility/</link> <content:encoded><p>In this article you will see how we are using Accessibility as an automation tool to test desktop applications just like a real user would using keyboard key presses and mouse clicks.</p> <p>Although this topic and all of its parts can be talked about for hours to exhaust everything, I will attempt to describe how we are dealing with automation testing in a more digestible form.</p> <span id="more-40083"></span> <p>For those interested there is a link to a full technical solution at the end of this post, with all of our tools and how to use them. We also provide our full GNOME Terminal testing suite for anyone to try.</p> <p>Let us start wit the very core of our ability. Accessibility.</p> <div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained"><h2 class="wp-block-heading">What is Accessibility</h2> <p>Accessibility (<a href="https://en.wikipedia.org/wiki/Assistive_Technology_Service_Provider_Interface" target="_blank" rel="noreferrer noopener">AT-SPI</a>) in software development aims to make software products available to people of all abilities. While being used for various tools present throughout many distributions, it can be used for other purposes.</p> <p>We are using Accessibility through Python.</p> <p>Specifically we utilize Python module GObject introspection that holds Python bindings and support for GTK toolkit and GNOME applications, namely the Atspi module.</p> <p>While Atspi is already providing useful functions, in general this is not enough, we need quite a few more tools to do our job effectively.</p> <p>With that in mind lets go over our automation stack.</p></div></div> <h2 class="wp-block-heading">Automation stack</h2> <p>We do not have a single project that we could utilize. No such project that would fulfill all of our criteria exists, to our knowledge.</p> <p>Therefore, we are using multiple open source projects together to achieve our goal of testing desktop applications. We are maintainers and contributors to most of the following projects.</p> <ul><li>The API – <em>dogtail</em></li> <li>Usage on Wayland – <em>gnome-ponytail-daemon</em></li> <li>The project template – <em>behave</em></li> <li>Gathering results – <em>behave-html-pretty-formatter</em></li> <li>Library of tools – <em>qecore</em></li></ul> <div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained"><h3 class="wp-block-heading">The API – dogtail</h3> <p><em>dogtail</em> is a GUI test tool and automation framework written in Python. It is an extension and wrapper around Atspi and pyatspi2 python libraries.</p> <p>Atspi provides almost everything we need. The <em>dogtail</em> framework, however, is more user friendly in matters of usage.</p> <p><em>dogtail</em> is how we obtain positions and sizes of various widgets. It also provides functions to press single keyboard keys, do key combinations, typing of text, and mouse button clicking.</p></div></div> <div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained"><h3 class="wp-block-heading">Usage on Wayland</h3> <p>Another piece of the stack is the <em>gnome-ponytail-daemon</em> project.</p> <p>This is a helper daemon intended for <em>dogtail</em> on Wayland. Wayland does not expose desktop coordinates so <em>gnome-ponytail-daemon</em> uses remote-desktop and screen-cast APIs in order to work around that. </p> <p>Working with <em>gnome-ponytail-daemon</em> is not trivial. Fortunately, most of what we need from it is hidden behind <em>dogtail</em> which uses <em>gnome-ponytail-daemon</em> functions when needed. This enables seamless work without the need to change API calls.</p> <p>Let us continue to the structure of our automation code.</p></div></div> <div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained"><h3 class="wp-block-heading">The project template – behave</h3> <p><em>behave</em> provides a way to connect natural language, which serves as our step by step suite definition, to an implementation in Python. To illustrate a more specific example, here are <em>behave</em>‘s feature files that contain natural language…</p> <pre class="wp-block-preformatted">@showing_off_behaveFeature: Showing off behave Scenario: Run a simple test Given we have behave installed When we implement 5 tests Then behave will test them for us!</pre></div></div> <p>… which is implemented in Python as you can see below…</p> <pre class="wp-block-preformatted">from &lt;mark class="has-inline-color has-black-color" style="background-color:rgba(0, 0, 0, 0)"&gt;behave&lt;/mark&gt; import given, when, then, step @given('we have behave installed')def step_impl(context): pass @when('we implement {number:d} tests')def step_impl(context, number): assert number &gt; 1 or number == 0 context.tests_count = number @then('behave will test them for us!')def step_impl(context): assert context.failed is False assert context.tests_count &gt;= 0</pre> <p></p> <p>We also use <em>behave</em>‘s file structure as a project template for our testing suites. Therefore, our suites are started by <em>behave</em> in all of our cases.</p> <p>Starting a single test:</p> <pre class="wp-block-preformatted">$ behave -kt showing_off_behave</pre> <p>There is more that <em>behave</em> does for us but that is not relevant here.</p> <p>Lets explore how we gather the results of our testing.</p> <div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained"><h3 class="wp-block-heading">Gathering result – behave-html-pretty-formatter</h3> <p><em>behave</em> provides results, after execution, in user specified format. There are a lot of built-in formats but none of them are useful for us. We are testing GUI applications after all, so we need a lot more than what <em>behave</em> provides.</p> <p>While <em>behave</em>‘s formats are not useful for us, it does provides us with a way to add a new one as a module.</p> <p>We wrote our own formatter for <em>behave</em> called <em>behave-html-pretty-formatter</em>. This formatter returns the output as HTML which we can direct to a file. We have functions specified in our module that enable us to embed data into the HTML file as links, strings, screenshots and videos.</p> <p>The following is an example of starting a test, specifying what the output format will be, and what file to output the data to.</p> <pre class="wp-block-preformatted">$ behave -kt &lt;test&gt; -f html-pretty -o test.html</pre></div></div> <h3 class="wp-block-heading">Library of tools – qecore</h3> <p>With the tools above we have a way to implement our test, have the steps written in natural language, have them executed, and obtain the output of this execution in an HTML file for review. In spite of having all of that, we still need more, much more.</p> <p>For that reason we have a library of tools that is present in all of our automation suites. It provides everything else we might need in our solution. When we need a new feature, we will add it to this project.</p> <p>To list a few examples of what <em>qecore</em> is used for:</p> <ul><li>System configuration.</li> <li>Video recording.</li> <li>Data gathering.</li> <li>Debugging on error.</li> <li>Image matching.</li></ul> <h3 class="wp-block-heading">Summary of parts</h3> <ul><li> <strong><em>qecore</em></strong> will start a session and execute <em>behave</em>.<ul><li><strong><em>behave</em></strong> starts executing its parts.<ul><li><strong><em>qecore</em></strong> initiates and executes commons functions.<ul><li>Test will execute.<ul><li>Automation testing via <strong><em>dogtail</em></strong> /<strong><em>ponytail</em></strong>.</li></ul></li> <li>Test finishes.</li></ul></li> <li><strong><em>qecore</em></strong> gathers all data and lets <em>behave</em> know how to include them in our file.</li></ul></li> <li><strong><em>behave</em></strong> finishes its parts and provides results in HTML format.</li></ul></li> <li> <strong><em>qecore</em></strong> may or may not terminate the session based on user setup.</li></ul> <p>Starting the entire solution for a single test:</p> <pre class="wp-block-preformatted">$ qecore-headless “behave -kt &lt;test&gt; -f html-pretty -o test.html”</pre> <p>The “headless” in the name of the script is historical, now it serves as a session configuration tool.</p> <h2 class="wp-block-heading">Examples</h2> <ul><li>Click on System menu – <a href="https://modehnal.github.io/data/click_on_system_menu.webm" target="_blank" rel="noreferrer noopener">Video of the execution</a></li></ul> <pre class="wp-block-preformatted">#!/usr/bin/python3from dogtail.tree import rootfrom time import sleep # Load application root to variable.shell = root.application("gnome-shell") # Search the application tree for objects.system_menu = shell.child("System", "menu")# Click it.system_menu.click()</pre> <ul><li>Open Terminal form Overview – <a href="https://modehnal.github.io/data/open_terminal_from_overview.webm" target="_blank" rel="noreferrer noopener">Video of the execution</a></li></ul> <pre class="wp-block-preformatted">#!/usr/bin/python3from dogtail.rawinput import typeText, pressKeyfrom time import sleep # Start the application.# Open overview.pressKey("Super")# Give overview a little time to show.sleep(1) # Search application.typeText("Terminal")# Confirm by Enter.pressKey("Enter")</pre> <ul><li>Scrolling the terminal – <a href="https://modehnal.github.io/data/scrolling_the_terminal.webm" target="_blank" rel="noreferrer noopener">Video of the execution</a></li></ul> <pre class="wp-block-preformatted">#!/usr/bin/python3from dogtail.tree import rootfrom dogtail.rawinput import typeText, pressKeyfrom time import sleep # Start the application.# Open overview.pressKey("Super")# Give overview a little time to show.sleep(1) # Search application.typeText("Terminal")# Confirm by Enter.pressKey("Enter") typeText("seq 100")pressKey("Enter") scroll_bar = terminal.findChild( lambda x: x.roleName == "scroll bar")s_min = int(scroll_bar.minValue)s_max = int(scroll_bar.maxValue) for i in range(s_max, s_min, -1): scroll_bar.value = i sleep(0.05) for i in range(s_min,s_max): scroll_bar.value = i sleep(0.05)</pre> <ul><li>Start Terminal and execute a command in New Tab – <a href="https://modehnal.github.io/data/terminal_open_new_tab_execute_command.webm" target="_blank" rel="noreferrer noopener">Video of the execution</a></li></ul> <pre class="wp-block-preformatted">#!/usr/bin/python3from dogtail.tree import rootfrom dogtail.rawinput import typeText, pressKeyfrom time import sleep # First open the application.pressKey("Super") # Open overview.sleep(1) # Give overview a little time to show. # Search application.typeText("Terminal")# Confirm by Enter.pressKey("Enter") # Load application root to variable.app = root.application("gnome-terminal-server") # Search the application tree for objects.terminal = app.child("Terminal", "terminal")# Right click in the terminal.terminal.click(3)# Give menu some time to show.sleep(1) # Find the item Show Menubar that is showingshow_menubar = app.findChild( lambda x: x.name == "Show Menubar" and x.roleName == "check menu item" and x.showing)# Click it if the option is not checked.if not show_menubar.checked: show_menubar.click()else: # Close the menu if option is checked. pressKey("Esc") sleep(1) app.child("File", "menu").click()app.child("New Tab", "menu").click()app.findChild(lambda x: "1." in x.name).click()sleep(1) # Execute the command.typeText("echo Hello World")pressKey("Enter")</pre> <ul><li>Start a Calculator and do a simple calculation – <a href="https://modehnal.github.io/data/start_calculator_do_a_calculation.webm" target="_blank" rel="noreferrer noopener">Video of the execution</a></li></ul> <pre class="wp-block-preformatted">#!/usr/bin/python3from dogtail.tree import rootfrom time import sleepimport dogtail.rawinput # Load application root to variable.shell = root.application("gnome-shell") # Search the application tree for objects.shell.child("Activities", "label").click()sleep(2) # Give overview a little time to show. shell.child("Show Apps", "toggle button").click()sleep(2) shell.child("Calculator", "label").click()sleep(2) # Load the Calculator Atspi object to a variable.calculator = root.application("gnome-calculator") # For calculator we have to account for shadows.def _update_coords(coords): return (coords[0] + 40, coords[1] + 40)dogtail.rawinput.update_coords = _update_coords# Or you can disable box-shadow for gtk4 css. # Simple calculation.calculator.child("3").click()calculator.child("+").click()calculator.child("5").click()calculator.child("=").click() # Simple check.assert calculator.child("3+5").showingassert calculator.child("8").showing</pre> <h2 class="wp-block-heading">Examples of an automation suite output files</h2> <ul><li>Passed test in GNOME Terminal Suite</li></ul> &lt;figure class="wp-block-image size-full wp-lightbox-container" data-wp-context="{"uploadedSrc":"https:\/\/fedoramagazine.org\/wp-content\/uploads\/2024\/04\/test_example.png","figureClassNames":"wp-block-image size-full","figureStyles":null,"imgClassNames":"wp-image-40105","imgStyles":null,"targetWidth":1917,"targetHeight":535,"scaleAttr":false,"ariaLabel":"Enlarge image","alt":""}" data-wp-interactive="core/image"&gt;<img width="1917" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/test_example.png" class="wp-image-40105" height="535" /><button type="button" class="lightbox-trigger"> <svg height="12" width="12" xmlns="http://www.w3.org/2000/svg" fill="none"> <path d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" fill="#fff"> </path></svg> </button>&lt;/figure&gt; <ul><li>Passed test in GNOME Terminal Suite in High Contrast.</li></ul> <p>We have teammates with visual impairment. While designing the output format we thought about a button that would remove all color as a core feature.</p> &lt;figure class="wp-block-image size-full wp-lightbox-container" data-wp-context="{"uploadedSrc":"https:\/\/fedoramagazine.org\/wp-content\/uploads\/2024\/04\/test_example_high_contrast.png","figureClassNames":"wp-block-image size-full","figureStyles":null,"imgClassNames":"wp-image-40106","imgStyles":null,"targetWidth":1920,"targetHeight":637,"scaleAttr":false,"ariaLabel":"Enlarge image","alt":""}" data-wp-interactive="core/image"&gt;<img width="1920" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/test_example_high_contrast.png" class="wp-image-40106" height="637" /><button type="button" class="lightbox-trigger"> <svg height="12" width="12" xmlns="http://www.w3.org/2000/svg" fill="none"> <path d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" fill="#fff"> </path></svg> </button>&lt;/figure&gt; <ul><li>Failed test in a Zenity Testing Suite</li></ul> <p>Our automation solution will provide as much data as possible after any error.</p> <p>You will notice the amount of data present in a failed page. This page has everything a developer will need to debug a problem.</p> <ul><li>Set of steps taken to reproduce the issue.</li> <li>Screenshot at the moment of the failure.</li> <li>Video of the reproducer.</li> <li>Journal logs.</li> <li>Full backtrace from coredumps – all relevant debuginfo/debugsource packages are installed.</li> <li>Status shows what version of an application is tested.</li> <li>We also have debug logs for our own tools to verify we did not introduce the issue.</li></ul> &lt;figure class="wp-block-image size-full wp-lightbox-container" data-wp-context="{"uploadedSrc":"https:\/\/fedoramagazine.org\/wp-content\/uploads\/2024\/04\/zenity_backtrace_example.png","figureClassNames":"wp-block-image size-full","figureStyles":null,"imgClassNames":"wp-image-40107","imgStyles":null,"targetWidth":1917,"targetHeight":507,"scaleAttr":false,"ariaLabel":"Enlarge image","alt":""}" data-wp-interactive="core/image"&gt;<img width="1917" alt="" src="https://fedoramagazine.org/wp-content/uploads/2024/04/zenity_backtrace_example.png" class="wp-image-40107" height="507" /><button type="button" class="lightbox-trigger"> <svg height="12" width="12" xmlns="http://www.w3.org/2000/svg" fill="none"> <path d="M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z" fill="#fff"> </path></svg> </button>&lt;/figure&gt; <h2 class="wp-block-heading">Advantages of our solution</h2> <ul><li>It does not matter what theme is in use.</li> <li>It does not matter what font is in displayed on the screen.</li> <li>It does not matter where on the screen the application is located.</li> <li>In GNOME Control Center we can enable Zoom, Large Text or High Contrast and the automation will still work.</li> <li>If the application is in the Atspi tree in can be tested:<ul><li>Evolution</li> <li>Firefox</li> <li>GNOME Control Center</li> <li>GNOME Shell</li> <li>GNOME Software</li></ul></li></ul> <h2 class="wp-block-heading">Disadvantages of our solution</h2> <ul><li>Accessibility is primarily not meant to be used for automation.</li> <li>Most applications we test have the Accessibility layer in imperfect/incomplete state.<ul><li>Wrong coordinates.</li> <li>Incorrect or missing names, roles or attributes.</li> <li>Widgets for scroll bars have their limit set to 0 and cannot be changed even if a user can scroll in the GUI with no issues.</li></ul></li> <li>While most of the issues we find have relatively simple workarounds they still exist and have to be dealt with.</li> <li>Problems with Accessibility in context of an automation are not a priority and might not get the attention they would need.</li></ul> <div class="wp-block-group"><div class="wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained"><h2 class="wp-block-heading">Full technical solution</h2> <p>For those interested in more details I am providing full technical solution for automation testing of GNOME Terminal on Fedora 38 with Wayland.</p> <p>The article will guide you to fully functional Automation Testing solution.</p> <p><a href="https://modehnal.github.io/" target="_blank" rel="noreferrer noopener">https://modehnal.github.io/</a></p></div></div></content:encoded> <dc:date>2024-04-10T08:00:00+00:00</dc:date></item><item rdf:about="https://communityblog.fedoraproject.org/?p=13505"> <title>Fedora Community Blog: Fedora Strategy 2028: April 2024 Update</title> <link>https://communityblog.fedoraproject.org/strategy-2028-april-2024-update/</link> <content:encoded><p><em><strong>from Fedora Project Leader Matthew Miller, on behalf of the Fedora Council</strong></em></p> <p><em>First, a personal note! As you may have seen, I was out sick with Covid for a month after getting home from our annual Council face-to-face meeting. It’s not been fun — some respiratory symptoms, but primarily, overwhelming fatigue. Somewhat ironically, the timing suggests that I managed to avoid catching anything at FOSDEM itself (where I wore a mask most of the time), or at the Council meeting, but rather on the plane or in the airport on the way back. Although emergency measures have been lifted, there really is still a pandemic going on. Be careful, everyone, especially when traveling! In any case, I’m back to myself now, and am excited for Fedora’s next big steps.</em></p> <h1 class="wp-block-heading">The Story so Far</h1> <p>So! I’ve been talking about “Strategy 2028” for a while — we started this effort seriously about a year ago. If you’re just joining in, or want a refresher, <a href="https://discussion.fedoraproject.org/t/fedora-strategy-2028-a-topic-index-for-our-planning-process/46733">Fedora Strategy 2028: a topic index for our planning process</a> is a great place to start. I won’t rehash all of that here.</p> <p>The important thing is: 2023 was <em>kind of a hard year</em>, and although we made some progress, we lost momentum. The Council hackfest helped get things back on track, and we’re moving forward now. We’re not making any fundamental changes, but we are restructuring how we present things — and we’re moving on from theory to practical work.</p> <span id="more-13505"></span> <h1 class="wp-block-heading">A New Presentation</h1> <p>Over the last year, we got feedback from many people who felt that the organization into <em>Themes </em>and <em>Focus Areas </em>was overwhelming and confusing. It felt really big, maybe too much, and hard to know where one might fit in.</p> <p>After some discussion, we decided that we could better present our various objectives as they align with something we’re all already very familiar with: Fedora’s “four foundations”: <strong>Freedom</strong>, <strong>Friends</strong>, <strong>Features</strong>, and <strong>First</strong>. The objectives we’ve talked about over the past year aren’t going away, but this gives us an easier way to organize and prioritize them over the next few years.</p> <h1 class="wp-block-heading">What Else?</h1> <p>Even with a big and ambitious plan, we left some important ideas behind. For example, we want to better tell our Fedora stories (both inside and outside the project), and we want work to improve distribution security. We’re not immediately adding planned effort on these, but our new framing around the Foundations gives us more room to add those things as needed.</p> <p>Our project has amazing, passionate people who have done amazing things for Fedora and for the world of community-built, free and open source software in general. We should do more to celebrate them, to give everyone the recognition they deserve. We should show new and potential contributors the incredible things we’ve done and the exciting things we’re doing — and what it means to be part of our community.</p> <p>The recent xz exploit relied on long-term, persistent social engineering within an open source project, along with a very sophisticated technical attack. A long discussion on the <a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/YWMNOEJ34Q7QLBWQAB5TM6A2SVJFU4RV/">devel mailing list</a> shows that we have many ideas for how we can make Fedora more resilient against such attacks as a project, and Fedora Linux safer as an operating system. Initiatives to work on these improvements may end up under a different umbrella, but will certainly have some interconnection.</p> <p>As we go through the next five years, don’t be surprised to see us add Community Initiatives focused on these things — and others, as they emerge.</p> <h1 class="wp-block-heading">And then, there’s AI</h1> <p>We’ve all heard a lot about various “large language model” chatbots, and about image and even video creation. There is obviously a lot of hype around AI — and inevitably, over-the-top nonsense. We’re not<em> really </em> “just five years away” from actual generalized Artificial Intelligence. This <em>isn’t</em> the start of Skynet from The Terminator movies. Human creativity <em>isn’t</em> being replaced, and I don’t think all programmers will end up as “prompt engineers”.</p> <p>However, there <em>is</em> something real here.</p> <p>Advances in accelerated hardware and machine-learning software have unlocked possibilities which were imagined last century, but which were not practical at the time. When the dust settles around the hyperbole, I believe we’ll still be left with something significant, powerful.</p> <p>In addition to the big showy LLM-based tools for chat and code generation, these advances have brought big jumps for more tailored tasks: for translation, file search, home automation, and especially for accessibility (already a key part of our strategy). For example, open source speech synthesis has long lagged behind proprietary options. Now, what we have in Fedora is not even close to the realism, nuance, and flexibility of AI-generated speech.</p> <p>Right now, most of all this is proprietary. It’s corporate-owned closed models trained with hidden data, largely running on hardware without open source drivers. If we ignore this, we’re going to be left behind — not just Fedora, but free and open source software entirely. On the other hand, we can take a leadership position, and build a future where AI belongs to all of us.</p> <p>The Guiding Star for Strategy 2028 is about growing our contributor base. We can make <strong>Fedora Linux the best community platform for AI</strong>, and in doing so, open a new frontier of contribution and community potential.</p> <p>This won’t be easy. We have a lot of basic work on platform fundamentals. That’s drivers and tooling, packages and containers, and even new ways of distributing Fedora software. We also need to improve developer experience — for example, it’d be nice to have Podman Desktop as part of Fedora, with easy paths to getting started.</p> <p>We can use AI/ML as part of <em>making</em> the Fedora Linux OS. New tools could help with package automation and bug triage. They could note anomalies in test results and logs, maybe even help identify potential security issues. We can also create infrastructure-level features for our users. For example, package update descriptions aren’t usually very meaningful. We could automatically generate concise summaries of what’s new in each system update — not just for each package, but highlighting what’s important in the whole set, including upstream change information as well.</p> <p>At the same time, we need to work with the rest of the free and open source world to create labels for AI technology which aligns with our values. We need polices on what we allow, and on what we encourage. We may even need to fight for legal frameworks friendly to community-built software.</p> <p>Finally, of course, we can provide models in the OS. This includes accessibility tooling, which can benefit everyone: imagine an all-local voice assistant that doesn’t send your conversations to some big datacenter or try to sell you things while simultaneously selling your personal data. We could also include tools that make it easier to find help, features to simplify system administration tasks, and interfaces to better organize your documents and media — all within <em>your</em> control, all running on a free and open source software stack.</p> <p>We’re just getting started here (with, for example, Pytorch <a href="https://fedoraproject.org/wiki/Changes/PyTorchRelease">coming in Fedora Linux 40 1</a>, CPU-only — for now). There will be more exciting things coming soon.</p> <h1 class="wp-block-heading">Next Steps</h1> <p>The next post will be the high-level view of Strategy 2028, updated from this new perspective.</p> <p>The Council’s next immediate step is to identify Executive Sponsors and leaders for each Focus Area under the broad umbrellas of our Four Foundations. Then, we’ll plan and schedule concrete outputs and practical activities in each area. For larger efforts, we expect to launch <a href="https://docs.fedoraproject.org/en-US/project/initiatives/">Community Initiatives</a>, but much of the work will be organized as smaller projects under each focus area banner. Expect more announcements soon as we build this out!</p><p>The post <a href="https://communityblog.fedoraproject.org/strategy-2028-april-2024-update/">Fedora Strategy 2028: April 2024 Update</a> appeared first on <a href="https://communityblog.fedoraproject.org">Fedora Community Blog</a>.</p></content:encoded> <dc:date>2024-04-10T08:00:00+00:00</dc:date></item><item rdf:about="tag:github.com,2008:Repository/123299/8.1.0"> <title>Bodhi: 8.1.0</title> <link>https://github.com/fedora-infra/bodhi/releases/tag/8.1.0</link> <content:encoded><p>Released on 2024-04-09.<br />This is a feature release that adds options for running createrepo_c.</p><h2>Features</h2><ul><li>Bodhi can now set a timeout on postgresql database queries (default to 30 sec) (<a href="https://github.com/fedora-infra/bodhi/pull/5593" class="issue-link js-issue-link">#5593</a>).</li><li>The createrepo_c config file now can accept enabling/disabling sqlite metadata generation and using --compatibility flag (<a href="https://github.com/fedora-infra/bodhi/pull/5617" class="issue-link js-issue-link">#5617</a>).</li><li>Builds submission can now be restricted to only specified sources (<a href="https://github.com/fedora-infra/bodhi/issues/5556" class="issue-link js-issue-link">#5556</a>).</li><li>A new <code>/list_releases/</code> GET endpoint is available to allow retrieving JSON data through ajax calls. (<a href="https://github.com/fedora-infra/bodhi/issues/5587" class="issue-link js-issue-link">#5587</a>).</li></ul><h2>Bug fixes</h2><ul><li>Use urljoin for update URLs construction (<a href="https://github.com/fedora-infra/bodhi/issues/5566" class="issue-link js-issue-link">#5566</a>`).</li><li>DRPMs can now be disabled per Release in createrepo_c config file (<a href="https://github.com/fedora-infra/bodhi/issues/5616" class="issue-link js-issue-link">#5616</a>).</li></ul><h2>Development improvements</h2><ul><li>The Vagrant development environment is entirely removed in favor of BCD, and bodhi-shell is fixed in BCD. (<a href="https://github.com/fedora-infra/bodhi/pull/5600" class="issue-link js-issue-link">#5600</a>).</li></ul><h2>Contributors</h2><p>The following developers contributed to this release of Bodhi:</p><ul><li>Aurélien Bompard</li><li>Adam Williamson</li><li>Mattia Verga</li></ul></content:encoded> <dc:date>2024-04-09T12:27:28+00:00</dc:date></item><item rdf:about="http://sgallagh.wordpress.com/?p=2100"> <title>Stephen Gallagher: One Week With KDE Plasma Workspaces 6 on Fedora 40 Beta (Vol. 2)</title> <link>https://sgallagh.wordpress.com/2024/04/08/one-week-with-kde-plasma-workspaces-6-on-fedora-40-beta-vol-2/</link> <content:encoded><h2 class="wp-block-heading">Checking In</h2> <p>It’s been a few days since my <a href="https://sgallagh.wordpress.com/2024/04/03/one-week-with-kde-plasma-workspaces-6-on-fedora-40-beta-vol-1/">first entry</a> in this series. For the most part, things have been going quite smoothly. I have to say, I am liking KDE Plasma Workspaces 6 much better than previous releases (which I dabbled with but admittedly did not spend a significant amount of time using). The majority of what I want to do here Just Works. This should probably not come as a surprise to me, but I’ve been burned before when jumping desktops.</p> <p>I suppose that should really be my first distinct note here: the transition from GNOME Desktop to KDE Plasma Workspaces has been minimally painful. No matter what, there will always be some degree of muscle memory that needs to be relearned when changing working environments. It’s as true going from GNOME to KDE as it is from Windows to Mac, Mac to ChromeOS and any other major shift. That said, the Fedora <a href="https://fedoraproject.org/wiki/Changes/FedoraPlasmaWorkstation">Change</a> that prompted this investigation is specifically about the possibility of changing the desktop environment of Fedora Workstation over to using KDE Plasma Workspaces and away from GNOME. As such, I will be keeping in mind some of the larger differences that users would face in such a transition.</p> <h2 class="wp-block-heading">Getting fully hooked up</h2> <p>The first few days of this experience, I spent all of my time directly at my laptop, rather than at my usual monitor-and-keyboard setup. This was because I didn’t want to taint my initial experience with potential hardware-specific headaches. My main setup involves a very large 21:9 aspect monitor, an HDMI surround sound receiver and a USB stereo/mic headset connected via a temperamental USB 3.2/Thunderbolt hub and the cheapest USB A/B switch imaginable (I share these peripherals with an overpowered gaming PC). So when I put aside my usual daily driver and plugged my Thinkpad into the USB-C hub, I was prepared for the worst. At the best of times, Fedora has been… <em>touchy</em> about working with these devices.</p> <p>Let’s start with the good bits: When I first connected the laptop to my docking station, I was immediately greeted by an on-screen display asking me how I wanted to handle the new monitor. Rather than just making a guess between cloning or spanning the desktop, it gave me an easy and visual prompt to do so. Unfortunately, I don’t have a screenshot of this, as after the first time it seems that the system “remembers” the devices and puts them back the way I had them. This is absolutely desirable for the user, but as a reviewer it makes it harder to show it off. (<strong>EDIT</strong>: After initial publication, I was informed of the meta-P shortcut which allowed me to grab this screenshot)</p> &lt;figure class="wp-block-image size-large"&gt;<a href="https://sgallagh.files.wordpress.com/2024/04/monitors.png"><img width="1024" alt="" src="https://sgallagh.files.wordpress.com/2024/04/monitors.png?w=1024" class="wp-image-2114" height="428" /></a>&lt;/figure&gt; <p>Something else that I liked about the multi-monitor support was the way that the virtual desktop space on the taskbar automatically expanded to include the contents from both screens. It’s a simple thing, but I found that it made it really easy to tell at a glance which desktop I had particular applications running on.</p> <p>All in all, I want to be clear here: the majority of my experience with KDE Plasma Workspaces has been absolutely fine. So many things work the same (or close enough) to how they work in GNOME that the transition has actually been much easier than I expected. the biggest workflow changes I’ve encountered are related to keyboard shortcuts, but I’m not going to belabor that, having discussed it in the first entry. The one additional keyboard-shortcut complaint I will make is this: using the “meta” key and typing an application name has a strange behavior that gets in my way. It <em>almost</em> behaves identically to GNOME; I tap “meta” and start typing and then hit enter to proceed. But the issue I have with KDE is this: I’m a fast typist and the KDE prompt doesn’t accept <code>&lt;enter&gt;</code> until the visual effect of opening the menu completes. This baffles me, as it accepts all of the other keys. So my muscle memory to launch a terminal by quickly tapping “meta”, typing “term” and hitting enter doesn’t actually launch the terminal. It leaves me at the menu with konsole sitting there. When I hit enter after the animation completes, it works fine. So while the behavior isn’t <em>wrong</em>, per se, it’s frustrating. The fact that it accepts the other characters makes me think this was a deliberate choice that I don’t understand.</p> <p>There have been a few other issues, mostly around hardware support. I want to be clear: I’m fully aware that hardware is <em>hard</em>. One issue in particular that has gotten in the way is support for USB and HDMI sound devices in KDE Plasma. I don’t know if it’s specifically my esoteric hardware or a more general problem, but it has been very hard to get KDE to use the correct inputs and outputs. In the case of the HDMI audio receiver, I still haven’t been able to get KDE to present it as an output option in the control panel. It connects to the receiver and treats it as a very basic 720p video output device, but it just won’t recognize it as an audio output device. My USB stereo headset with mic has also been more headache than headset: after much trial and error, I’ve managed to identify the right output to send stereo output to it, but no matter what I have fiddled with, it does not recognize the microphone.</p> <p>More issues on the hardware front are related to having two webcam devices available. KDE properly detects both the built-in camera on the laptop as well as the external webcam I have clipped to the top of my main monitor, but it seems to have difficulty switching between them. I’m not yet 100% sure how much of this is a KDE problem and how much a Firefox problem, but it is frustrating. Sometimes I’ll select my external webcam and it will still be taking input from the built-in camera. Also, it seems to always show two entries for both devices. I need to do more digging here, but I anticipate that I’ll be filing a bug report once I gather enough data.</p> <h2 class="wp-block-heading">Odds and Ends</h2> <p>I have mixed feelings about KDE’s clipboard applet in the toolbar. On the one hand, I can certainly see the convenience of digging into the clipboard history, particularly if you accidentally drag-select something and replace the clipboard copy you intended to keep. On the other hand, as a heavy user of <a href="https://bitwarden.com/">Bitwarden</a> who regularly copies passwords<sup class="fn"><a href="https://sgallagh.wordpress.com/category/fedora/feed/#65b383f5-dfb9-43d1-aa18-042bedae716c" id="65b383f5-dfb9-43d1-aa18-042bedae716c-link">1</a></sup> out of the wallet and into other applications, the fact that all of the clipboard contents are easily viewable in plaintext to anyone walking by if I forget to lock my screen for a few seconds is quite alarming. I’m pretty sure I’ll either have to disable this applet or build a habit of clearing it any time I copy a password. Probably the former, as I don’t like the fact that I have to call up and make the plaintext visible first in order to delete it without clearing the entire history anyway.</p> <h2 class="wp-block-heading">Conclusion</h2> <p>This will probably seem odd after a post that mostly contained complaints and nitpicks, but I want to reiterate: my experience over the last several days has actually been quite good. When dealing with a computer, I consider “it was boring” to be the <em>highest of praise</em>. Using KDE has not been a life-altering experience. It has been a stable, comfortable environment in which to get work done. Have I experienced some issues? Absolutely. None of them are deal-breakers, though the audio issues are fairly annoying. My time in the Fedora Project has shown me that hardware issues inevitably get fixed once they are noticed, so I’m not overly worried.</p> <p>As for me? I’m going to stick around in KDE for a while and see how things play out. If you’re reading this and you’re curious, I’ll happily direct you to the <a href="https://fedoraproject.org/spins/kde/download">Fedora KDE Spin</a> for the Live ISO or the <a href="https://fedoraproject.org/atomic-desktops/kinoite/download">Kinoite installer</a> if, like me, you enjoy an atomic update environment. Make sure to select “Show Beta downloads” to get Plasma 6!</p> <ol class="wp-block-footnotes"><li id="65b383f5-dfb9-43d1-aa18-042bedae716c">I generate high-entropy, unique random passwords for <em>everything</em>. Don’t you? <a href="https://sgallagh.wordpress.com/category/fedora/feed/#65b383f5-dfb9-43d1-aa18-042bedae716c-link"><img src="https://s0.wp.com/wp-content/mu-plugins/wpcom-smileys/twemoji/2/72x72/21a9.png" style="height: 1em;" class="wp-smiley" alt="↩" />︎</a></li></ol></content:encoded> <dc:date>2024-04-08T20:31:32+00:00</dc:date></item><item rdf:about="https://badges.fedoraproject.org/badge/fedora-42-coreos-test-day"> <title>Fedora Badges: New badge: Fedora 42 CoreOS Test Day !</title> <link>https://badges.fedoraproject.org/badge/fedora-42-coreos-test-day</link> <content:encoded><img src="https://infrastructure.fedoraproject.org/infra/badges/pngs/coreos-test-day-f42.png" alt="Fedora 42 CoreOS Test Day" />You helped solidify the core for the Fedora 42 rebase!</content:encoded> <dc:date>2024-04-08T12:09:42+00:00</dc:date></item><item rdf:about="https://badges.fedoraproject.org/badge/fedora-41-coreos-test-day"> <title>Fedora Badges: New badge: Fedora 41 CoreOS Test Day !</title> <link>https://badges.fedoraproject.org/badge/fedora-41-coreos-test-day</link> <content:encoded><img src="https://infrastructure.fedoraproject.org/infra/badges/pngs/coreos-test-day-f41.png" alt="Fedora 41 CoreOS Test Day" />You helped solidify the core for the Fedora 41 rebase!</content:encoded> <dc:date>2024-04-08T12:07:33+00:00</dc:date></item> </rdf:RDF> If you would like to create a banner that links to this page (i.e. this validation result), do the following:
Download the "valid RSS" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):
If you would like to create a text link instead, here is the URL you can use:
http://www.feedvalidator.org/check.cgi?url=http%3A//fedoraproject.org/people/rss10.xml
