Self Introduction: Penn Bauman

2025-05-12 Thread Penn Bauman
Hello Fedora, My name is Penn Bauman. I have been using Linux for 8 years, Fedora for 4 year, and I currently use Fedora Silverblue. I have been packaging several pieces of software in Copr [1] for years and I think they are ready to be included in mainline Fedora. My initial goal is to add L

Re: How to deal with static libraries and cmake?

2025-05-12 Thread Paul Grosu
Hi Orion, Thank you for pointing me to the Bugzilla page. Could you please add me to the packager and/or qa group for my FAS account (pgrosu) so I can log into f40-test.fedorainfracloud.org to test this out. Thanks, Paul On Sun, May 11, 2025 at 4:45 PM Orion Poplawski wrote: > On 5/9/25 23:37

License change: Unhide

2025-05-12 Thread Robby Callicotte via devel
Hello, I recently updated Unhide in rawhide. The license tag has been updated as follows: GPL-3.0-or-later AND MIT Previous tag: GPL-3.0-only Regards, Robby Callicotte -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe se

Fedora Linux 40 is EOL tomorrow, May 13

2025-05-12 Thread Aoife Moloney via devel-announce
Hi folks, A quick fyi that F40 will go EOL tomorrow, May 13 2025. Bugzillas opened against this version have already received warning message that this date was approaching ~2 weeks ago, so this is just another heads up that after tomorrow, all open bugs against F40 will be automatically closed.

Fedora Linux 40 End of Life

2025-05-12 Thread Samyak Jain
Hello all, Fedora Linux 40 will go end of life for updates and support on 2025-05-13. No more updates of any kind, including security updates or security Announcements will be available for Fedora Linux 40 after this date. No pending updates for Fedora Linux 40 will be pushed to stable. Fedora Li

Re: Working around multilib symlink conflicts in llvm

2025-05-12 Thread Josh Stone
On 5/12/25 12:31 AM, Florian Weimer wrote: > * Nikita Popov: > >> In f42 the main llvm package switched to installing all files under a >> /usr/lib{64}/llvmN prefix and >> providing symlinks in the default prefix, to align the contents between the >> versioned and unversioned >> packages. What w

orphaned: aws-c-*, ec2-instance-connect and s2n-tls

2025-05-12 Thread Dominik Wombacher
Hi everyone, as announced a week ago [1], I orphaned the following packages today: rpms/aws-c-auth rpms/aws-c-compression rpms/aws-c-event-stream rpms/aws-checksums rpms/aws-c-http rpms/aws-c-io rpms/aws-c-mqtt rpms/aws-c-s3 rpms/aws-c-sdkutils rpms/ec2-instance-connect rpms/s2n-tls Dom (FAS: wo

Re: Help wanted - Potentially broken use of sysusers.d in systemtap package

2025-05-12 Thread Alex Haydock
Ah, that helps! I see now. The nested `if` statements had thrown me off. I missed the fact it's the %{with_sysusers} check that's falling back to the oldschool method of directly using user creation commands if not satisfied. I'd been reading it as if it fell back to that method if the version c

Re: Help wanted - Potentially broken use of sysusers.d in systemtap package

2025-05-12 Thread Zbigniew Jędrzejewski-Szmek
On Sat, May 10, 2025 at 12:58:58PM -, Alex Haydock wrote: > Fedora Atomic bug documented here: > https://bugzilla.redhat.com/show_bug.cgi?id=2359764 > > I think this bug comes from the systemtap .spec's use of traditional (non > sysusers.d) methods to handle user creation. I tried to author

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

2025-05-12 Thread Petr Pisar
V Sun, May 11, 2025 at 05:40:55PM -, Ryan Bach via devel napsal(a): > 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 > > >

Re: How to deal with static libraries and cmake?

2025-05-12 Thread Kevin Kofler via devel
Orion Poplawski wrote: > I did come across this: > > https://reviews.llvm.org/D32668 > > which seems promising, but not sure I'll be able to adapt that to > SuiteSparse or not. That looks like the right approach in any case: export the static targets to a separate file and include that file w

perl-Cairo-GObject license tag corrected

2025-05-12 Thread Petr Pisar
I corrected a license tag in perl-Cairo-GObject package from "LicenseRef-Callaway-LGPLv2+" to "LGPL-2.1-or-later". -- Petr signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an emai

Fedora rawhide compose report: 20250512.n.0 changes

2025-05-12 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20250511.n.0 NEW: Fedora-Rawhide-20250512.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 1 Dropped packages:0 Upgraded packages: 34 Downgraded packages: 0 Size of added packages: 1.33 MiB Size of dropped packages:0 B

Re: How to deal with static libraries and cmake?

2025-05-12 Thread Cristian Le via devel
On 2025/05/11 22:42, Orion Poplawski wrote: To be clear, I would prefer to be able to still package and ship the static libraries in a separate package.  Although I am considering just dropping the static build as well.  But I think the HPC / scientific community still has a reasonably high in

Re: Working around multilib symlink conflicts in llvm

2025-05-12 Thread Florian Weimer
* Nikita Popov: > In f42 the main llvm package switched to installing all files under a > /usr/lib{64}/llvmN prefix and > providing symlinks in the default prefix, to align the contents between the > versioned and unversioned > packages. What we were not aware of at the time is that rpm's suppor