<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rust on Pensées de Michel</title>
    <link>/tags/rust/</link>
    <description>Recent content in Rust on Pensées de Michel</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/rust/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Sandogasa, now for EPEL and CentOS SIG workflows too!</title>
      <link>/posts/2026-04-02-sandogasa-for-epel-and-centos-sigs/</link>
      <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate>
      <guid>/posts/2026-04-02-sandogasa-for-epel-and-centos-sigs/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Caveat lector&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This post discusses tools reluctantly written with AI assistance. If you don&amp;rsquo;t entertain&#xA;using them under any circumstance, and think even reading about them legally compromise&#xA;your ability to reimplement them yourselves, stop reading now&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;This is a follow-up to the &lt;a href=&#34;https://michel-slm.name/posts/2026-03-24-announcing-sandogasa-for-fedora-packaging-workflows/&#34;&gt;original Sandogasa announcement&lt;/a&gt;. Before I ended up &lt;a href=&#34;https://crates.io/crates/fedora-cve-triage&#34;&gt;&lt;code&gt;fedora-cve-triage&lt;/code&gt;&lt;/a&gt; to extract library crates and reuse them in the other Sandogasa tools, I already created two tools for managing CentOS Hyperscale SIG workflows, &lt;a href=&#34;https://crates.io/crates/hs-intake&#34;&gt;&lt;code&gt;hs-intake&lt;/code&gt;&lt;/a&gt; and &lt;a href=&#34;https://crates.io/crates/hs-relmon&#34;&gt;&lt;code&gt;hs-relmon&lt;/code&gt;&lt;/a&gt;. It simply makes sense to also merge them back in and deduplicate functionalities.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Announcing Sandogasa, a set of Rust crates to help with Fedora packaging workflows</title>
      <link>/posts/2026-03-24-announcing-sandogasa-for-fedora-packaging-workflows/</link>
      <pubDate>Tue, 24 Mar 2026 19:06:34 +0000</pubDate>
      <guid>/posts/2026-03-24-announcing-sandogasa-for-fedora-packaging-workflows/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Caveat lector&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;This post discusses tools reluctantly written with AI assistance. If you don&amp;rsquo;t entertain&#xA;using them under any circumstance, and think even reading about them legally compromise&#xA;your ability to reimplement them yourselves, stop reading now&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve spent the past few weeks of having to use LLMs to scratch some long-standing itches that, unfortunately, no one in the community has had the time to solve programmatically.&lt;/p&gt;&#xA;&lt;h2 id=&#34;fedora-cve-triage&#34;&gt;fedora-cve-triage&lt;/h2&gt;&#xA;&lt;p&gt;It started off with &lt;a href=&#34;https://crates.io/crates/fedora-cve-triage&#34;&gt;&lt;code&gt;fedora-cve-triage&lt;/code&gt;&lt;/a&gt;, written to address the issue that a lot of CVE bugs filed against Fedora packages are badly attributed, and there is a lack of automation for handling issues filed against CVEs that have been addressed in a software update but failed to reference said issue.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
