Insight on impact of an update to dropbear

Hello, I'd like to ask you guys an indication on a package upgrade. I'd like to update dropbear for 42 and 41 (and possibily 40 still) following the upgrade on Rawhide, mostly to fix a recent CVE. But besides fixing the CVE it brings a few configuration / default changes, so I'm not sure if this w

Fedora eln compose report: 20250512.n.0 changes

OLD: Fedora-eln-20250511.n.0 NEW: Fedora-eln-20250512.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 3 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of

Re: How to deal with static libraries and cmake?

On 5/9/25 23:37, Paul Grosu wrote: Hi Orion, Do you have the complete build-log to see the trace of it?  Something similar to this: https://build.alpinelinux.org/buildlogs/build-3-20-x86_64/community/ suitesparse/suitesparse-7.7.0-r0.log

Re: How to deal with static libraries and cmake?

On 5/10/25 10:36, Ben Beasley wrote: I recently had to fix this in the opensubdiv package. As Cristian said, every project is different, but here’s one simple example of a successful downstream patch: https://src.fedoraproject.org/rpms/opensubdiv/c/fb27f64a61a5eb8fc123132213870dcb4211872e?bran

Re: failed to add subkeys for /var/cache/PackageKit/43/metadata/google-chrome-rawhide-x86_64/linux_signing_key.pub to rpmdb

Petr Pisar wrote: > V Tue, Apr 29, 2025 at 09:32:18PM -, Ryan Bach via devel napsal(a): > > failed to add subkeys for > > /var/cache/PackageKit/43/metadata/google-chrome-rawhide-x86_64/linux_signing_key.pub > > to rpmdb > > Report it please against PackageKit in Fedora's Bugzilla and don't fo

Heads-up: Updating llhttp to 9.3.0 in Rawhide

In one week, 2025-05-18, or slightly later, I plan to update llhttp to 9.3.0[1] in Rawhide. Based on the source diff[2], this release contains no obvious security fixes or exceptionally serious bug fixes. Therefore, although this package has a permanent exception under the Updates Policy[3][4]

Updating uv from 0.6.17 to 0.7.x in all Fedora releases and in EPEL10 leading branch

In one week, 2025-05-18, or slightly later, I plan to update the uv package from 0.6.17 to 0.7.3 or a later 0.7.x release[1] in Fedora Rawhide, 42, and 41. (Fedora 40 will have reached its end-of-life by then.) I also plan to ship the same update to the EPEL10 leading branch, currently EPEL 10.

Re: Noctua Presentation

Here I submitted a new package https://bugzilla.redhat.com/show_bug.cgi?id=2365521 since pycryptodome seems to be already present in the repo source, despite orphan. Can you review it please? -- ___ devel mailing list -- devel@lists.fedoraproject.org T

Re: Noctua Presentation

On 11-05-2025 05:19, Cristian Le via devel wrote: On 11 May 2025 03:24:14 CEST, Neal Gompa wrote: Huh, I think we retired this years ago in favor of python-pycryptodomex: https://src.fedoraproject.org/rpms/python-pycryptodomex If you've still got projects using pycryptodome, you should port