From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 2610C4FC9; Mon, 06 Oct 2025 13:06:47 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 539EE4FAD; Mon, 06 Oct 2025 13:06:44 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from fhigh-b3-smtp.messagingengine.com (fhigh-b3-smtp.messagingengine.com [202.12.124.154]) by atuin.qyliss.net (Postfix) with ESMTPS id 1EF0E4FAC for ; Mon, 06 Oct 2025 13:06:42 +0000 (UTC) Received: from phl-compute-10.internal (phl-compute-10.internal [10.202.2.50]) by mailfhigh.stl.internal (Postfix) with ESMTP id 53CF57A001E; Mon, 6 Oct 2025 09:06:40 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-10.internal (MEProxy); Mon, 06 Oct 2025 09:06:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:subject:subject:to:to; s=fm1; t=1759756000; x=1759842400; bh=Vo65uQ6OsmXtI3HKAJcPaA/SnAGqX9Ip 3obF5AzNTss=; b=PMHZB9w6hStwa8kAPJ9yY5dOx+TJfF6PfVA1RjTEudirLTYw CKaQcysSW4Zwd4Or2bMZ+2IeVs+ZdQRctKVKmV7rlIRkTPpirZaqClT6L5El4f+r 81Zd6ZOHrwn9D8VaJiKi1sk7Uz69Kboa4n4lELsFAO1PZ9N22ZQHVE/PJtSUk+aI OmQhG0lNwcygFLBChVWwzwTvy4xaqT/cRZrvPLHV3AEo9D9aXtT6uVZEh4vNmyJb lM42QHP/qtKHF/oLuObXffRJoSE8pYQWYUfgXZCONwNJS8DlpJlBWOu4S8wR36cG A2TRosl7t8rPVieIiqF5rnKJ49iHcnQtwobd3Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1759756000; x= 1759842400; bh=Vo65uQ6OsmXtI3HKAJcPaA/SnAGqX9Ip3obF5AzNTss=; b=t UsW6wYflTFZuDnAv76hpZLdx6iLp1yRfvbKCzGSiHnMbIjOx9c3+AGOLR7DggAGF aF82t9xM+4QFhkq/m82jC7L/YSPz1u4CpWZ4/gTHV0SAu+oHP9UEipT2OgGpNfHc Bk516vtKKiv1Zsdb+3f5OX2+AjV0Dr2BCe6SIwrxgLJSzDC5MscqyarJp0nGiR6a jJWtZKctYj6keyUe34kbK5vqmxVw+Kfkww+d9vAyVKRMvZ+kGs7TNASxvgWivGKC jU1Ub2TwKx32jkkv5GVAxj8NEEaj8YVdPC1z5p2ZoWCpY8KatitGERQufgWqOjU4 6LC/JSYXzh/7dFnd4DEbw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggdeljeeiudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhvfevufffkfggtgesghdtreertddtjeenucfhrhhomheptehlhihsshgrucftohhs shcuoehhihesrghlhihsshgrrdhisheqnecuggftrfgrthhtvghrnhephfeggfejtdduje effeegudejlefhgeejgeehtddthfeuffejveeghfekgeehleeknecuffhomhgrihhnpeht uhifihgvnhdrrggtrdgrthdpghhithhhuhgsrdgtohhmpdhukhhvlhihrdhorhhgpdgrlh hlqdhshihsthgvmhhsqdhgohdrihhopdhfvgguohhrrghprhhojhgvtghtrdhorhhgnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephhhisegrlh ihshhsrgdrihhspdhnsggprhgtphhtthhopeefpdhmohguvgepshhmthhpohhuthdprhgt phhtthhopeihuhhrvghkrgestgihsggvrhgthhgrohhsrdguvghvpdhrtghpthhtohepug gvmhhiohgsvghnohhurhesghhmrghilhdrtghomhdprhgtphhtthhopeguihhstghushhs sehsphgvtghtrhhumhdqohhsrdhorhhg X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 6 Oct 2025 09:06:38 -0400 (EDT) Received: by rock.qyliss.net (Postfix, from userid 1000) id DBFDC15D1605; Mon, 06 Oct 2025 15:06:27 +0200 (CEST) From: Alyssa Ross To: discuss@spectrum-os.org Subject: This Week in Spectrum, 2025-W40 Date: Mon, 06 Oct 2025 15:06:24 +0200 Message-ID: <87bjmkdvsf.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-ID-Hash: THNV4AOVQESWBEWP25DJY3ZYFPALTGSO X-Message-ID-Hash: THNV4AOVQESWBEWP25DJY3ZYFPALTGSO X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-discuss.spectrum-os.org-0; header-match-discuss.spectrum-os.org-1; header-match-discuss.spectrum-os.org-2; header-match-discuss.spectrum-os.org-3; header-match-discuss.spectrum-os.org-4; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Demi Marie Obenour , Yureka Lilian X-Mailman-Version: 3.3.9 Precedence: list List-Id: General high-level discussion about Spectrum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable It was quite a week. Yureka and I were at XDC from Monday until Wednesday. My talk, "An upstream-first approach to application virtualization", was on Tuesday, and the video is now online[1]. I didn't learn that much at the conference that was directly relevant to Spectrum, but I was interested to learn from a lightning talk that kmscon has been revived and was recently repackaged in Fedora[2]. I'm still getting used to public speaking again, so the talk wasn't as smooth as I'd have liked, but it was okay. After XDC, I stopped by the Systems Meetup Dresden[3] and did a lighting talk. This one went much better, but wasn't recorded, so you'll just have to believe me. While we were away, All Systems Go[4] (AIUI basically the systemd conference) took place in Berlin, and that meant a lot of Linux mobile/desktop people were in town who are not normally. We were able to get together over the following days, and in particular we had some good conversations about what the future of Flatpak/Portals might look like. It's great to be in the room for this sort of thing because it means Spectrum's needs can be considered from the start. The designs being considered would solve our biggest pain points, so I'm optimistic, but there's of course the question of momentum / developer attention to make it happen. Hopefully we can contribute to that. [1]: https://video.tuwien.ac.at/events/xdc/v/Ow9xtIyJeTt?t=3D01h13m49s [2]: https://github.com/Aetf/kmscon/ [3]: https://ukvly.org/ [4]: https://all-systems-go.io/ In between the talks at XDC (and during some of the talks about graphics drivers I had no hope of understanding), I was pleasantly surprised to find myself in a particularly productive state =E2=80=94 it must have been = the conference atmosphere. It didn't make sense to try to work on anything big, so I went through my backlog of small Spectrum improvements. Image rebuild times during development have gone down by a further non-trivial two seconds on a fast laptop, more code has been integrated into the single Meson build system I aspire to, and a few other smaller things. I also managed to completely clear my review queue, although it of course started filling up again immediately after. Demi's patch to automate the lists of files to include in images is finally finished and committed, and her udev changes made progress, but they've been blocked on further review from me, since with so much stuff on I haven't had a chance since leaving XDC. She's also made a bit of progress on system updates using systemd-sysupdate, about which we'll hopefully have more to say soon. Finally, we've been discussing for a couple of days now what to do about a recently introduced build failure on x86_64. I'm already late getting this update out, so I'm not going to go into detail, but basically it's very unclear what the right way to build BPF programs that include kernel UAPI headers is, or if there even is one. The common way of using a distro's linux-headers/libc package is not correct, and likely to lead to either loud compilation failures (as we're currently experiencing) or silent hidden bugs[5]. If we can't find a good solution, we can fall back to copying the definitions we need out of the headers, but I'm hoping it won't come to that. Investigation continues. This has also highlighted the need for pre-push testing on all supported architectures =E2=80=94 the reason this build failure got past me is that it only happens on x86_64, and I was working on aarch64. I'll try to get that addressed. [5]: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraprojec= t.org/thread/FLBBMJ2GTD4SCGTIMDAT6GQDXJMDFGVH/ Hopefully next week will be less busy, and I'll be able to get my head down a bit and do some programming. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEH9wgcxqlHM/ARR3h+dvtSFmyccAFAmjjvtEACgkQ+dvtSFmy ccDKaBAAleFOinOMhgZbPAeeGvXAIXTCgWrj2jbC0dcP3NCwLmaAGmXfVBNEVy9K WugIYeAtKSBmDh2eOQXhLuIC9LRJaEreM0ydDNx79IluVH5SUZBHCRO51XxCKxGs 9qOvRQXEI5hD4wbI6vJmw9nNgyPALAfvBOfokjXpqOiCm3sYBDU59lp21HnKs0ov vWc1ivDvf9UnjAiAG9fO8uRQOqzul+wwEIx6HC3AtHyvP7H5JNHD9uObdNS0k6Tf R1KkwSohk+4SloqCqrL0vCW2Hiub81/l5HavukEzqzaTkLUxtplF+WSCOdtSnXtz mDxe53IFpmEbqPoZeIFn1l8KobmSXPm7cCQQ+Jx90WsXeSoxrSGkNKb/zQIFHWbc qFqNjFhck0zY7H+rOitqqaOqXvmKptHzrJCSgDM9bkGgh7x6se2NwsIoEJBT2ORW yW7zkPe2yTIK9Pc1xCZT6W6YFF0GfG9KzcQPzwoKjU5d5NuONwOdFu+2ubFspjrP kMjc7lWs6IgdtvJGYhabChXyI90/kE2UlTOTLnAcHwPtOdf7cdHlZf7Pge8rJkCr ICiSp5Pi4/cdXMMm1ohqe5GRyVA20gYnP42QiK9Dd38S3XlMu80F3qqcq03yoNX0 xqAJB1T2oDgkXp0U7hcYB/WnCU/jvmSGuigt9LBUv3sHz1cNj3c= =pv1J -----END PGP SIGNATURE----- --=-=-=--