devel June 2026

devel@lists.fedoraproject.org

143 participants
209 discussions

libical 4.0 for rawhide (when?)
by Milan Crha 26 Aug '26

26 Aug '26

Hi, the libical folks released libical 4.0 recently [bug2458837]. I'd like to get it to Fedora rawhide, but it cannot be installed beside the 3.x series (which is for good). Some parts of the API changed, but it's mostly compatible with the 3.x series. I cannot create the compat package, because it's similar with libsoup2->libsoup3 transition, one process cannot link (even indirectly) to both versions of the library, due to clashing API. Again, it's for good, from my point of view. According to `dnf repoquery --whatrequires "libical*-devel" --recursive --srpm --enablerepo=rawhide-source` these are the affected packages: ``` akonadi-calendar-0:26.04.0-1.fc45.src akonadi-search-0:26.04.0-1.fc45.src calendarsupport-0:26.04.0-1.fc45.src elementary-calendar-0:8.0.1-3.fc44.src eventviews-0:26.04.0-1.fc45.src evolution-0:3.60.1-1.fc45.src evolution-data-server-0:3.60.1-1.fc45.src folks-1:0.15.12-1.fc45.src incidenceeditor-0:26.04.0-1.fc45.src kcalutils-0:26.04.0-1.fc45.src kf5-akonadi-calendar-0:23.08.5-3.fc42.src kf5-akonadi-search-0:23.08.5-5.fc44.src kf5-calendarsupport-0:23.08.5-5.fc44.src kf5-eventviews-0:23.08.5-5.fc44.src kf5-incidenceeditor-0:23.08.5-6.fc44.src kf5-kblog-0:20.04.3-15.fc44.src kf5-kcalendarcore-1:5.116.0-5.fc44.src kf5-kcalendarutils-0:23.08.5-5.fc44.src kf5-ktnef-0:23.08.5-6.fc44.src kf5-libkgapi-0:23.08.5-5.fc44.src kf6-kcalendarcore-0:6.25.0-1.fc45.src kitinerary-0:26.04.0-2.fc45.src ktnef-0:26.04.0-1.fc45.src libical-0:3.0.20-7.fc44.src libkgapi-0:26.04.0-1.fc45.src ``` Searching for `libical*` produces much longer list, but it's due to the dependencies, as far as I can tell. The evolution-data-server and evolution packages are ready for the switch, it might need some minor tweaks, if any at all. I do not know about the other projects, thus I'm asking here first. The libical 4.0 is very fresh, I'm fine to wait until the other projects are ready. I CC'ed the above package maintainers too. Let me know what you think would be the best. Thanks and bye, Milan [bug2458837] https://bugzilla.redhat.com/show_bug.cgi?id=2458837 P.S.: this is a resend, the original message from April 21st did not pass the list moderation, due to too many recipients (I added package owners as CC, not BCC, all through their fedoraproject.org addresses).

2 5

Two-factor authentication required for provenpackager members
by Maxwell G via devel-announce 24 Aug '26

24 Aug '26

Hi everyone, FESCo has voted to require two-factor authentication (2FA) for all members of the provenpackager group (SHOULD is now upgraded to MUST). Please enable 2FA if you haven't yet. During the three-month grace period, existing provenpackager accounts without 2FA can continue to be used, but 2FA is required for any new provenpackager members. After the end of the grace period, remaining provenpackager accounts will be temporarily downgraded until 2FA is enabled. 2FA is also strongly recommended for non-provenpackager accounts. Please see https://docs.fedoraproject.org/en-US/fedora-accounts/user/#twofactor for more information on setting up 2FA in the Fedora Accounts System. It is recommended to maintain a backup of your 2FA tokens and/or enroll multiple devices (e.g., a hardware security device and a mobile authenticator app). Any new users applying to the provenpackager group must have 2FA set up in Fedora Accounts. For provenpackager members who currently do not have 2FA configured, a three month grace period (until 2026-09-24) is provided to set up 2FA in Fedora Accounts. Affected users will be emailed directly. Members who have not enabled 2FA by 2026-09-24 will be removed from the provenpackager group. Those members can be reinstated once they configure 2FA by filing a ticket with Fedora Infrastructure — they do NOT need to re-apply to FESCo for provenpackager access. All the best, Maxwell (on behalf of FESCo) -- _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

2 1

fedpkg clone fails with Permission denied (publickey).
by Richard Shaw 24 Aug '26

24 Aug '26

Long story short I lost my home directory where I do all of my packager activities (separate from my main user) so I'm setting things up from scratch. I created new ssh keys and uploaded the public key to admin.fedoraproject.org and pasted into pagure.io. It's been over an hour and I'm still getting: $ fedpkg clone hamlib Cloning into 'hamlib'... hobbes1069(a)pkgs.fedoraproject.org: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Could not execute clone: Failed to execute command. I've also updated my API tokens, which is STILL not well documented. I pasted them in the appropriate spot in "/etc/rpkg/fedpkg.conf" which isn't real intuitive. Thanks, Richard

6 11

s390x builder outage
by Kevin Fenzi via devel-announce 23 Aug '26

23 Aug '26

