Re: bin-sbin merge rebuild
* Zbigniew Jędrzejewski-Szmek: > glibc If we rebuild glibc, should we do a second rebuild into your side tag? Thanks, Florian -- ___ 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: incompatible update of libkdumpfile heading to Rawhide
On Thu, 2025-01-02 at 12:52 -0600, Michel Lind wrote: > On Thu, Jan 02, 2025 at 12:12:10PM -0600, Michel Lind wrote: > > libkdumpfile 0.5.4 => 0.5.5 involves bumping its soname from 10 to > > 12 > > (not quite semantic versioned, this one). > > > > This is also the last release with the deprecated Python bindings, > > which > > no other package in Fedora repos currently use, and those are > > already > > removed upstream in favor of `pykdumpfile`: > > > > COPR with libkdumpfile and python-drgn rebuilt for Rawhide and ELN: > > https://copr.fedorainfracloud.org/coprs/salimma/libkdumpfile-0.5.5/packages/ > > PR: https://src.fedoraproject.org/rpms/libkdumpfile/pull-request/3 > > I'll merge and land on Jan 9 unless there are unanticipated issues. > This is merged and built: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5a36d3f769 Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 signature.asc Description: This is a digitally signed message part -- ___ 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: rubberband ABI bump for Rawhide (2 -> 3)
On Wed, 2025-01-08 at 23:03 -0600, Michel Lind wrote: > On Tue, Dec 03, 2024 at 04:29:25PM -0800, Michel Lind wrote: > > Hi all, > > > > This PR updates rubberband from v3 to v4; in the process the > > soversion > > is bumped from 2 to 3: > > > > https://src.fedoraproject.org/rpms/rubberband/pull-request/11#request_diff > > > > Per the upstream announcement the API should be backward compatible > > > > https://www.breakfastquay.com/news/20241025.html > > > > This is the one-week heads up notice per the update policy: > > https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide > > > > I'll follow up later today or tomorrow with a COPR with dependent > > packages rebuilt to verify this; if you maintain one of the > > packages in > > the list, let me know if you prefer building the update yourself > > between > > now and next week. > > > Life happens, so I only got round to doing the COPR now: > https://copr.fedorainfracloud.org/coprs/salimma/rubberband4/builds/ > > > I'll do another update in a week announcing the side tag I'm using > > for > > this, and will rebuild all the packages where the maintainers have > > not > > opted out. > Side tag: f42-build-side-103298 > > Nobody opted out so I'll be doing the actual side tag rebuilds > tomorrow. > See comments in line for the COPR rebuild results > > > Affected packages: > > > > $ fedrq whatrequires -P rubberband-devel > > > > ardour6-6.9.0- > > 23.fc41.src > > > ardour7-7.5.0-11.fc41.src > > ardour8-8.10.0-1.fc42.src > > denemo-2.6.0-15.fc42.src > > easyeffects-7.1.9-2.fc42.src > > ffmpeg-7.0.2-8.fc42.src > > mlt-7.28.0-4.fc42.src > > mpv-0.39.0-1.fc42.src > > mpv-devel-0.39.0-1.fc42.aarch64 > > muse-1:4.2.1-5.fc42.src > > qmplay2-24.06.16-3.fc42.src > > qtractor-1.2.0-1.fc42.src > > samplv1-0.9.91-2.fc41.src > > sonic-visualiser-5.0-2.fc42.src > These build fine > > > sooperlooper-1.7.3-24.fc40.src > Already FTBFS - https://bugzilla.redhat.com/show_bug.cgi?id=2301283 > > Best regards, > rubberband 4.0.0 and rebuilt packages are now built: https://bodhi.fedoraproject.org/updates/FEDORA-2025-99b5db319c sooperlooper has been FTBFS for a really long time due to an integer conversion issue https://kojipkgs.fedoraproject.org//work/tasks/2864/127712864/build.log I can put up a PR if I can get it to build but it probably needs a new maintainer (releng is the top committer, it's been auto-rebuilt for years) https://src.fedoraproject.org/rpms/sooperlooper/stats#authors Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 signature.asc Description: This is a digitally signed message part -- ___ 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: Self-reintroduction, reflections, and so forth
On Wed, 2025-01-08 at 20:43 -0800, Brendan Conoboy wrote: > Over the last few months on chat.fp.o and at conferences I have > started joining into conversations- listening, asking questions, > making assertions, telling bad jokes. All this activity has led to a > recurring question by many people in the community, “uhh, who are > you?” > > ... > But this isn’t just an introduction, this is a reintroduction. My > first foray into the Fedora community, beyond just running Fedora, > was in 2012 when my team at Red Hat started to explore the potential > for ARM servers. We, with many of you, bootstrapped armv7hl, then > aarch64. We started with a Seneca College partnership, we gave away > hardware, we made ugly uboot hacks, ported hundreds of packages, > helped establish the Linaro Enterprise Group to do more ports & > standardization, and solved seemingly thousands of circular > dependencies- and hired a bunch of great contributors along the way, > folks like Marcin Juszkiewicz and Paul Whalen. Several of us took > what we learned from the experience and replicated the work inside > Red Hat with RHEL 7, first for ppc64le, then aarch64- two > architectures that are mainstream in RHEL today, but scarcely existed > a decade ago. For me that evolved into driving general RHEL > development as an individual, then management, then last year I had > the opportunity to come back to support Red Hat’s Linux communities > in general and Fedora in particular. > Ahh, the perfect person to deal with our s390x capacity crunch ;) > I think it’s fair to say that most of the RHEL management team has, > as a whole, tended to be hands-off in Fedora’s affairs. There are > some notable exceptions of course, but on average, most people > working as managers are less involved in Fedora. There’s no written > rule about this, so for my part I’ve inferred that most managers > don’t think they have a lot of value to contribute compared to the > people who they manage who are engaged in Fedora. Even in writing > this blog I feel apprehensive: do I have anything to say people want > to hear? Maybe just one thing… > Thank you for engaging! I agree with your analysis, and happen to think that more engagement from management - done properly - is a good thing. After all certain issues require investment to fix, and Fedora depends on Red Hat for its infrastructure... Looking forward to your next posts, and future collaborations, Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 signature.asc Description: This is a digitally signed message part -- ___ 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: libnova: announcing soname bump
On Mon, 2025-01-06 at 17:49 +0100, Fabio Valentini wrote: > On Mon, Jan 6, 2025 at 10:05 AM Mattia Verga via devel > wrote: > > > > Despite 0.16 being available as tag in repository since 2015, > > libnova > > was never updated and it's still 0.15 in Fedora. > > > > I have notified the package maintainer long ago [1], but I never > > got a > > reply. So I plan to push an update as provenpackager, which will > > include > > a soname bump (from libnova-0.15.so.0 to libnova-0.16.so.0) and > > rebuild > > all dependent packages in a side-tag for Rawhide. The list of > > affected > > packages is: > > Please don't use provenpackager privileges for this kind of thing. > If the maintainer is truly unresponsive, that's what the unresponsive > maintainer process is for. > You can even commit rights on the package within a week or two, if > some conditions are met. I have the same problem with lxc and lxcfs all maintainers are more or less unresponsive , I did the PR, I waited, I asked and finally I used PP power to merge it and built it [1] . My point here is while we have maintainers that maintain the package and don't like that proven packagers change it, we have many others which don't even reply , so is not easy decide what to do . [1] https://src.fedoraproject.org/rpms/lxcfs/pull-request/1 merged by me https://src.fedoraproject.org/rpms/lxcfs/pull-request/2 https://src.fedoraproject.org/rpms/lxc/pull-request/3 -- 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
Fedora eln compose report: 20250110.n.0 changes
OLD: Fedora-eln-20250109.n.1 NEW: Fedora-eln-20250110.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 31 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded packages: 2.87 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 427.55 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: clevis-21-9.eln144 Old package: clevis-21-8.eln144 Summary: Automated decryption framework RPMs: clevis clevis-dracut clevis-luks clevis-pin-pkcs11 clevis-systemd clevis-udisks2 Size: 584.66 KiB Size change: 2.19 KiB Changelog: * Tue Jan 07 2025 Sergio Arroutbi - 21-9 - Include packages required by clevis-pin-pkcs11 Package: diffstat-1.67-1.eln144 Old package: diffstat-1.66-2.eln144 Summary: A utility which provides statistics based on the output of diff RPMs: diffstat Size: 177.91 KiB Size change: -5.25 KiB Changelog: * Thu Jan 09 2025 Tim Waugh - 1.67-1 - Update to 1.67 (#2325242) Package: dnf5-5.2.8.1-4.eln144 Old package: dnf5-5.2.8.1-3.eln144 Summary: Command-line package manager RPMs: dnf5 dnf5-devel dnf5-plugin-automatic dnf5-plugins libdnf5 libdnf5-cli libdnf5-cli-devel libdnf5-devel libdnf5-plugin-actions libdnf5-plugin-rhsm perl-libdnf5 perl-libdnf5-cli python3-libdnf5 python3-libdnf5-cli python3-libdnf5-python-plugins-loader ruby-libdnf5 ruby-libdnf5-cli Size: 29.80 MiB Size change: 44.69 KiB Changelog: * Thu Jan 09 2025 Petr Pisar - 5.2.8.1-4 - Fix plural form in "Replacing N packages" message - Fix reporting disk space to be freed on a pure package removal (GH #1938) - Fix a library name in libdnf5-cli pkg-config file - Fix expanding "{body}" in command_format option of automatic plugin (GH #1951) - Display remaining time as nonnegative number (bug #2332931) - Document removal of "userinstalled" subcommand (bug #2335257) - Own /var/lib/dnf by libdnf5 (bug #2332856) - Fix a memory leak in copr plugin - Fix a crash when reporting metadata download errors (GH #1919) - Fix end-of-lines in messages sent by email emitter of automatic plugin (bug #2335508) Package: ffmpeg-7.0.2-9.eln144 Old package: ffmpeg-7.0.2-8.eln144 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.18 MiB Size change: -788.78 KiB Changelog: * Thu Jan 09 2025 Michel Lind - 7.0.2-9 - Rebuilt for rubberband 4 Package: glibc-2.40.9000-27.eln144 Old package: glibc-2.40.9000-26.eln144 Summary: The GNU libc libraries RPMs: glibc glibc-all-langpacks glibc-benchtests glibc-common glibc-devel glibc-doc glibc-gconv-extra glibc-langpack-aa glibc-langpack-af glibc-langpack-agr glibc-langpack-ak glibc-langpack-am glibc-langpack-an glibc-langpack-anp glibc-langpack-ar glibc-langpack-as glibc-langpack-ast glibc-langpack-ayc glibc-langpack-az glibc-langpack-be glibc-langpack-bem glibc-langpack-ber glibc-langpack-bg glibc-langpack-bhb glibc-langpack-bho glibc-langpack-bi glibc-langpack-bn glibc-langpack-bo glibc-langpack-br glibc-langpack-brx glibc-langpack-bs glibc-langpack-byn glibc-langpack-ca glibc-langpack-ce glibc-langpack-chr glibc-langpack-ckb glibc-langpack-cmn glibc-langpack-crh glibc-langpack-cs glibc-langpack-csb glibc-langpack-cv glibc-langpack-cy glibc-langpack-da glibc-langpack-de glibc-langpack-doi glibc-langpack-dsb glibc-langpack-dv glibc-langpack-dz glibc-langpack-el glibc-langpack-en glibc-langpack-eo glibc-langpack-es glibc-langpack-et glibc-langpack-eu glibc-langpack-fa glibc-langpack-ff glibc-langpack-fi glibc-langpack-fil glibc-langpack-fo glibc-langpack-fr glibc-langpack-fur glibc-langpack-fy glibc-langpack-ga glibc-langpack-gd glibc-langpack-gez glibc-langpack-gl glibc-langpack-gu glibc-langpack-gv glibc-langpack-ha glibc-langpack-hak glibc-langpack-he glibc-langpack-hi glibc-langpack-hif glibc-langpack-hne glibc-langpack-hr glibc-langpack-hsb glibc-langpack-ht glibc-langpack-hu glibc-langpack-hy glibc-langpack-ia glibc-langpack-id glibc-langpack-ig glibc-langpack-ik glibc-langpack-is glibc-langpack-it glibc-langpack-iu glibc-langpack-ja glibc-langpack-ka glibc-langpack-kab glibc-langpack-kk glibc-langpack-kl glibc-langpack-km glibc-langpack-kn glibc-langpack-ko glibc-langpack-kok glibc-langpack-ks glibc-langpack-ku glibc-langpack-kw glibc-langpack-ky glibc-langpack-lb glibc-langpack-lg glibc-langpack-li glibc-langpack-lij glibc-langpack-ln glibc-langpack-lo glibc-langpack-lt glibc-langpack-lv glibc-langpack
Re: [Fedocal] Reminder meeting : ELN SIG
On 1/9/25 07:00, yselk...@redhat.com wrote: Dear all, You are kindly invited to the meeting: ELN SIG on 2025-01-10 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: * New meeting schedule * New SIG member: Johnny Hughes * Review https://github.com/fedora-eln/eln/issues -- Yaakov Selkowitz Principal Software Engineer, Emerging RHEL Red Hat, Inc. -- ___ 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 Thu, Jan 9, 2025 at 3:14 PM Zbigniew Jędrzejewski-Szmek wrote: > I want to make another attempt at the bin-sbin merge tomorrow. > See [0, 1, 2] for the general description and history. [snip] > Packages to build: > libguestfs > nbdkit It's that time of year where side tags step on each other. As mentioned on the mailing list a few hours ago, I am in the process of rebuilding the OCaml world for OCaml 5.3.0. That includes the 2 packages listed above. I already did test builds of all packages, so I'm not expecting any trouble, but the number of packages is large enough that it will probably take me another 20-24 hours to finish all of the builds. For a little more fun the hivex package, which libguestfs depends on, is already in a side tag for a ruby update. I need to rebuild hivex and then libguestfs in the OCaml side tag, but am waiting for the ruby side tag to be merged back in. Alternatively, I could leave hivex and libguestfs out of the OCaml rebuilds and merge the side tag as soon as I am done tomorrow, leaving both packages broken in Rawhide, then after the ruby side tag is merged back in, you could do this work, but add hivex to your list of packages to build. That would fix both of them OCaml-wise in passing. What's your preference? -- Jerry James http://www.jamezone.org/ -- ___ 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: zswap: should we use zsmalloc as default allocator?
On Wed, Jan 8, 2025, at 3:29 AM, Vitaly Zaitsev via devel wrote: > On 02/01/2025 15:00, Dmitry Konishchev wrote: >> Should this default be changed? > > I know this is not you're looking for, but you can use the zswap-cli > package to manage zswap kernel module. > > You can edit the /etc/zswap-cli/zswap-cli.conf configuration file to set > any supported kernel module options, and then enable the systemd unit: > > sudo systemctl enable --now zswap-cli.service Oh cool, so I should use that instead of kernel parameters. Do I still need to enable zswap with the kernel param? Or can it all be done by the service unit? -- Chris Murphy -- ___ 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
Help needed with sooperlooper Re: Heads-up: rubberband ABI bump for Rawhide (2 -> 3)
On Thu, 2025-01-09 at 15:59 -0600, Michel Lind wrote: > > sooperlooper has been FTBFS for a really long time due to an integer > conversion issue > https://kojipkgs.fedoraproject.org//work/tasks/2864/127712864/build.log > > I can put up a PR if I can get it to build but it probably needs a > new > maintainer (releng is the top committer, it's been auto-rebuilt for > years) > > https://src.fedoraproject.org/rpms/sooperlooper/stats#authors > If anyone is interested, some notes: per the latest attempt to rebuild the current source (see Koji link above) it's failing with an integer coercion issue We're currently at version 1.7.3; 1.7.8 is the latest on the website and GitHub has 1.7.9 that is two years newer 1.7.8 still has the same issue 1.7.9 - we can't build easily because the github tarball does not have a configure script, and autoreconf barfed because upstream uses some really old macros So if someone wants to give this package some TLC - that'd be great, I probably don't have the time to spend on this right now. Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 signature.asc Description: This is a digitally signed message part -- ___ 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
Jerry James wrote on 2025/01/10 8:10: On Thu, Jan 9, 2025 at 3:14 PM Zbigniew Jędrzejewski-Szmek wrote: I want to make another attempt at the bin-sbin merge tomorrow. See [0, 1, 2] for the general description and history. [snip] Packages to build: libguestfs nbdkit It's that time of year where side tags step on each other. As mentioned on the mailing list a few hours ago, I am in the process of rebuilding the OCaml world for OCaml 5.3.0. That includes the 2 packages listed above. I already did test builds of all packages, so I'm not expecting any trouble, but the number of packages is large enough that it will probably take me another 20-24 hours to finish all of the builds. For a little more fun the hivex package, which libguestfs depends on, is already in a side tag for a ruby update. I need to rebuild hivex and then libguestfs in the OCaml side tag, but am waiting for the ruby side tag to be merged back in. Alternatively, I could leave hivex and libguestfs out of the OCaml rebuilds and merge the side tag as soon as I am done tomorrow, leaving both packages broken in Rawhide, then after the ruby side tag is merged back in, you could do this work, but add hivex to your list of packages to build. That would fix both of them OCaml-wise in passing. What's your preference? Just noting that ruby3.4 side tag is already merged into rawhide tree. https://bodhi.fedoraproject.org/updates/FEDORA-2025-dbf6ae505d Regards, Mamoru -- ___ 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 rebuild
Hi folks, I want to make another attempt at the bin-sbin merge tomorrow. See [0, 1, 2] for the general description and history. I tried to do the merge last year, but there were various failures and the attempt was reverted. Those issues have been fixed, so I'll try again, following the same plan as before: 1. In a side tag: rebuild filesystem with merged_sbin=1 2. In a side tag: rebuild rpm with merged_sbin=1 3. In a side tag: rebuild various packages, list below 4. Create a bodhi update and wait for the CI results Depending on the results, a decision to either merge the update, or do some more builds, or drop the side tag and revert the changes in filesystem and rpm will need to be made. [0] https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3562IKYYO4YLC5IPS3WSV3DNQXW3V7QG/ [2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/EOKNNAMSTPNFVKU3WQ3R42HFXKE6QLJS/ Packages to build: filesystem rpm bind chkconfig coreutils cyrus-sasl device-mapper-multipath device-mapper-persistent-data dmidecode dosfstools e2fsprogs efibootmgr esmtp exim fping glibc glusterfs gnupg2 hdparm hfsutils httpd initscripts iproute iptables iputils kexec-tools kmod libcap libguestfs libreswan libselinux lm_sensors lvm2 msmtp msr-tools nbdkit net-tools nfs-utils nilfs-utils ntpsec ocfs2-tools opensmtpd pciutils policycoreutils postfix ppp procps-ng psmisc rpcbind sanlock sendmail shadow-utils smartmontools tcpdump util-linux v4l-utils xfsprogs 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: Self-reintroduction, reflections, and so forth
On Thu, Jan 9, 2025 at 3:53 PM Michel Lind wrote: > On Wed, 2025-01-08 at 20:43 -0800, Brendan Conoboy wrote: > > Over the last few months on chat.fp.o and at conferences I have > > started joining into conversations- listening, asking questions, > > making assertions, telling bad jokes. All this activity has led to a > > recurring question by many people in the community, “uhh, who are > > you?” > > > > > ... > > But this isn’t just an introduction, this is a reintroduction. My > > first foray into the Fedora community, beyond just running Fedora, > > was in 2012 when my team at Red Hat started to explore the potential > > for ARM servers. We, with many of you, bootstrapped armv7hl, then > > aarch64. We started with a Seneca College partnership, we gave away > > hardware, we made ugly uboot hacks, ported hundreds of packages, > > helped establish the Linaro Enterprise Group to do more ports & > > standardization, and solved seemingly thousands of circular > > dependencies- and hired a bunch of great contributors along the way, > > folks like Marcin Juszkiewicz and Paul Whalen. Several of us took > > what we learned from the experience and replicated the work inside > > Red Hat with RHEL 7, first for ppc64le, then aarch64- two > > architectures that are mainstream in RHEL today, but scarcely existed > > a decade ago. For me that evolved into driving general RHEL > > development as an individual, then management, then last year I had > > the opportunity to come back to support Red Hat’s Linux communities > > in general and Fedora in particular. > > > Ahh, the perfect person to deal with our s390x capacity crunch ;) > Yes! Actually, I think Kevin and IT just applied a bandaid that has made a significant improvement in wait times. That's the thing about utilization, it's in the domain of queue theory where linear increases in utilization lead to exponential wait increases in wait time. Currently Fedora is using part of a z16 in one of our data centers and there isn't another one available for our use. If we want to increase capacity further our next easiest avenue is to look for space on a z15 or make use of IBM's Cloud where space is available. We've generally tried to avoid using clouds for builders since koji's architecture isn't well suited to it, but I'm hopeful as we find ways to take advantage of konflux we can make use of external clouds for demand bursts. I'm old so I mostly think of builders as the thing people care about, but if other workloads are being held back that are amenable to cloud semantics or where we don't currently need z16 we can explore that. > I think it’s fair to say that most of the RHEL management team has, > > as a whole, tended to be hands-off in Fedora’s affairs. There are > > some notable exceptions of course, but on average, most people > > working as managers are less involved in Fedora. There’s no written > > rule about this, so for my part I’ve inferred that most managers > > don’t think they have a lot of value to contribute compared to the > > people who they manage who are engaged in Fedora. Even in writing > > this blog I feel apprehensive: do I have anything to say people want > > to hear? Maybe just one thing… > > > Thank you for engaging! I agree with your analysis, and happen to think > that more engagement from management - done properly - is a good thing. > After all certain issues require investment to fix, and Fedora depends > on Red Hat for its infrastructure... > > Looking forward to your next posts, and future collaborations, > Cheers! -- Brendan Conoboy / Community Linux Engineering / Red Hat, Inc. -- ___ 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
SPDX Statistics - 161 packages remaining
Hot news: - New version of upstream SPDX list has been released https://github.com/spdx/license-list-XML/releases/tag/v3.26.0 Most of the licenses were added due to Fedora. Three weeks (because of Christmas) ago we had: * 24368spec files in Fedora * 31025license tags in all spec files * 224 tags are not SPDX compliant (number from line bellow minus packages with LicenseRef-Callaway-*) * 2475 tags have not been converted to SPDX yet * 21 tags can be trivially converted using `license-fedora2spdx` * Progress: 99.28% ░█100% ELN subset: 62 out of 2314 packages are not converted yet (progress 97.32%) Today we have: * 24379spec files in Fedora * 30988license tags in all spec files * 161 tags are not SPDX compliant (number from line bellow minus packages with LicenseRef-Callaway-*) * 2325 tags have not been converted to SPDX yet * 21 tags can be trivially converted using `license-fedora2spdx` * Progress: 99.48% ░█100% ELN subset: 61 out of 2316 packages are not converted yet (progress 97.37%) Graph of these data with the burndown chart: https://docs.google.com/spreadsheets/d/1QVMEzXWML-6_Mrlln02axFAaRKCQ8zE807rpCjus-8s/edit?usp=sharing The list of packages needed to be converted is here: https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final.txt List by package maintainers is here https://pagure.io/copr/license-validate/blob/main/f/packages-without-spdx-final-maintainers.txt Packages that are neither in SPDX nor in Callaway format (highest priority for now) - 55 packages: https://pagure.io/copr/license-validate/blob/main/f/neither-nor-remaining-packagers.txt Most of such packages has open issue in fedora-license-data. A lot of them are waiting for SPDX to approved the license and assign ID. New version of fedora-license-data has been released. With: 3 new licenses and several public domain or ultrapermissive dedications 12 licenses are waiting to be reviewed by SPDX.org (and then to be added to fedora-license-data) https://gitlab.com/fedora/legal/fedora-license-data/-/issues/?label_name%5B%5D=SPDX%3A%3Ablocked Legal docs and especially https://docs.fedoraproject.org/en-US/legal/allowed-licenses/ was updated too. If your package does not have neither git-log entry nor spec-changelog entry mentioning SPDX and you know your license tag matches SPDX formula, you can put your package on ignore list https://pagure.io/copr/license-validate/blob/main/f/ignore-packages.txt Either pull-request or direct email to me is fine. Miroslav -- ___ 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: Retiring GlusterFS in Fedora 42. First Notice
On Thu, 9 Jan 2025 at 12:07, Richard W.M. Jones wrote: > On Sun, Jan 05, 2025 at 02:07:11PM +0300, Benson Muite wrote: > > > > > > On Sat, Jan 4, 2025, at 9:28 PM, Kaleb Keithley wrote: > > > Are you a packager? > > > > Yes > > > > What's your FAS ID? > > > > Fed500 > > Note that the entire virt stack (just about) depends on gluster, so > please coordinate with us if you push any breaking change. We may > need to rebuild quite a few dependent packages. Easiest way is to > email 'qemu-maintain...@fedoraproject.org'. > > Although I suppose since upstream development is dead, maybe that > won't be very likely ... > While it doesn't affect things from a build perspective, but could gluster be possibly be made recommended instead of required at the libvirt-daemon-driver-storage level? -- ___ 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: Plans for OCaml 5.2/5.3
On Wed, Jan 8, 2025 at 7:04 AM Richard W.M. Jones wrote: > OCaml 5.3.0 was finally released today, but for various reasons I > won't be able to handle this until February. Richard and I talked about this, and I am going to run the OCaml rebuilds this time around. I will start the OCaml 5.3.0 builds today in side tag f42-build-side-103318. I will delay touching mostly non-OCaml packages, like plplot and xen, until the end to minimize the time window when these rebuilds might clash with other builds. I will reply to this thread when the builds are ready to merge into Rawhide. -- Jerry James http://www.jamezone.org/ -- ___ 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: rubberband ABI bump for Rawhide (2 -> 3)
On Tue, Dec 03, 2024 at 04:29:25PM -0800, Michel Lind wrote: > Hi all, > > This PR updates rubberband from v3 to v4; in the process the soversion > is bumped from 2 to 3: > > https://src.fedoraproject.org/rpms/rubberband/pull-request/11#request_diff > > Per the upstream announcement the API should be backward compatible > > https://www.breakfastquay.com/news/20241025.html > > This is the one-week heads up notice per the update policy: > https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide > > I'll follow up later today or tomorrow with a COPR with dependent > packages rebuilt to verify this; if you maintain one of the packages in > the list, let me know if you prefer building the update yourself between > now and next week. > Life happens, so I only got round to doing the COPR now: https://copr.fedorainfracloud.org/coprs/salimma/rubberband4/builds/ > I'll do another update in a week announcing the side tag I'm using for > this, and will rebuild all the packages where the maintainers have not > opted out. Side tag: f42-build-side-103298 Nobody opted out so I'll be doing the actual side tag rebuilds tomorrow. See comments in line for the COPR rebuild results > Affected packages: > > $ fedrq whatrequires -P rubberband-devel > > ardour6-6.9.0-23.fc41.src > > ardour7-7.5.0-11.fc41.src > ardour8-8.10.0-1.fc42.src > denemo-2.6.0-15.fc42.src > easyeffects-7.1.9-2.fc42.src > ffmpeg-7.0.2-8.fc42.src > mlt-7.28.0-4.fc42.src > mpv-0.39.0-1.fc42.src > mpv-devel-0.39.0-1.fc42.aarch64 > muse-1:4.2.1-5.fc42.src > qmplay2-24.06.16-3.fc42.src > qtractor-1.2.0-1.fc42.src > samplv1-0.9.91-2.fc41.src > sonic-visualiser-5.0-2.fc42.src These build fine > sooperlooper-1.7.3-24.fc40.src Already FTBFS - https://bugzilla.redhat.com/show_bug.cgi?id=2301283 Best regards, -- _o) Michel Lind _( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2 README: https://fedoraproject.org/wiki/User:Salimma#README 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: Self-reintroduction, reflections, and so forth
On Wed, Jan 08, 2025 at 08:43:55PM -0800, Brendan Conoboy wrote: > Having come full circle, starting a project in the Fedora community, > maturing it in RHEL, learning deeply how RHEL works and shaping it, and now > back in a community space, I believe I have one valuable thing to offer: > insider perspective. In the coming weeks I will be sharing insights and > ideas. I’m not sure where it will lead, but that’s part of the fun of > sharing with others, the feedback alters the course. I'd love to hear from > you. /me waves This sounds intriguing and cool. I am looking forward to hearing those ideas. 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
[Fedocal] Reminder meeting : ELN SIG
Dear all, You are kindly invited to the meeting: ELN SIG on 2025-01-10 from 12:00:00 to 13:00:00 US/Eastern At fedora-meet...@irc.libera.chat The meeting will be about: Source: https://calendar.fedoraproject.org//meeting/10938/ -- ___ 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: Retiring GlusterFS in Fedora 42. First Notice
On Sun, Jan 05, 2025 at 02:07:11PM +0300, Benson Muite wrote: > > > On Sat, Jan 4, 2025, at 9:28 PM, Kaleb Keithley wrote: > > Are you a packager? > > Yes > > What's your FAS ID? > > Fed500 Note that the entire virt stack (just about) depends on gluster, so please coordinate with us if you push any breaking change. We may need to rebuild quite a few dependent packages. Easiest way is to email 'qemu-maintain...@fedoraproject.org'. Although I suppose since upstream development is dead, maybe that won't be very likely ... Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -- ___ 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: Retiring GlusterFS in Fedora 42. First Notice
Just to be clear, Benson Muite has agreed to take over as admin/maintainer of glusterfs and it's not going to be retired now. Somewhat orthogonal to that, upstream development has slowed to a crawl and there hasn't been a release in over a year; the outlook is pretty grim in my opinion. Take that for what it's worth. On Thu, Jan 9, 2025 at 9:01 AM Peter Robinson wrote: > > > On Thu, 9 Jan 2025 at 12:07, Richard W.M. Jones wrote: > >> On Sun, Jan 05, 2025 at 02:07:11PM +0300, Benson Muite wrote: >> > >> > >> > On Sat, Jan 4, 2025, at 9:28 PM, Kaleb Keithley wrote: >> > > Are you a packager? >> > >> > Yes >> > >> > What's your FAS ID? >> > >> > Fed500 >> >> Note that the entire virt stack (just about) depends on gluster, so >> please coordinate with us if you push any breaking change. We may >> need to rebuild quite a few dependent packages. Easiest way is to >> email 'qemu-maintain...@fedoraproject.org'. >> >> Although I suppose since upstream development is dead, maybe that >> won't be very likely ... >> > > While it doesn't affect things from a build perspective, but could gluster > be possibly be made recommended instead of required at the > libvirt-daemon-driver-storage level? > -- > ___ > 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 > -- Kaleb -- ___ 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: 20250109.n.1 changes
OLD: Fedora-eln-20250108.n.0 NEW: Fedora-eln-20250109.n.1 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:18 Upgraded packages: 270 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:30.50 MiB Size of upgraded packages: 5.37 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -9.44 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = Package: bodhi-client-8.3.0-1.eln144 Summary: Bodhi client RPMs:bodhi-client Size:91.77 KiB Package: fedora-easy-karma-0.54-1.eln144 Summary: Fedora update feedback made easy RPMs:fedora-easy-karma Size:30.80 KiB Package: fedora-packager-1.0-4.eln144 Summary: Tools for setting up a Fedora maintainer environment RPMs:fedora-packager fedora-packager-kerberos Size:34.38 KiB Package: fedora-repoquery-0.7.1-1.eln144 Summary: Fedora release repos package query tool RPMs:fedora-repoquery Size:25.25 MiB Package: fedpkg-1.45-3.eln142 Summary: Fedora utility for working with dist-git RPMs:fedpkg Size:118.63 KiB Package: python-authlib-1.4.0-1.eln144 Summary: Build OAuth and OpenID Connect servers in Python RPMs:python3-authlib Size:489.94 KiB Package: python-bugzilla-3.3.0-1.eln144 Summary: Python library for interacting with Bugzilla RPMs:python3-bugzilla Size:138.01 KiB Package: python-click-plugins-1.1.1-22.eln144 Summary: Click extension to register CLI commands via setuptools RPMs:python3-click-plugins Size:17.18 KiB Package: python-kitchen-1.2.6-21.eln144 Summary: Small, useful pieces of code to make python coding easier RPMs:python3-kitchen Size:111.58 KiB Package: python-krb5-0.7.0-1.eln144 Summary: Kerberos API bindings for Python RPMs:python3-krb5 Size:2.59 MiB Package: python-lockfile-1:0.12.2-15.eln144 Summary: Platform-independent file locking module RPMs:python3-lockfile Size:39.14 KiB Package: python-munch-4.0.0-1.eln144 Summary: A dot-accessible dictionary (a la JavaScript objects) RPMs:python3-munch Size:26.03 KiB Package: python-openidc-client-0.6.0^1.0e2ed81-2.eln144 Summary: Python OpenID Connect client with token caching and management RPMs:python3-openidc-client Size:27.26 KiB Package: python-pygit2-1.16.0-1.eln144 Summary: Python bindings for libgit2 RPMs:python3-pygit2 Size:1.15 MiB Package: python-requests-kerberos-0.15.0-1.eln144 Summary: A Kerberos authentication handler for python-requests RPMs:python3-requests-kerberos Size:28.29 KiB Package: python-rpmautospec-0.7.3-1.eln144 Summary: Package and CLI tool to generate release fields and changelogs RPMs:python3-rpmautospec rpmautospec Size:89.64 KiB Package: python-rpmautospec-core-0.1.5-2.eln144 Summary: Minimum functionality for rpmautospec RPMs:python3-rpmautospec-core Size:15.26 KiB Package: python-spnego-0.11.1-1.eln144 Summary: Windows Negotiate Authentication Client and Server RPMs:python3-spnego python3-spnego+kerberos Size:292.41 KiB = UPGRADED PACKAGES = Package: abseil-cpp-20240722.0-2.eln144 Old package: abseil-cpp-20240722.0-1.eln144 Summary: C++ Common Libraries RPMs: abseil-cpp abseil-cpp-devel abseil-cpp-testing Size: 6.31 MiB Size change: -487.87 KiB Changelog: * Wed Jan 08 2025 Benjamin A. Beasley - 20240722.0-2 - Report and skip a test regression on ppc64le Package: accel-config-4.1.8-9.eln144 Old package: accel-config-4.1.7-8.eln144 Summary: Configure accelerator subsystem devices RPMs: accel-config accel-config-devel accel-config-libs Size: 142.87 KiB Size change: -5.27 KiB Changelog: * Thu Jan 09 2025 Jun Miao - 4.1.8-9 - Update to v4.1.8 release Package: akonadi-calendar-24.12.1-1.eln144 Old package: akonadi-calendar-24.12.0-1.eln144 Summary: The Akonadi Calendar Library RPMs: akonadi-calendar Size: 1.57 MiB Size change: 860 B Changelog: * Tue Jan 07 2025 Steve Cossette - 24.12.1-1 - 24.12.1 Package: akonadi-calendar-tools-24.12.1-1.eln144 Old package: akonadi-calendar-tools-24.12.0-1.eln144 Summary: Akonadi Calendar Tools RPMs: akonadi-calendar-tools Size: 988.55 KiB Size change: -187 B Changelog: * Tue Jan 07 2025 Steve Cossette - 24.12.1-1 - 24.12.1 Package: akonadi-contacts-24.12.1-1.eln144 Old package: akonadi-contacts-24.12.0-1.eln144 Summary: The Akonadi Contacts Library RPMs: akonadi-contacts Size: 1.16 MiB Size change: 313 B Changelog: * Tue Jan 07 2025 Steve Cossette - 24.12.1-1 - 24.12.1 Package: akonadi-import-wizard-24.12.1-1.eln144 Old package: akonadi-import-wizard-24.12.0-1.eln144 Summary: Akonadi Import Wizard RPMs: akonadi-import-wizard Size: 1.49 MiB Size change: -356 B
Re: Self-reintroduction, reflections, and so forth
On Wed, Jan 8, 2025 at 11:45 PM Brendan Conoboy wrote: > Over the last few months on chat.fp.o and at conferences I have started > joining into conversations- listening, asking questions, making assertions, > telling bad jokes. All this activity has led to a recurring question by > many people in the community, “uhh, who are you?” > > It's great to see you around, Brendan. I too look forward to your thoughts over the coming weeks. -Jared -- ___ 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
Unannounced soname bump: libcamera
libcamera-0.4.0-1.fc42 - https://bodhi.fedoraproject.org/updates/FEDORA-2025-8e97fedfb9 - bumped the soname of the libraries from libcamera(*).so.0.3 to libcamera(*).so.0.4. soname bumps are supposed to be announced on devel@ and to maintainers of dependent packages - https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/#_notify_others_of_changes_that_may_affect_their_packages (that could use a glow-up, but it's basically right). In this case, pipewire-plugin-libcamera requires libcamera, and that package is part of default KDE and GNOME installs, so this update is broken on both KDE and GNOME at least. We need an update that contains the libcamera soname bump and a rebuild of pipewire against it. To do this, you should use a side tag, per https://docs.fedoraproject.org/en-US/package-maintainers/Package_Update_Guide/#multiple_packages . In future please remember to announce bumps to the soname, and co- ordinate rebuilds and a sidetag update with the pipewire maintainer (and the maintainers of any more packages that grow libcamera deps in future). 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