Re: Need help with pybind11 c++ compilation warning/error
On 5 February 2025 06:17:01 CET, Orion Poplawski wrote: >cc1plus: all warnings being treated as errors >gmake[2]: *** [libmambapy/CMakeFiles/bindings.dir/build.make:96: >libmambapy/CMakeFiles/bindings.dir/src/libmambapy/bindings/legacy.cpp.o] Error >1 > >I'm guessing 'SR.32262' is some kind of temporary variable. libmamba has >taken the (perhaps admirable?) step of compiling with -Werror so it fails. The errors are in mamba's code base afaict. You should disable warnings as error, enforce C++ standard in CMakeLists.txt, ask upstream about C++17 warnings, or all the above. But just to be sure it's gcc15 related can you also target F41? -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: bin-sbin merge rebuild
On Tue, Feb 04, 2025 at 02:16:33PM +, Richard W.M. Jones wrote: > On Tue, Feb 04, 2025 at 02:10:53PM +, Richard W.M. Jones wrote: > > On Mon, Jan 13, 2025 at 01:46:03PM +, Zbigniew Jędrzejewski-Szmek wrote: > > > On Fri, Jan 10, 2025 at 10:13:31AM +, Zbigniew Jędrzejewski-Szmek > > > wrote: > > > > On Fri, Jan 10, 2025 at 08:58:32AM +0100, Florian Weimer wrote: > > > > > * Zbigniew Jędrzejewski-Szmek: > > > > > > > > > > > glibc > > > > > > > > > > If we rebuild glibc, should we do a second rebuild into your side tag? > > > > > > > > Probably… But let's coordinate (here or on Matrix). I hope we can > > > > avoid duplicate rebuilds. > > > > > > The update with the rebuilds has been pushed to stable > > > (https://bodhi.fedoraproject.org/updates/FEDORA-2025-da0a082e66). > > > rpm was pushed independently earlier today > > > (https://bodhi.fedoraproject.org/updates/FEDORA-2025-432932ed60). > > > > > > In the buildroot, builds should now see a merged filesystem. > > > Once the compose goes out, people installing rawhide should > > > end up with a merged filesystem, and people upgrading rawhide > > > should see a message like > > > /usr/sbin cannot be merged, found /usr/sbin/ > > > Once the mass rebuild goes through, people upgrading rawhide > > > should see a message like > > > All files under /usr/sbin are symlinks; linking to ./bin... > > > Once that's done, the merge is complete on upgraded systems. > > > > What's the component / script which prints this message? > > To answer my own question, it's a Lua script in filesystem.spec. Yes. > > Is it safe to 'dnf update' an existing Fedora Rawhide installation now? Yes. (There never was a point where it wasn't…) Zbyszek -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: bin/sbin merge: Are we going to change kconfig MODPROBE_PATH?
On Wed, Feb 05, 2025 at 03:02:33PM +, Richard W.M. Jones wrote: > On Wed, Feb 05, 2025 at 01:57:01PM +, Zbigniew Jędrzejewski-Szmek wrote: > > On Wed, Feb 05, 2025 at 12:03:21PM +, Richard W.M. Jones wrote: > > > https://github.com/torvalds/linux/blob/5c8c229261f14159b54b9a32f12e5fa89d88b905/kernel/module/Kconfig#L416 > > > > > > This defaults to "/sbin/modprobe". Should it be changed to > > > "/usr/bin/modprobe"? > > > > > > A few possible reasons: > > > > > > (1) Bad RPM installers that don't run scripts, specifically the > > > filesystem.spec script. (This is the case that broke for me.) > > > > Can you expand a bit on this? All installs with 'rpm' should DTRT. > > It's not really possible in some circumstances, namely when trying to > install an RPM without needing to be root. (There are also package > systems like bazel which are simply broken in this regard, but that's > another issue.) Ack. I guess 'rpm2cpio … | cpio -i --make-dir' falls into this category. But systems "installed" in such a way will have other problems: ldconfig, alternatives, systemd symlinks, and many other things are created via scriptlets. The bad part is that that chroot will not have the /usr/sbin symlink at all, since it's created via a scriptlet. > So eventually are we planning to remove the script stuff in > filesystem.spec, and replace it with a simple /usr/sbin -> /usr/bin > symlink RPM file entry? Eventually – yes. But I'd like to keep the upgrades from older systems working. If we just change the symlink to be part of the normal payload, rpm would refuse to upgrade. Maybe we can make this work with some %pretrans script that removes the old directory. Zbyszek -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: removing self as co-maintainer on several packages
V Wed, Feb 05, 2025 at 02:50:18PM -, Ken Dreyer napsal(a):
> Hi folks, I've changed jobs recently and I need to drop
> co-maintainership on some packages.
>
> I have (co-)maintainership on 27 packages here:
> https://src.fedoraproject.org/user/ktdreyer/projects
>
> If I have admin permissions on a package, I can remove myself, but for many
> of these I only have co-maintainer rights ("commit" rights in Pagure,
> sometimes even restricted to certain branch patterns like epel)
>
> How can I remove myself from packages where I don't have admin access?
> https://src.fedoraproject.org/rpms/babeltrace , for example.
I have a haze memory that it's possible with a web API. The web user interface
definitly does not support it.
I removed you from perl-NTLM.
-- Petr
signature.asc
Description: PGP signature
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Rust SIG Spring Cleaning - 2025 Edition
On Wed, Feb 5, 2025 at 2:51 PM Ben Beasley wrote: > > It seems like the inclusion of rust-smallvec on this list might have > been an error, since "fedrq wr rust-smallvec*-devel" gives a very large > number of results that aren’t subpackages of rust-smallvec itself. You are correct, this should have been "smallstr", not "smallvec" (typo on my side). While smallstr depends on smallvec, nothing depends on smallstr itself any longer. > - > > I know that members of the AI/ML SIG are interested in packaging > python-safetensors, which would require rust-safetensors (and, I think, > is the reason it was originally packaged). I was chatting with them > about it on Matrix just a few days ago. > > The first step would be getting rust-safetensors up to date, > https://src.fedoraproject.org/rpms/rust-safetensors/pull-request/1. > > I am not sure when or if someone will *actually* do the packaging work > for python-safetensors and put it up for review, but it does seem worth > keeping rust-safetensors around a bit longer in order to support that > possibility. Sounds good to me. I had missed that discussion (and your PR, sorry!). I'll add it to the list of packages that we want to keep. Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: removing self as co-maintainer on several packages
On Wed, Feb 05, 2025 at 02:50:18PM +, Ken Dreyer wrote:
> Hi folks, I've changed jobs recently and I need to drop
> co-maintainership on some packages.
>
> I have (co-)maintainership on 27 packages here:
> https://src.fedoraproject.org/user/ktdreyer/projects
>
> If I have admin permissions on a package, I can remove myself, but for many
> of these I only have co-maintainer rights ("commit" rights in Pagure,
> sometimes even restricted to certain branch patterns like epel)
>
> How can I remove myself from packages where I don't have admin access?
> https://src.fedoraproject.org/rpms/babeltrace , for example.
You will need to contact someone who is an admin for the package(s) to
remove you. ;(
Or, I suppose if it's a long list and there's difficulty contacting
everyone you could file a releng ticket to have releng do it.
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2025-02-06 from 15:00:00 to 16:00:00 US/Eastern At meet...@fedoraproject.org The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10979/ -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Linux 42 Has Been Branched!
Hi All, Fedora Linux 42 has now been branched! Please be sure to run git fetch -v to pick up the new branch. As a reminder, Rawhide and Fedora Linux 42 are now completely isolated from previous releases. This means that any changes you make for Fedora 42 should also be applied in the Rawhide branch, and a corresponding build should be done there. A Fedora Linux 42 compose will be generated and will appear in [1] once complete. Bodhi is currently enabled in the Fedora Linux 42 branch, similar to Rawhide, with automatic update creation. When we reach the Beta Change Freeze in the Fedora Linux 42 schedule [2], updates-testing will be enabled, and manual Bodhi updates will be required, as is the case for all stable releases. The Fedora 42 Branched release is currently frozen until we achieve a successful composition. Please expect that your Fedora 42 builds will not be available immediately. Additionally, the following package updates were unpushed at the time of mass branching to avoid placing them in an inconsistent state. Maintainers should verify their updates and push them as needed: Unpushed/Revoked Updates: FEDORA-2025-1df6d10dfc - nodejs22-22.13.1-1.fc42 FEDORA-2025-326f30cbd8 - httpd-2.4.63-1.fc42 FEDORA-2025-4217a95b13 - openwsman-2.7.2-14.fc42 FEDORA-2025-436275a69d - iscsi-initiator-utils-6.2.1.10-0.gitd0f04ae.fc42.3 FEDORA-2025-63cd1b3f96 - fcitx5-lua-5.0.14-1.fc42 FEDORA-2025-679a0f5501 - binutils-2.44-1.fc42 FEDORA-2025-7fcd6c3f4c - libsecret-0.21.6-1.fc42 FEDORA-2025-8c6212f8f8 - vsftpd-3.0.5-10.fc42 FEDORA-2025-9eb31c83d9 - dracut-105-1.fc42 FEDORA-2025-ab13571cc1 - osbuild-139-1.fc42 FEDORA-2025-ae9bfeedff - mysql-connector-java-8.0.30-15.fc42 FEDORA-2025-b0fe175865 - cpio-2.15-4.fc42 FEDORA-2025-bacda91d23 - tmt-1.42.1-1.fc42 FEDORA-2025-c1d22427c2 - bluedevil-6.2.91-1.fc42, breeze-gtk-6.2.91-1.fc42, (etc) FEDORA-2025-c3119a8ebb - llvm-19.1.7-5.fc42 FEDORA-2025-ded532ce7d - weldr-client-35.14-3.fc42 FEDORA-2025-e42ccc4c9b - util-linux-2.40.4-4.fc42 FEDORA-2025-eae56b1c0a - frr-10.2.1-1.fc42, libnetconf2-3.5.5-1.fc42, libyang-3.7.8-1.fc42, netopeer2-2.2.35-1.fc42, sysrepo-3.3.10-1.fc42 FEDORA-2025-ed82d7584e - tomcat-10.1.34-3.fc42 FEDORA-2025-fccba7057c - criu-4.0-4.fc42 In most cases, submitting a new build for Rawhide (now Fedora 43) and Fedora 42 should work (assuming any gating failures are resolved). Thanks for your understanding. Regards, Samyak Jain Fedora Release Engineering [1] https://dl.fedoraproject.org/pub/fedora/linux/development/42/ [2] https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html -- ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@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-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: removing self as co-maintainer on several packages
On 2/5/25 8:50 AM, Ken Dreyer wrote:
Hi folks, I've changed jobs recently and I need to drop
co-maintainership on some packages.
I have (co-)maintainership on 27 packages here:
https://src.fedoraproject.org/user/ktdreyer/projects
If I have admin permissions on a package, I can remove myself, but for many of these I
only have co-maintainer rights ("commit" rights in Pagure, sometimes even
restricted to certain branch patterns like epel)
How can I remove myself from packages where I don't have admin access?
https://src.fedoraproject.org/rpms/babeltrace , for example.
Hey Ken, I remember us crossing paths at some point. Sad to hear you have to step
away from Fedora.
lttng-ust is needed by dotnet so that may be of interest to Omar. 'CCing.
Regards,
Michael
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Rust SIG Spring Cleaning - 2025 Edition
It seems like the inclusion of rust-smallvec on this list might have been an error, since "fedrq wr rust-smallvec*-devel" gives a very large number of results that aren’t subpackages of rust-smallvec itself. - I know that members of the AI/ML SIG are interested in packaging python-safetensors, which would require rust-safetensors (and, I think, is the reason it was originally packaged). I was chatting with them about it on Matrix just a few days ago. The first step would be getting rust-safetensors up to date, https://src.fedoraproject.org/rpms/rust-safetensors/pull-request/1. I am not sure when or if someone will *actually* do the packaging work for python-safetensors and put it up for review, but it does seem worth keeping rust-safetensors around a bit longer in order to support that possibility. On 2/5/25 8:21 AM, Fabio Valentini wrote: Hi all, In an effort to keep the stack of Rust crate packages in good shape in Fedora, I'm regularly checking for library-only packages that have been unused for extended periods of time (usually 365+ days, i.e. two full release cycles). Dropping packages like this reduces the maintenance effort overall due to less dense dependency graphs - making updates for remaining Rust packages easier. Additionally, many of these crates were either packaged for reasons that are no longer valid (i.e. they were a dependency of something in the past, but are no longer being depended on now), they are obsolete and replaced by other crates "upstream", or they were packaged as part of an effort to ship a specific application, but that effort has since been abandoned. These library-only (source-only) packages for Rust crates have been unused for 365+ days (by main maintainer): albertlarsan68: rust-fend-core atim: rust-nparse blinxen:rust-symlink dcavalca: rust-rusttype decathorpe: rust-ghost, rust-smallvec, rust-unidecode leo:rust-colorgrad, rust-enum-display-derive, rust-euclid salimma:rust-nom-supreme, rust-vec1, rust-xcb thunderbirdtr: rust-safetensors Some packages are omitted from this list because there are still valid reasons to keep them (for example, packages that are still pending review depend on them, or they will be needed for other pending crate updates). I looked at package review tickets in an attempt to figure out why these packages were originally packaged, but that wasn't always possible (because it wasn't mentioned in the ticket and / or the review bug didn't block any other bugs): colorgrad: ? enum-display-derive:? euclid: ? fend-core: ? ghost: used to be dependency of something, no longer is nom-supreme:? nparse: used to be dependency of something, no longer is rusttype: ? (blocked "Fedora Asahi Remix: touchbar support") safetensors:? smallvec: used to be dependency of something, no longer is suggest:? (potentially as a dependency of "zellij") symlink:used to be dev-dependency of gix-worktree (now removed) unidecode: used to be dependency of fake (replaced with deunicode) vec1: ? xcb:used to be dependency of x11-clipboard (replaced with x11rb) If there is a package in this list that is still needed for something that you're working on, please let me know soon, and I will add it to the list here: https://pagure.io/ironthree/fedora-rust-sig-leaf-check/blob/main/f/reasons.txt Otherwise I plan to retire any Rust packages that are - library-only / source-only and - have been unused leaf packages for 365+ days and - have no documented reason for why they are still needed before the F42 Beta Freeze takes effect. Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
removing self as co-maintainer on several packages
Hi folks, I've changed jobs recently and I need to drop
co-maintainership on some packages.
I have (co-)maintainership on 27 packages here:
https://src.fedoraproject.org/user/ktdreyer/projects
If I have admin permissions on a package, I can remove myself, but for many of
these I only have co-maintainer rights ("commit" rights in Pagure, sometimes
even restricted to certain branch patterns like epel)
How can I remove myself from packages where I don't have admin access?
https://src.fedoraproject.org/rpms/babeltrace , for example.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Fedora CoreOS Community Meeting Minutes 2025-02-05
Minutes: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-02-05/fedora-coreos-meeting.2025-02-05-16.31.html Minutes (text): https://meetbot-raw.fedoraproject.org//meeting-1_matrix_fedoraproject-org/2025-02-05/fedora-coreos-meeting.2025-02-05-16.31.log.txt Log: https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-02-05/fedora-coreos-meeting.2025-02-05-16.31.log.html = # #meeting-1:fedoraproject.org: fedora_coreos_meeting = Meeting started by @jbtrystram:matrix.org at 2025-02-05 16:31:17 Meeting summary --- * TOPIC: roll call (@jbtrystram:matrix.org, 16:31:26) * TOPIC: Add azure blob support (@jbtrystram:matrix.org, 16:34:34) * LINK: https://github.com/coreos/ignition/pull/1923#issuecomment-2631451532 (@jbtrystram:matrix.org, 16:34:40) * TOPIC: Implement Proxmox VE (@jbtrystram:matrix.org, 17:00:29) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1652 (@jbtrystram:matrix.org, 17:00:34) * AGREED: Make proxmox a toplevel platform for Fedora CoreOS (@jbtrystram:matrix.org, 17:30:17) Meeting ended at 2025-02-05 17:34:44 Action items People Present (lines said) --- * @jlebon:fedora.im (46) * @dustymabe:matrix.org (44) * @siosm:matrix.org (42) * @jbtrystram:matrix.org (28) * @zodbot:fedora.im (9) * @marmijo:fedora.im (7) * @meetbot:fedora.im (2) * @aaradhak:matrix.org (1) * @mnguyen:fedora.im (1) * @hricky:fedora.im (1) * @ravanelli:matrix.org (1) -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: bin/sbin merge: Are we going to change kconfig MODPROBE_PATH?
On Wed, Feb 05, 2025 at 01:57:01PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Wed, Feb 05, 2025 at 12:03:21PM +, Richard W.M. Jones wrote: > > https://github.com/torvalds/linux/blob/5c8c229261f14159b54b9a32f12e5fa89d88b905/kernel/module/Kconfig#L416 > > > > This defaults to "/sbin/modprobe". Should it be changed to > > "/usr/bin/modprobe"? > > > > A few possible reasons: > > > > (1) Bad RPM installers that don't run scripts, specifically the > > filesystem.spec script. (This is the case that broke for me.) > > Can you expand a bit on this? All installs with 'rpm' should DTRT. It's not really possible in some circumstances, namely when trying to install an RPM without needing to be root. (There are also package systems like bazel which are simply broken in this regard, but that's another issue.) > > (2) I suspect some race between needing to modprobe modules are > > running the filesystem.spec script, even in a well-behaved RPM > > install. > > Indeed, there is a race on split systems, during the first upgrade > from a package with /usr/sbin/modprobe to a package with /usr/bin/modprobe. > The window is between the %postun phase of the old package and > the %posttrans scriptlets in filesystem to create the symlink. > But I think this can be ignored… It's a one-time occurence and > would require new drivers to requested in in that window. > > In general, when stuff is in the middle of the upgrade, some minor > transitory issues are expected. It's very hard to make those completely > go away with our non-transactional system and that's why we officially > recommend offline upgrades. > > > (3) Extremely small speed increase not having to follow a symlink? > > The downside of changing the path is that systems with the old path > would stop working. It's impossible to ensure the version of the > userspace from the kernel. Because of that, I'd vote against changing > the path as split systems are supported (i.e. at least until F41 goes > EOL). Hmm this is true. It's a shame the kernel doesn't allow a colon-separated list here. So eventually are we planning to remove the script stuff in filesystem.spec, and replace it with a simple /usr/sbin -> /usr/bin symlink RPM file entry? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nodejs22 rawhide update unpushed (among others)
On Wed, Feb 05, 2025 at 01:42:17PM +0100, Fabio Valentini wrote: > On Wed, Feb 5, 2025 at 1:26 PM Artur Frenszek-Iwicki > wrote: > > > > We're currently in the middle of F42 branching + related freeze. > > > > > All builds that will be running at that time for the rawhide will be > > > canceled and can be resubmitted by maintainers after the branching. > > > > > > All rawhide updates that are pending for rawhide will be unpushed. > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HLQJ7KK4HQ2ROB3HCKAUN3PVZOXIZ6H7/ > > Yes, this was intentional. Maybe it would have been good to also add a > comment to those updates and not just unpush them. yeah. Sorry about that. Will add a note next time. > Updates that are stuck in "gating" (i.e. in "pending" or "testing" > state) during the mass branching will end up in a weird state, and > will always require manual action to fix and end up in a consistent > state. > > In most cases, submitting a new build for rawhide (now F43) and F42 > should work (assuming the gating failures are taken care of, of > course). Yep. This ^ kevin -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [heads up] mass rebuild for opencv 4.11.0 with soname bump on rawhide
On Wed, 2025-02-05 at 10:40 -0800, Adam Williamson wrote: > On Tue, 2025-02-04 at 12:35 +, Sérgio Basto via devel wrote: > > On Tue, 2025-02-04 at 02:00 +, Sérgio Basto via devel wrote: > > > On Mon, 2025-02-03 at 01:06 +, Sérgio Basto via devel wrote: > > > > Hi, > > > > I will start a mass rebuild in a side-tag, very soon , the goal > > > > is > > > > finish and merge it before the mass branch which is scheduled > > > > for 4 > > > > of > > > > Feb of 2025 > > > > > > Started > > > > > > Building opencv-4.11.0-1.fc42 for f42-build-side-104797 > > > > > > Failures from my tests are : dtkmultimedia alreaady FTBFS , gmic > > > FTBFS > > > ? os-autoinst fails only on ppc64le and opentoonz > > > > > > Corrections are welcome and you can submit builds to the side tag > > > > side tag merged to stable , missing dtkmultimedia, gmic , os- > > autoinst > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2025-8ca0faa87a > > > > > > opentoonz was built successful, later, already in rawhide with the > > latest fixes > > Next time could you please email me directly for os-autoinst? devel@ > gets a lot of email and I don't read it all. I didn't see this. The > guidelines say to contact maintainers directly. > OK , thanks for the tip > Thanks! -- Sérgio M. B. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [heads up] mass rebuild for opencv 4.11.0 with soname bump on rawhide
On Tue, 2025-02-04 at 12:35 +, Sérgio Basto via devel wrote: > On Tue, 2025-02-04 at 02:00 +, Sérgio Basto via devel wrote: > > On Mon, 2025-02-03 at 01:06 +, Sérgio Basto via devel wrote: > > > Hi, > > > I will start a mass rebuild in a side-tag, very soon , the goal is > > > finish and merge it before the mass branch which is scheduled for 4 > > > of > > > Feb of 2025 > > > > Started > > > > Building opencv-4.11.0-1.fc42 for f42-build-side-104797 > > > > Failures from my tests are : dtkmultimedia alreaady FTBFS , gmic > > FTBFS > > ? os-autoinst fails only on ppc64le and opentoonz > > > > Corrections are welcome and you can submit builds to the side tag > > side tag merged to stable , missing dtkmultimedia, gmic , os-autoinst > > https://bodhi.fedoraproject.org/updates/FEDORA-2025-8ca0faa87a > > > opentoonz was built successful, later, already in rawhide with the > latest fixes Next time could you please email me directly for os-autoinst? devel@ gets a lot of email and I don't read it all. I didn't see this. The guidelines say to contact maintainers directly. Thanks! -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Need help with pybind11 c++ compilation warning/error -> python abort()
On 2/4/25 22:17, Orion Poplawski wrote: I'm working on updating libmamba to 2.0.X [1] but hitting the following error: cd /home/orion/fedora/libmamba/libmamba-2.0.6-build/mamba-2.0.6/redhat- linux-build/libmambapy && /usr/lib64/ccache/g++ -DFMT_SHARED - DMAMBA_USE_INSTALL_PREFIX_AS_BASE -DSPDLOG_FMT_EXTERNAL - DSPDLOG_FWRITE_UNLOCKED -Dbindings_EXPORTS -I/home/orion/fedora/ libmamba/libmamba-2.0.6-build/mamba-2.0.6/libmambapy/src/libmambapy/ bindings -I/home/orion/fedora/libmamba/libmamba-2.0.6-build/mamba-2.0.6/ libmamba/include -isystem /usr/include/python3.13 -isystem /usr/share - O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches - pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,- D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/ redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/ redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous- unwind-tables -fstack-clash-protection -fcf-protection -mtls- dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -O2 -g -DNDEBUG -fPIC -fvisibility=hidden -Wall -Wextra -Wshadow -Wnon-virtual- dtor -Wold-style-cast -Wcast-align -Wunused -Woverloaded-virtual - Wpedantic -Wconversion -Wsign-conversion -Wnull-dereference -Wdouble- promotion -Wformat=2 -Wunreachable-code -Wuninitialized -Werror - Wmisleading-indentation -Wduplicated-cond -Wduplicated-branches - Wlogical-op -Wuseless-cast -Wno-error=deprecated-declarations -MD -MT libmambapy/CMakeFiles/bindings.dir/src/libmambapy/bindings/legacy.cpp.o -MF CMakeFiles/bindings.dir/src/libmambapy/bindings/legacy.cpp.o.d -o CMakeFiles/bindings.dir/src/libmambapy/bindings/legacy.cpp.o -c /home/ orion/fedora/libmamba/libmamba-2.0.6-build/mamba-2.0.6/libmambapy/src/ libmambapy/bindings/legacy.cpp /home/orion/fedora/libmamba/libmamba-2.0.6-build/mamba-2.0.6/libmambapy/ src/libmambapy/bindings/legacy.cpp: In lambda function: /home/orion/fedora/libmamba/libmamba-2.0.6-build/mamba-2.0.6/libmambapy/ src/libmambapy/bindings/legacy.cpp:557:47: warning: ‘mamba::expected_t > mamba::SubdirData::cache_path() const’ is deprecated: since version 2.0 use ``valid_solv_cache`` or ``valid_json_cache`` instead [-Wdeprecated- declarations] 557 | return extract(self.cache_path()); | ~~~^~ In file included from /home/orion/fedora/libmamba/libmamba-2.0.6-build/ mamba-2.0.6/libmambapy/src/libmambapy/bindings/legacy.cpp:30: /home/orion/fedora/libmamba/libmamba-2.0.6-build/mamba-2.0.6/libmamba/ include/mamba/core/subdirdata.hpp:135:33: note: declared here 135 | expected_t cache_path() const; | ^~ In file included from /usr/include/pybind11/attr.h:14, from /usr/include/pybind11/detail/class.h:12, from /usr/include/pybind11/pybind11.h:12, from /usr/include/pybind11/functional.h:14, from /home/orion/fedora/libmamba/libmamba-2.0.6-build/ mamba-2.0.6/libmambapy/src/libmambapy/bindings/legacy.cpp:11: In function ‘pybind11::detail::collect_arguments<(pybind11::return_value_policy)1, std::__cxx11::basic_string, std::allocator >&, pybind11::detail::accessor, pybind11::arg_v, void>(std::__cxx11::basic_string, std::allocator >&, pybind11::detail::accessor&&, pybind11::arg_v&&)pybind11::detail::unpacking_collector<(pybind11::return_value_policy)1>’, inlined from ‘pybind11::detail::object_api >::operator()<(pybind11::return_value_policy)1, std::__cxx11::basic_string, std::allocator >&, pybind11::detail::accessor, pybind11::arg_v>(std::__cxx11::basic_string, std::allocator >&, pybind11::detail::accessor&&, pybind11::arg_v&&) constpybind11::object’ at /usr/include/pybind11/cast.h:1823:45, inlined from ‘deprecated(std::basic_string_viewstd::char_traits >, std::basic_string_viewstd::char_traits >)’ at /home/orion/fedora/libmamba/ libmamba-2.0.6-build/mamba-2.0.6/libmambapy/src/libmambapy/bindings/ legacy.cpp:52:26: /usr/include/pybind11/cast.h:1812:67: error: ‘SR.32262’ may be used uninitialized [-Werror=maybe-uninitialized] 1812 | return unpacking_collector(std::forward(args)...); | ^ /usr/include/pybind11/cast.h: In function ‘deprecated(std::basic_string_view >, std::basic_string_view >)’: /usr/include/pybind11/cast.h:1823:45: note: ‘SR.32262’ was declared here 1823 | return detail::collect_arguments(std::forward(args)...).call(derived().ptr()); | ~^ cc1plus: all warnings being treated as errors gmake[2]: *** [libmambapy/CMakeFiles/bindings.dir/build.make:96: libmambapy/CMakeFiles/bindings.dir/src/libmambapy/bindings/legacy.cpp.o] Error 1 I'm guessing 'SR.32262' is some kind of temporary variable. libmamba has taken the (perhaps admirable?) step of compilin
Fedora rawhide compose report: 20250205.n.3 changes
OLD: Fedora-Rawhide-20250204.n.0 NEW: Fedora-Rawhide-20250205.n.3 = SUMMARY = Added images:3 Dropped images: 0 Added packages: 13 Dropped packages:1 Upgraded packages: 186 Downgraded packages: 0 Size of added packages: 5.79 MiB Size of dropped packages:68.04 KiB Size of upgraded packages: 12.93 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 235.39 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Kinoite bootable-container x86_64 Path: Kinoite/x86_64/images/Fedora-Kinoite-x86_64-Rawhide.20250205.n.3.ociarchive Image: Kinoite bootable-container aarch64 Path: Kinoite/aarch64/images/Fedora-Kinoite-aarch64-Rawhide.20250205.n.3.ociarchive Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20250205.n.3.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: linux-sgx-enclaves-prebuilt-2.25-1.fc43 Summary: Intel SGX prebuilt architectural enclaves RPMs:sgx-enclave-prebuilt-common sgx-enclave-prebuilt-ide-signed sgx-enclave-prebuilt-pce-signed sgx-enclave-prebuilt-qe3-signed sgx-enclave-prebuilt-tdqe-signed Size:2.76 MiB Package: php-phpunit-php-code-coverage11-11.0.8-2.fc42 Summary: PHP code coverage information, version 11 RPMs:php-phpunit-php-code-coverage11 Size:249.63 KiB Package: php-sebastian-comparator6-6.3.0-2.fc42 Summary: Compare PHP values for equality, version 6 RPMs:php-sebastian-comparator6 Size:23.03 KiB Package: php-sebastian-exporter6-6.3.0-2.fc42 Summary: Export PHP variables for visualization, version 6 RPMs:php-sebastian-exporter6 Size:14.50 KiB Package: phpunit11-11.5.6-2.fc42 Summary: The PHP Unit Testing framework version 11 RPMs:phpunit11 Size:522.17 KiB Package: python-avalara-24.12.0-1.fc43 Summary: AvaTax Python SDK RPMs:python3-avalara Size:98.75 KiB Package: python-findpython-0.6.2-1.fc42 Summary: A utility to find python versions on your system RPMs:python3-findpython Size:62.35 KiB Package: python-mkdocs-git-committers-plugin-2-2.4.1-1.fc43 Summary: MkDocs plugin to create a list of contributors on the page RPMs:python3-mkdocs-git-committers-plugin-2 Size:28.56 KiB Package: python-mkdocs-git-revision-date-localized-plugin-1.3.0-1.fc43 Summary: Mkdocs plugin to display the last git modification date RPMs:python3-mkdocs-git-revision-date-localized-plugin python3-mkdocs-git-revision-date-localized-plugin+all python3-mkdocs-git-revision-date-localized-plugin+base Size:61.29 KiB Package: rust-ironrdp-error-0.1.2-1.fc42 Summary: IronPDU generic error definition RPMs:rust-ironrdp-error+alloc-devel rust-ironrdp-error+default-devel rust-ironrdp-error+std-devel rust-ironrdp-error-devel Size:36.79 KiB Package: rust-picky-7.0.0~rc.12-1.fc43 Summary: Portable X.509, PKI, JOSE and HTTP signature implementation RPMs:rust-picky+chrono_conversion-devel rust-picky+default-devel rust-picky+http_signature-devel rust-picky+http_timestamp-devel rust-picky+http_trait_impl-devel rust-picky+jose-devel rust-picky+pkcs12-devel rust-picky+pkcs7-devel rust-picky+time_conversion-devel rust-picky+wincert-devel rust-picky+x509-devel rust-picky-devel Size:268.49 KiB Package: rust-snpguest-0.8.2-1.fc43 Summary: AMD SEV-SNP guest utility tool RPMs:snpguest Size:1.68 MiB Package: wcurl-2024.12.08-4.fc43 Summary: A simple wrapper around curl to easily download files RPMs:wcurl Size:16.63 KiB = DROPPED PACKAGES = Package: tcl-signal-1.4-31.fc41 Summary: This extension adds dynamically loadable signal handling to Tcl/Tk scripts RPMs:tcl-signal Size:68.04 KiB = UPGRADED PACKAGES = Package: MagicPoint-1.13a-42.fc42 Old package: MagicPoint-1.13a-39.fc41 Summary: X based presentation software RPMs: MagicPoint Size: 2.51 MiB Size change: -2.26 KiB Changelog: * Mon Sep 02 2024 Miroslav Such?? - 1.13a-40 - convert license to SPDX * Thu Jan 16 2025 Fedora Release Engineering - 1.13a-41 - Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild * Tue Feb 04 2025 Hans de Goede - 1.13a-42 - Fix FTBFS (rhbz#2336251, rhbz#2339853) Package: OpenImageIO-1:2.5.16.0-5.fc42 Old package: OpenImageIO-1:2.5.16.0-4.fc42 Summary: Library for reading and writing images RPMs: OpenImageIO OpenImageIO-devel OpenImageIO-iv OpenImageIO-utils python3-openimageio Size: 18.16 MiB Size change: 814 B Changelog: * Tue Feb 04 2025 S??rgio Basto - 1:2.5.16.0-5 - Rebuild for opencv-4.11.0 Package: YafaRay-3.5.1-47.fc42 Old package: YafaRay-3.5.1-46.fc42 Summary: A free open-source ray-tracing render engine RPMs: YafaRay YafaRay-blender YafaRay-devel YafaRay-lib python3-YafaRay Size: 4.55 MiB Size change: 199.42 KiB Changelog: * Tue Feb 04 2025 S??rgio M. Basto - 3.5.1-47 - Rebuild for opencv-4.11.0 Package
Re: nodejs22 rawhide update unpushed (among others)
On Wed, Feb 5, 2025 at 2:00 PM Kevin Fenzi wrote: > On Wed, Feb 05, 2025 at 01:42:17PM +0100, Fabio Valentini wrote: > > On Wed, Feb 5, 2025 at 1:26 PM Artur Frenszek-Iwicki > > wrote: > > > > > > We're currently in the middle of F42 branching + related freeze. > > > > > > > All builds that will be running at that time for the rawhide will be > > > > canceled and can be resubmitted by maintainers after the branching. > > > > > > > > All rawhide updates that are pending for rawhide will be unpushed. > > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HLQJ7KK4HQ2ROB3HCKAUN3PVZOXIZ6H7/ > > > > Yes, this was intentional. Maybe it would have been good to also add a > > comment to those updates and not just unpush them. > > yeah. Sorry about that. Will add a note next time. > > > Updates that are stuck in "gating" (i.e. in "pending" or "testing" > > state) during the mass branching will end up in a weird state, and > > will always require manual action to fix and end up in a consistent > > state. > > > > In most cases, submitting a new build for rawhide (now F43) and F42 > > should work (assuming the gating failures are taken care of, of > > course). > > Yep. This ^ > I guess it's partly my fault for not noticing that the update was "stuck" but in my case, it's not a single build, but a soname bump and all dependencies that got unpushed. Ugg Thanks, Richard -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora eln compose report: 20250206.n.0 changes
OLD: Fedora-eln-20250205.n.1 NEW: Fedora-eln-20250206.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 3 Dropped packages:0 Upgraded packages: 34 Downgraded packages: 0 Size of added packages: 8.02 MiB Size of dropped packages:0 B Size of upgraded packages: 2.59 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 10.18 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = Package: python-pyqt6-webengine-6.8.0-2.eln145 Summary: Python bindings for Qt6WebEngine RPMs:python3-pyqt6-webengine Size:313.83 KiB Package: qt6-qtquick3dphysics-6.8.2-1.eln146 Summary: Qt6 - Quick3D Physics Libraries and utilities RPMs:qt6-qtquick3dphysics Size:3.13 MiB Package: tk8-1:8.6.15-5.eln146 Summary: The graphical toolkit for the Tcl scripting language, version 8 RPMs:tk8 Size:4.59 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: ImageMagick-1:7.1.1.43-3.eln146 Old package: ImageMagick-1:7.1.1.43-3.eln145 Summary: An X application for displaying and manipulating images RPMs: ImageMagick ImageMagick-c++ ImageMagick-libs Size: 10.81 MiB Size change: 78 B Package: crash-8.0.6-4.eln146 Old package: crash-8.0.6-2.eln144 Summary: Kernel analysis utility for live systems, netdump, diskdump, kdump, LKCD or mcore dumpfiles RPMs: crash crash-devel Size: 17.23 MiB Size change: 550.96 KiB Changelog: * Thu Jan 16 2025 Fedora Release Engineering - 8.0.6-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild * Wed Feb 05 2025 Lianbo Jiang - 8.0.6-4 - Doc: add compilation requirements note in README - Fix "net -a" option on Linux 6.13 and later kernels - kmem: fix the determination of slab page due to invalid page_type - Enhance "kmem -i[=shared]" to display(or not) shared pages - Fix misleading CPU count in display_sys_stats() - arm64: add pac mask to better support gdb stack unwind - x86_64: Fix 'bt -S/-I' segfault issue - Fix build failure in readline lib - tools.c: do not use keywords 'nullptr' as a variable in code - Fix build failure on 32bit machine(i686) Package: dovecot-1:2.3.21.1-5.eln146 Old package: dovecot-1:2.3.21.1-4.eln145 Summary: Secure imap and pop3 server RPMs: dovecot dovecot-devel dovecot-mysql dovecot-pgsql dovecot-pigeonhole Size: 23.57 MiB Size change: 9.63 KiB Changelog: * Wed Feb 05 2025 Michal Hlavinka - 1:2.3.21.1-5 - fix sysusers config file name Package: expect-5.45.4-28.eln146 Old package: expect-5.45.4-27.eln145 Summary: A program-script interaction and testing utility RPMs: expect Size: 1023.96 KiB Size change: 584 B Changelog: * Wed Feb 05 2025 Adam Williamson - 5.45.4-28 - Fix tclsh path for 'example' binaries like unbuffer Package: ffmpeg-7.0.2-12.eln146 Old package: ffmpeg-7.0.2-12.eln145 Summary: A complete solution to record, convert and stream audio and video RPMs: ffmpeg-free libavcodec-free libavdevice-free libavfilter-free libavformat-free libavutil-free libpostproc-free libswresample-free libswscale-free Size: 37.77 MiB Size change: -1.75 KiB Package: galera-26.4.21-1.eln146 Old package: galera-26.4.20-2.eln145 Summary: Synchronous multi-master wsrep provider (replication engine) RPMs: galera Size: 4.85 MiB Size change: 13.92 KiB Changelog: * Wed Feb 05 2025 Michal Schorm - 26.4.21-1 - Rebase to 26.4.21 Package: kernel-6.14.0-0.rc1.20250205git5c8c229261f1.17.eln146 Old package: kernel-6.14.0-0.rc1.20250204git0de63bb7d919.16.eln145 Summary: The Linux kernel RPMs: kernel kernel-64k kernel-64k-core kernel-64k-debug kernel-64k-debug-core kernel-64k-debug-devel kernel-64k-debug-devel-matched kernel-64k-debug-modules kernel-64k-debug-modules-core kernel-64k-debug-modules-extra kernel-64k-devel kernel-64k-devel-matched kernel-64k-modules kernel-64k-modules-core kernel-64k-modules-extra kernel-64k-uki-virt kernel-64k-uki-virt-addons kernel-abi-stablelists kernel-core kernel-cross-headers kernel-debug kernel-debug-core kernel-debug-devel kernel-debug-devel-matched kernel-debug-modules kernel-debug-modules-core kernel-debug-modules-extra kernel-debug-uki-virt kernel-debug-uki-virt-addons kernel-devel kernel-devel-matched kernel-doc kernel-headers kernel-modules kernel-modules-core kernel-modules-extra kernel-rt kernel-rt-core kernel-rt-debug kernel-rt-debug-core kernel-rt-debug-devel kernel-rt-debug-kvm kernel-rt-debug-modules kernel-rt-debug-modules-core kernel-rt-debug-modules-extra kernel-rt-devel kernel-rt-kvm kernel-rt-modules kernel-rt-modules-core kernel-rt-modules-extra kernel-tools kernel-tools-libs kernel-tools-libs-devel kernel-uki-virt kernel-uki-virt-addons kernel-zf
Re: Need help with pybind11 c++ compilation warning/error
On 2/5/25 01:00, Cristian Le via devel wrote:
On 5 February 2025 06:17:01 CET, Orion Poplawski wrote:
cc1plus: all warnings being treated as errors
gmake[2]: *** [libmambapy/CMakeFiles/bindings.dir/build.make:96:
libmambapy/CMakeFiles/bindings.dir/src/libmambapy/bindings/legacy.cpp.o] Error 1
I'm guessing 'SR.32262' is some kind of temporary variable. libmamba has taken
the (perhaps admirable?) step of compiling with -Werror so it fails.
The errors are in mamba's code base afaict.
You should disable warnings as error, enforce C++ standard in CMakeLists.txt,
ask upstream about C++17 warnings, or all the above.
But just to be sure it's gcc15 related can you also target F41?
I'm not entirely sure I understand all of your suggestions. I did
disable -Werror, but that led to the issue I reported in my other email.
I tried compiling with cmake -DCMAKE_CXX_STANDARD=17 ... but that did
not appear to make any difference.
I have reported issues upstream:
https://github.com/mamba-org/mamba/issues/3791 (the uninitialized warning)
https://github.com/mamba-org/mamba/issues/3809 (the python abort)
I'll note here as well that I see the same python abort in F41. The
uninitialized warning goes away though, and I get this instead:
/builddir/build/BUILD/libmamba-2.0.6-build/mamba-2.0.6/libmambapy/src/libmambapy/bindings/path_caster.hpp:17:16:
warning: type ‘struct type_caster’ violates the C++ One Definition Rule
[-Wodr]
17 | struct type_caster :
path_caster
|^
/usr/include/pybind11/cast.h:38:7: note: a type with different bases is
defined in another translation unit
38 | class type_caster : public type_caster_base {};
| ^
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane or...@nwra.com
Boulder, CO 80301 https://www.nwra.com/
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
bin/sbin merge: Are we going to change kconfig MODPROBE_PATH?
https://github.com/torvalds/linux/blob/5c8c229261f14159b54b9a32f12e5fa89d88b905/kernel/module/Kconfig#L416 This defaults to "/sbin/modprobe". Should it be changed to "/usr/bin/modprobe"? A few possible reasons: (1) Bad RPM installers that don't run scripts, specifically the filesystem.spec script. (This is the case that broke for me.) (2) I suspect some race between needing to modprobe modules are running the filesystem.spec script, even in a well-behaved RPM install. (3) Extremely small speed increase not having to follow a symlink? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nodejs22 rawhide update unpushed (among others)
We're currently in the middle of F42 branching + related freeze. > All builds that will be running at that time for the rawhide will be > canceled and can be resubmitted by maintainers after the branching. > > All rawhide updates that are pending for rawhide will be unpushed. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HLQJ7KK4HQ2ROB3HCKAUN3PVZOXIZ6H7/ A.FI. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Rust SIG Spring Cleaning - 2025 Edition
Hi all, In an effort to keep the stack of Rust crate packages in good shape in Fedora, I'm regularly checking for library-only packages that have been unused for extended periods of time (usually 365+ days, i.e. two full release cycles). Dropping packages like this reduces the maintenance effort overall due to less dense dependency graphs - making updates for remaining Rust packages easier. Additionally, many of these crates were either packaged for reasons that are no longer valid (i.e. they were a dependency of something in the past, but are no longer being depended on now), they are obsolete and replaced by other crates "upstream", or they were packaged as part of an effort to ship a specific application, but that effort has since been abandoned. These library-only (source-only) packages for Rust crates have been unused for 365+ days (by main maintainer): albertlarsan68: rust-fend-core atim: rust-nparse blinxen:rust-symlink dcavalca: rust-rusttype decathorpe: rust-ghost, rust-smallvec, rust-unidecode leo:rust-colorgrad, rust-enum-display-derive, rust-euclid salimma:rust-nom-supreme, rust-vec1, rust-xcb thunderbirdtr: rust-safetensors Some packages are omitted from this list because there are still valid reasons to keep them (for example, packages that are still pending review depend on them, or they will be needed for other pending crate updates). I looked at package review tickets in an attempt to figure out why these packages were originally packaged, but that wasn't always possible (because it wasn't mentioned in the ticket and / or the review bug didn't block any other bugs): colorgrad: ? enum-display-derive:? euclid: ? fend-core: ? ghost: used to be dependency of something, no longer is nom-supreme:? nparse: used to be dependency of something, no longer is rusttype: ? (blocked "Fedora Asahi Remix: touchbar support") safetensors:? smallvec: used to be dependency of something, no longer is suggest:? (potentially as a dependency of "zellij") symlink:used to be dev-dependency of gix-worktree (now removed) unidecode: used to be dependency of fake (replaced with deunicode) vec1: ? xcb:used to be dependency of x11-clipboard (replaced with x11rb) If there is a package in this list that is still needed for something that you're working on, please let me know soon, and I will add it to the list here: https://pagure.io/ironthree/fedora-rust-sig-leaf-check/blob/main/f/reasons.txt Otherwise I plan to retire any Rust packages that are - library-only / source-only and - have been unused leaf packages for 365+ days and - have no documented reason for why they are still needed before the F42 Beta Freeze takes effect. Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
nodejs22 rawhide update unpushed (among others)
Hello list, I've just received a notification that my nodejs22 update [1] to rawhide was unpushed by jnsamyak. Looking around, it seems that's not the only update affected (for example, [2]). [1]: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1df6d10dfc [2]: https://bodhi.fedoraproject.org/updates/FEDORA-2025-326f30cbd8 Given that update to the same version is now in F41 testing repo, there is now a potential for regression. Can I get some more context for this action? Why were these updates unpushed? What followup is needed – new build, re-submit the update manually again, …? Thanks in advance for any info. -- Jan Staněk Software Engineer, Red Hat jsta...@redhat.com irc: jstanek signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: nodejs22 rawhide update unpushed (among others)
On Wed, Feb 5, 2025 at 1:26 PM Artur Frenszek-Iwicki wrote: > > We're currently in the middle of F42 branching + related freeze. > > > All builds that will be running at that time for the rawhide will be > > canceled and can be resubmitted by maintainers after the branching. > > > > All rawhide updates that are pending for rawhide will be unpushed. > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/HLQJ7KK4HQ2ROB3HCKAUN3PVZOXIZ6H7/ Yes, this was intentional. Maybe it would have been good to also add a comment to those updates and not just unpush them. Updates that are stuck in "gating" (i.e. in "pending" or "testing" state) during the mass branching will end up in a weird state, and will always require manual action to fix and end up in a consistent state. In most cases, submitting a new build for rawhide (now F43) and F42 should work (assuming the gating failures are taken care of, of course). Fabio -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: copy-jdk-configs
On Sun, Feb 2, 2025 at 4:20 PM Orion Poplawski wrote: > > copy-jdk-configs was just retired with this note: > > Paralel installs are going to be remove from JDK. Package existed only > to support that > > but some packages still require it: > > java-21-openjdk-headless-1:21.0.6.0.7-1.fc42.x86_64 > java-21-openjdk-headless-fastdebug-1:21.0.6.0.7-1.fc42.x86_64 > java-21-openjdk-headless-slowdebug-1:21.0.6.0.7-1.fc42.x86_64 > java-latest-openjdk-headless-1:23.0.2.0.7-1.rolling.fc42.x86_64 > java-latest-openjdk-headless-fastdebug-1:23.0.2.0.7-1.rolling.fc42.x86_64 > java-latest-openjdk-headless-slowdebug-1:23.0.2.0.7-1.rolling.fc42.x86_64 > > This is broken the install of octave (and I imagine others) that require > java-21-openjdk-headless. Is this still a problem? From what I can see java-21-openjdk was updated to no longer require copy-jdk-configs. -- Mikolaj > > -- > Orion Poplawski > he/him/his - surely the least important thing about me > IT Systems Manager 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane or...@nwra.com > Boulder, CO 80301 https://www.nwra.com/ > > -- > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: bin/sbin merge: Are we going to change kconfig MODPROBE_PATH?
On Wed, Feb 05, 2025 at 12:03:21PM +, Richard W.M. Jones wrote: > https://github.com/torvalds/linux/blob/5c8c229261f14159b54b9a32f12e5fa89d88b905/kernel/module/Kconfig#L416 > > This defaults to "/sbin/modprobe". Should it be changed to > "/usr/bin/modprobe"? > > A few possible reasons: > > (1) Bad RPM installers that don't run scripts, specifically the > filesystem.spec script. (This is the case that broke for me.) Can you expand a bit on this? All installs with 'rpm' should DTRT. > (2) I suspect some race between needing to modprobe modules are > running the filesystem.spec script, even in a well-behaved RPM > install. Indeed, there is a race on split systems, during the first upgrade from a package with /usr/sbin/modprobe to a package with /usr/bin/modprobe. The window is between the %postun phase of the old package and the %posttrans scriptlets in filesystem to create the symlink. But I think this can be ignored… It's a one-time occurence and would require new drivers to requested in in that window. In general, when stuff is in the middle of the upgrade, some minor transitory issues are expected. It's very hard to make those completely go away with our non-transactional system and that's why we officially recommend offline upgrades. > (3) Extremely small speed increase not having to follow a symlink? The downside of changing the path is that systems with the old path would stop working. It's impossible to ensure the version of the userspace from the kernel. Because of that, I'd vote against changing the path as split systems are supported (i.e. at least until F41 goes EOL). Zbyszek -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