Just to notify a wider audience, our s390x builders have been offline today due to a failure of a storage array. Folks have been working today to bring it back up, but the fix will require parts that need to be overnight shipped. Hopefully the machines will be back online tomorrow after the replacement is installed. Arched Builds submitted now will wait for s390x builders to be back to complete. You can watch https://www.fedorastatus.org/ and/or https://forge.fedoraproject.org/infra/tickets/issues/13326 for further status. Sorry for the outage. kevin -- _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

22 46

Help needed with matrix-synapse
by Kai A. Hiller 18 Aug '26

18 Aug '26

Hello, I am currently unable to provide the amount of work required for fully maintaining matrix-synapse. Could somebody please help with getting Synapse’s latest version to build on F44 and below? Thank you Kai

6 10

binary content in node_modules
by Gordon Messmer 14 Aug '26

14 Aug '26

I've started a review of a nodejs package, and its bundled node_modules include wasm and native binaries. I wanted to provide the packager with examples of packages that fix up their node_modules properly, but I'm actually a little confused by what I found. I picked nodejs-undici for reference, since it has a sources script: https://src.fedoraproject.org/rpms/nodejs-undici/blob/rawhide/f/undici-sour… That script removes wasm and rebundles the code, but only for the program itself. It's not stripping the node_modules directories of pre-built content. The prod directory is relatively small and I didn't see any pre-built binaries, but the dev directory contains "esbuild" ELF binaries. Shouldn't node_modules be stripped of this kind of content before uploading source? What package would you recommend as an reference example?

9 28

Way too much automated email on this list
by Kashyap Chamarthy 09 Aug '26

09 Aug '26

Hi folks, There is way too much automated email on this list. It's getting ridiculous. I say this as a 'power user' who is no stranger to very high-traffic lists. Today I had to add this "hook" to my main client (Mutt) to will hide the automated gunk from view. So I can at least skim the damn list! folder-hook Fedora/devel 'limit ! (~s "ELN Report" | ~s "Branched Report" | ~s "Rawhide Report" | ~s "compose" | ~s "Meeting")' (I know, I might miss some precious discussion that could branch out from these mails. It's a tiny cost to pay for the skimmability gains.) If we don't fix this deluge, expect non-power users of lists to drop out drastically. Only a handful of those who configured their setup to hell and back[1] might remain. * * * How about creating a 'fedora-notifications' or 'fedora-reports' list and redirect them all there? Or a weekly "digest" with relevant links and reports in a _single_ email. I'm on this list to read what other _humans_ are talking about! I may soon have to start feeding an 'mbox' of this list to a local LLM to get a digest of it. [1] https://xkcd.com/1782/ Regards, Kashyap

29 69

Re: civetweb
by Kaleb Keithley 08 Aug '26

08 Aug '26

On Mon, Jun 8, 2026 at 7:09 AM Fernando Hueso González <Fernando.Hueso(a)uv.es> wrote: > Hello, I wanted to ask if it were possible to turn on *-DCIVETWEB_ENABLE_WEBSOCKETS=ON > -DCIVETWEB_ENABLE_X_DOM_SOCKET=ON* > > when building civetweb on Fedora / AlmaLinux packages > > It's necessary for building ROOT's CERN software with the system-packaged > version of civetweb. > > Thanks in advance. > Sure. I don't see why not. Be aware that civetweb is (currently) retired in rawhide. It wasn't apparent that anyone was using it. At least it isn't being used by any other packages _in_ Fedora. (It was originally added for nfs-ganesha which used it for a couple of versions.) Maybe someone wants to take it over and unretire it? (I'm planning on retiring soon and will soon be looking for someone or a couple of someones to take over my other packages.) -- Kaleb

2 1

Trying to release a new version of a package
by Kenneth Goldman 04 Aug '26

04 Aug '26

Evidently my notes are wrong (or something else). I don't do this too often. I cloned the repo: git clone https://src.fedoraproject.org/rpms/tss2.git updated the .spec file tested with fedpkg --release rawhide --name tss2 mockbuild (did f43 and f44 as well) How do I push the changes? In the past, I used: fedpkg --release f43 --name tss2 new-sources ibmtss2.5.0.tar.gz Output is: Uploading: ibmtss2.5.0.tar.gz to https://src.fedoraproject.org/repo/pkgs/upload.cgi Could not execute new sources: Fail to upload files. Server returns status 403 and git push origin rawhide Output is: fatal: Authentication failed for 'https://src.fedoraproject.org/rpms/tss2.git/' I think my user name and password are ok since 'koji moshimoshi' succeeds. -- Work 1-914-945-2415 -- Work 1-914-945-2415

6 11

nodejs20 retired in rawhide
by Jan Stanek 30 Jul '26

30 Jul '26

Hello list! Following the upstream support reaching EOL support [1], I have retired the nodejs20 package in rawhide. The last available version is 20.20.2, and you are encouraged to migrate to nodejs22 or nodejs24, which upstream still supports. [1]: https://nodejs.org/en/about/previous-releases Please note that we currently do not plan to obsolete the package (via the fedora-obsolete-packages [2] rpm), so it should remain installable (as should previous versions, as far as I can tell). However, this is open to discussion. If you feel we should be more proactive in preventing installations of EOL versions, please let us know. [2]: https://src.fedoraproject.org/rpms/fedora-obsolete-packages Best regards! -- Jan Stanek Senior Software Engineer Red Hat IM: @jstanek

1 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel June 2026