Notification: Closure of Failed Compose Issues from Last Release Cycle - Fedora 41
Hello, folks! \0/ We will close all failed compose issues that occurred over the last release cycle in the Pagure Failed Composes Repository[1]. This action will result in email notifications for each issue. Currently, there are issues, meaning email notifications will be triggered. To avoid inconvenience, we kindly suggest the following: - Set up a filter in your email client to automatically sort/clean or archive these notifications. - Temporarily mute notifications for this repository, if preferred. We sincerely apologize for the volume of notifications this action may generate and appreciate your understanding as we maintain a clean and efficient repository. Thank you for your cooperation. Best regards, Samyak Jain Fedora Release Engineering Team [1] https://pagure.io/releng/failed-composes/issues -- ___ 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: Non-responsive maintainer check for lbazan (Luis Enrique Bazan De Leon)
Can you poke him again please? I see no reaction on bugreport https://bugzilla.redhat.com/show_bug.cgi?id=2184181 -- ___ 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
Take ownership of golang-github-petermattis-goid
Hello, I want to take ownership of /golang-github-petermattis-goid/. It got retied, because it was orphaned for 6+ weeks. The re-review bug is https://bugzilla.redhat.com/show_bug.cgi?id=2326926 Best wishes Kai -- ___ 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: Non-responsive maintainer check for lbazan (Luis Enrique Bazan De Leon)
Can you poke him again please. I see no reaction from him. -- ___ 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
find-debuginfo failing with objcopy Permission denied error
This is a weird one: https://koji.fedoraproject.org/koji/taskinfo?taskID=125988419 + /usr/bin/find-debuginfo -j48 --strict-build-id -m -i --build-id-seed 1.55.2-1.fc42 --unique-debug-suffix -1.55.2-1.fc42.x86_64 --unique-debug-src-base libguestfs-1.55.2-1.fc42.x86_64 --run-dwz --dwz-low-mem-die-limit 1000 --dwz-max-die-limit 11000 -S debugsourcefiles.list /builddir/build/BUILD/libguestfs-1.55.2-build/libguestfs-1.55.2 find-debuginfo: starting Extracting debug info from 13 files objcopy: unable to copy file '/builddir/build/BUILD/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so'; reason: Permission denied *** ERROR:: GDB exited with exit status 1 during index generation The same thing happens on each architecture, for the same file. 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: find-debuginfo failing with objcopy Permission denied error
On Mon, Nov 18, 2024 at 03:35:38PM +, Richard W.M. Jones wrote: > On Mon, Nov 18, 2024 at 03:16:13PM +, Richard W.M. Jones wrote: > > This is a weird one: > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=125988419 > > > > + /usr/bin/find-debuginfo -j48 --strict-build-id -m -i --build-id-seed > > 1.55.2-1.fc42 --unique-debug-suffix -1.55.2-1.fc42.x86_64 > > --unique-debug-src-base libguestfs-1.55.2-1.fc42.x86_64 --run-dwz > > --dwz-low-mem-die-limit 1000 --dwz-max-die-limit 11000 -S > > debugsourcefiles.list > > /builddir/build/BUILD/libguestfs-1.55.2-build/libguestfs-1.55.2 > > find-debuginfo: starting > > Extracting debug info from 13 files > > objcopy: unable to copy file > > '/builddir/build/BUILD/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so'; > > reason: Permission denied > > *** ERROR:: GDB exited with exit status 1 during index generation > > I managed to reproduce this locally. The file permissions look > normal, albeit the file is write-protected: > > -r-xr-xr-x. 1 rjones rjones 2885944 Nov 18 15:22 > /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so > > I patched gdb-add-index to print the exact command which fails, and > that is: > > + objcopy --add-section > .gdb_index=/home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so.gdb-index > --set-section-flags .gdb_index=readonly > /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so > > /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so > objcopy: unable to copy file > '/home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so'; > reason: Permission denied > > It seems like it is trying to update the file in place, which is > interesting. Is that allowed? Anyway as the permissions of the file > are 0555 it won't be able to do that. Is this a recent change in > behaviour? Perhaps the same thing as this thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GG4LQYBEKGWAGFSJ5PKTKJAOHLAB3A27/#QYIK5E642MDB4NGBXLRLLTMU7HAJOVV5 ie, debugedit 5.1? kevin 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: Bodhi 8.2 in production: changes to karma requirements
On Mon, 2024-11-18 at 11:49 +, Zbigniew Jędrzejewski-Szmek wrote: > > If there is something that the policy text says that is stronger than > what Bodhi requires, then we should update the policy text immediately. As of now there is not, because in 8.2 I made the tool to implement what the policy says, which is the way around things ought to be. :D Before 8.2, this was the case, yes. -- 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: find-debuginfo failing with objcopy Permission denied error
On Mon, Nov 18, 2024 at 03:16:13PM +, Richard W.M. Jones wrote: > This is a weird one: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=125988419 > > + /usr/bin/find-debuginfo -j48 --strict-build-id -m -i --build-id-seed > 1.55.2-1.fc42 --unique-debug-suffix -1.55.2-1.fc42.x86_64 > --unique-debug-src-base libguestfs-1.55.2-1.fc42.x86_64 --run-dwz > --dwz-low-mem-die-limit 1000 --dwz-max-die-limit 11000 -S > debugsourcefiles.list > /builddir/build/BUILD/libguestfs-1.55.2-build/libguestfs-1.55.2 > find-debuginfo: starting > Extracting debug info from 13 files > objcopy: unable to copy file > '/builddir/build/BUILD/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so'; > reason: Permission denied > *** ERROR:: GDB exited with exit status 1 during index generation I managed to reproduce this locally. The file permissions look normal, albeit the file is write-protected: -r-xr-xr-x. 1 rjones rjones 2885944 Nov 18 15:22 /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so I patched gdb-add-index to print the exact command which fails, and that is: + objcopy --add-section .gdb_index=/home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so.gdb-index --set-section-flags .gdb_index=readonly /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so objcopy: unable to copy file '/home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so'; reason: Permission denied It seems like it is trying to update the file in place, which is interesting. Is that allowed? Anyway as the permissions of the file are 0555 it won't be able to do that. Is this a recent change in behaviour? 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
RamaLama is now packaged up for Fedora.
RamaLama is now available as a package for Fedora 40,41 and Rawhide. python-ramalama. dnf install ramalama You can also install it via pip/pipx from PyPi. Try it out for your AI Inferencing needs. github.com/containers/ramalama -- ___ 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: Findings by static analyzers in Fedora 42 Critical Path Packages
Right after I sent this I got a response [0] to the gcc bug and turns out that the culprit is disabled LTO. And indeed, if I build systemd with `-fanalyzer -flto=auto`, (almost) all reports disappear: With just -fanalyzer (meson setup build -Dc_args="-fanalyzer"): $ grep warning: log-fanalyzer.txt | wc -l 1519 With -fanalyzer -lto=auto (meson setup build -Dc_args="-fanalyzer -lto=auto"): $ grep warning: log-fanalyzer-lto.txt | wc -l 1 The LTO is being disabled in the csgcca wrapper since [1] because of some issues between -fanalyzer and LTO, but looks like disabling it has some disadvantages as well (not sure if they outweigh the advantages, I tested this only on systemd so far). [0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117662#c2 [1] https://github.com/csutils/cscppc/commit/d8d49b4cc92e0109b2654e9034c85e169bdc0566 On 11/18/24 18:25, František Šumšal wrote: Hey, Thank you for doing this! I started taking apart systemd findings and reported a first issue against gcc [0], so we can hopefully squash the false positives from the results (at least the ones repored by gcc's -fanalyzer) and make them more useful. One thing that comes to mind (especially after the battle in [1]): how does the gcc's -fanalyzer handle optimized builds? In Fedora we currently (IIRC) build with -O2, and if I do a systemd build locally with both -O0 and -O2, the latter one generates more warnings. There's also several notes in the official documentation [2] that some of the checks might not work when optimizations are enabled, since the analyzer runs quite late in the compilation process. Which also raises question - does optimization make -fanalyzer more prone to false positives? And does it make the findings less accurate? Cheers, Frantisek [0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117662 [1] https://github.com/csutils/cscppc/issues/46 [2] https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html On 11/14/24 08:47, Siteshwar Vashisht wrote: Hello, I am writing this message to get feedback from the community on new findings by static analyzers in Critical Path Packages that have changed in Fedora 42. TLDR: This report[1] contains 37330 findings. Please review the report and provide feedback. A mass scan was performed this week on the packages that have changed in Fedora 42. This report[1] contains all the new findings that have been identified in the packages listed in Critical Path Packages. Newly added findings since Fedora 41 are listed under ‘+’ column. Please review the report and fix or report any findings upstream that may be real bugs. Not all findings reported by OpenScanHub may be actual bugs, so please verify reported findings before investing time into fixing or reporting them. We hope this is helpful for the packages you maintain and for the upstream projects. Questions can be asked on the OpenScanHub mailing list[2]. If you want to see the full logs of the scans, they are available on the tasks[3] page. User documentation for performing a scan is available on the Fedora wiki[4]. Constructive feedback is appreciated. Thank you! [1] https://svashisht.fedorapeople.org/openscanhub/mass-scans/f42-13-Nov-2024/ [2] https://lists.fedoraproject.org/archives/list/openscan...@lists.fedoraproject.org/ [3] https://openscanhub.fedoraproject.org/task/ [4] https://fedoraproject.org/wiki/OpenScanHub -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B -- ___ 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: ABI change in ImageMagick
On Mon, Nov 18, 2024 at 09:17:48AM +0100, Remi Collet wrote:
> Le 16/11/2024 à 22:46, Peter Pentchev a écrit :
>
> > Hm, ICBW, but, at least to me, this enum change looks like an actual
> > breaking ABI (not API) change. If a program was compiled to call that
> > function with the SentinelFilter value, the program code would pass
> > 32 as a parameter and invoke the function. If loaded with the new
> > version of the library, this would cause the function to assume that
> > the caller wanted to pass MagicKernelSharp2013Filter and... do something
> > unexpected.
>
> No, SentinelFilter is a special value keeping track of first free value
> A program will never use this in an arg call (OK name is confusing)
>
> Typical usage
>
> if (filter < SentinelFilter) {
> SetResampleFilter(RF, filter);
> } else {
> printf("Bad filter value\n");
> exit(1);
> }
Ahh, okay. Thanks a lot for the explanation!
This only leaves one possible case for confusion: a user of the library
that somehow sees a now-valid value and compares it against their
"remembered" value for SentinelFilter, e.g. a callback or something.
But this seems to be a bit of a reach, so yeah, thanks again for
clearing this up, and sorry for stepping in uninformed :)
> Notice: the bad map change have been reverted,
> so 7.1.1-41 is OK with same ABI than 7.1.1-39
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@debian.org pe...@morpheusly.com
PGP key:https://www.ringlet.net/roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
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: Obtaining the RPM_ARCH etc. environment variables
On Mon, 2024-11-18 at 09:19 +0100, Florian Weimer wrote: > Is > > eval `rpm --eval %___build_pre_env` > > the canonical way to obtain definitions of these environment > variables, > or is there a better alternative? > from https://bugzilla.redhat.com/show_bug.cgi?id=2043092#c80 to the "official" documentation, is in /usr/lib/rpm/macros.d/macros.package-notes-srpm or at https://src.fedoraproject.org/rpms/package-notes/raw/rawhide/f/macros.package-notes-srpm > Thanks, > Florian > -- 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 rawhide compose report: 20241118.n.0 changes
OLD: Fedora-Rawhide-20241117.n.0 NEW: Fedora-Rawhide-20241118.n.0 = SUMMARY = Added images:0 Dropped images: 3 Added packages: 3 Dropped packages:0 Upgraded packages: 67 Downgraded packages: 0 Size of added packages: 2.65 MiB Size of dropped packages:0 B Size of upgraded packages: 209.27 MiB Size of downgraded packages: 0 B Size change of upgraded packages: -245.53 KiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20241117.n.0.iso Image: Kinoite dvd-ostree aarch64 Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20241117.n.0.iso Image: Onyx dvd-ostree x86_64 Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20241117.n.0.iso = ADDED PACKAGES = Package: python-eth-rlp-2.1.0-1.fc42 Summary: RLP definitions for common Ethereum objects in Python RPMs:python3-eth-rlp Size:15.13 KiB Package: python-flask-sqlalchemy-lite-0.1.0-2 Summary: Adds SQLAlchemy support to Flask application RPMs:python3-flask-sqlalchemy-lite Size:23.31 KiB Package: python-pyogrio-0.10.0-2.fc42 Summary: Vectorized spatial vector file format I/O using GDAL/OGR RPMs:python3-pyogrio Size:2.61 MiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: antimicrox-3.5.0-1.fc42 Old package: antimicrox-3.4.1-2.fc42 Summary: Graphical program used to map keyboard buttons and mouse controls to a gamepad RPMs: antimicrox Size: 4.08 MiB Size change: 1.03 KiB Changelog: * Sun Nov 17 2024 Gergely Gombos - 3.5.0-1 - 3.5.0 Package: cctz-2.4-1.fc42 Old package: cctz-2.3-15.fc41 Summary: Translating between absolute and civil times using time zone rules RPMs: cctz cctz-devel Size: 563.43 KiB Size change: 36.29 KiB Changelog: * Mon Nov 18 2024 Elliott Sales de Andrade - 2.4-1 - Update to latest version (#2264604) Package: cobbler-3.3.7-1.fc42 Old package: cobbler-3.3.6-2.fc42 Summary: Boot server configurator RPMs: cobbler cobbler-selinux cobbler-tests cobbler-tests-containers Size: 1.03 MiB Size change: 3.61 KiB Changelog: * Sun Nov 17 2024 Orion Poplawski - 3.3.7-1 - Update to 3.3.7 (CVE-2024-47533) Package: golang-github-aws-smithy-1.22.1-1.fc42 Old package: golang-github-aws-smithy-1.22.0-1.fc42 Summary: Smithy code generators for Go (in development) RPMs: golang-github-aws-smithy-devel Size: 237.38 KiB Size change: 83 B Changelog: * Fri Nov 15 2024 Packit - 1.22.1-1 - Update to 1.22.1 upstream release - Resolves: rhbz#2326619 Package: golang-github-projectdiscovery-ratelimit-0.0.62-1.fc42 Old package: golang-github-projectdiscovery-ratelimit-0.0.61-1.fc42 Summary: A Golang blocking rate limit implementation RPMs: golang-github-projectdiscovery-ratelimit-devel Size: 17.46 KiB Size change: 110 B Changelog: * Sun Nov 17 2024 Packit - 0.0.62-1 - Update to 0.0.62 upstream release - Resolves: rhbz#2326720 Package: jrnl-4.2-2.fc42 Old package: jrnl-4.1-12.fc42 Summary: Collect your thoughts and notes without leaving the command line RPMs: jrnl Size: 228.78 KiB Size change: 5.13 KiB Changelog: * Mon Nov 18 2024 Benjamin A. Beasley - 4.2-1 - Update to 4.2 (close RHBZ#2326878) * Mon Nov 18 2024 Benjamin A. Beasley - 4.2-2 - F41+: No longer need Obsoletes for the -doc package Package: kwin-6.2.3-2.fc42 Old package: kwin-6.2.3-1.fc42 Summary: KDE Window manager RPMs: kwin kwin-common kwin-devel kwin-doc kwin-libs kwin-wayland Size: 38.77 MiB Size change: -37.69 KiB Changelog: * Sun Nov 17 2024 Alessandro Astone - 6.2.3-2 - Backport fix for keyboard focus after using the task switcher https://bugs.kde.org/show_bug.cgi?id=495844 https://bugs.kde.org/show_bug.cgi?id=491398 Package: libheif-1.19.3-3.fc42 Old package: libheif-1.17.6-2.fc41 Summary: HEIF and AVIF file format decoder and encoder RPMs: heif-pixbuf-loader libheif libheif-devel libheif-tools Size: 3.18 MiB Size change: 850.02 KiB Changelog: * Tue Nov 12 2024 Dominik Mierzejewski - 1.19.3-1 - update to 1.19.3 (resolves rhbz#2295525) - drop obsolete patches - enable OpenH264, OpenJPH (64-bit only) and Brotli decoders - run tests unconditionally, they no longer require special build options - drop conditional hevc subpackage - use fewer wildcards in the file lists - stop building rav1e and svt AV1 encoders as plugins * Sat Nov 16 2024 S??rgio Basto - 1.19.3-2 - Add support to multilib in devel sub-package - Resolves: rhbz#2279891 * Sun Nov 17 2024 Dominik Mierzejewski - 1.19.3-3 - disable OpenJPH encoder support to work-around crashes Package: mingw-directxmath-3.20-1.fc42 Old package: mingw-directxmath-3.19-2.fc41
Fedora eln compose report: 20241119.n.0 changes
OLD: Fedora-eln-20241118.n.0 NEW: Fedora-eln-20241119.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:1 Upgraded packages: 29 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:484.52 KiB Size of upgraded packages: 1.83 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -3.37 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = = ADDED PACKAGES = = DROPPED PACKAGES = Package: openjph-0.18.0-1.eln143 Summary: Open-source implementation of JPEG2000 Part-15 (or JPH or HTJ2K) RPMs:libopenjph Size:484.52 KiB = UPGRADED PACKAGES = Package: annobin-12.77-1.eln143 Old package: annobin-12.75-1.eln143 Summary: Annotate and examine compiled binary files RPMs: annobin-annocheck annobin-docs annobin-libannocheck annobin-plugin-clang annobin-plugin-gcc annobin-plugin-llvm Size: 5.44 MiB Size change: 22.43 KiB Changelog: * Fri Nov 15 2024 Nick Clifton - 12.76-1 - Annocheck: Rename rwx-seg test to load-segments. Add more checks. Add check for gaps as a future fail. - Annocheck: Add --no-allow-excpetions to disable exceptions for known special binaries. - Annocheck: Add --enable-future to enable future fail components in normal tests. - Annocheck: Fix bug preventing the inclusion of the rpm name in reports. * Fri Nov 15 2024 Nick Clifton - 12.77-1 - Annocheck: Fix overly long debug messages. Package: bodhi-client-8.2.0-2.eln143 Old package: bodhi-client-8.2.0-1.eln143 Summary: Bodhi client RPMs: bodhi-client Size: 90.62 KiB Size change: 172 B Changelog: * Mon Nov 11 2024 Carl George - 8.2.0-2 - Correctly mark COPYING file as a license - Remove unnecessary pytest-cov build requirement Package: clevis-21-7.eln143 Old package: clevis-21-6.eln143 Summary: Automated decryption framework RPMs: clevis clevis-dracut clevis-luks clevis-pin-pkcs11 clevis-systemd clevis-udisks2 Size: 599.65 KiB Size change: 2.91 KiB Changelog: * Tue Nov 12 2024 Sergio Arroutbi - 21-7 - tpm2: use first PCR algorithm bank supported Package: egl-wayland-1.1.17^20241118giteeb29e1-5.eln143 Old package: egl-wayland-1.1.17^20241101git218f678-4.eln143 Summary: EGLStream-based Wayland external platform RPMs: egl-wayland egl-wayland-devel Size: 248.94 KiB Size change: 1.16 KiB Changelog: * Mon Nov 18 2024 Simone Caronni - 1.1.17^20241118giteeb29e1-5 - Update to latest snapshot. Package: evolution-data-server-3.54.1-2.eln143 Old package: evolution-data-server-3.54.1-1.eln143 Summary: Backend data server for Evolution RPMs: evolution-data-server evolution-data-server-devel evolution-data-server-doc evolution-data-server-langpacks evolution-data-server-perl evolution-data-server-tests Size: 18.04 MiB Size change: -99.41 KiB Changelog: * Mon Nov 18 2024 Adam Williamson - 3.54.1-2 - Backport MR #166 to fix build with GTK 4.17+ - Rebuild for libphonenumber 8.13.50 Package: guestfs-tools-1.53.5-1.eln143 Old package: guestfs-tools-1.53.4-1.eln143 Summary: Tools to access and modify virtual machine disk images RPMs: guestfs-tools virt-win-reg Size: 15.06 MiB Size change: 17.80 KiB Changelog: * Mon Nov 18 2024 Richard W.M. Jones - 1.53.5-1 - New upstream development version 1.53.5 Package: kernel-6.12.0-65.eln143 Old package: kernel-6.12.0-0.rc7.20241115gitcfaaa7d010d1.62.eln143 Summary: The Linux kernel RPMs: bpftool 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-zfcpdump kernel-zfcpdump-core kernel-zfcpdump-devel kernel-zfcpdump-devel-matched kernel-zfcpdump-modules kernel-zfcpdump-modules-core kernel-zfcpdump-modules-extra libperf
Re: find-debuginfo failing with objcopy Permission denied error
On Mon, Nov 18, 2024 at 07:50:38AM -0800, Kevin Fenzi wrote:
> On Mon, Nov 18, 2024 at 03:35:38PM +, Richard W.M. Jones wrote:
> > On Mon, Nov 18, 2024 at 03:16:13PM +, Richard W.M. Jones wrote:
> > > This is a weird one:
> > >
> > > https://koji.fedoraproject.org/koji/taskinfo?taskID=125988419
> > >
> > > + /usr/bin/find-debuginfo -j48 --strict-build-id -m -i --build-id-seed
> > > 1.55.2-1.fc42 --unique-debug-suffix -1.55.2-1.fc42.x86_64
> > > --unique-debug-src-base libguestfs-1.55.2-1.fc42.x86_64 --run-dwz
> > > --dwz-low-mem-die-limit 1000 --dwz-max-die-limit 11000 -S
> > > debugsourcefiles.list
> > > /builddir/build/BUILD/libguestfs-1.55.2-build/libguestfs-1.55.2
> > > find-debuginfo: starting
> > > Extracting debug info from 13 files
> > > objcopy: unable to copy file
> > > '/builddir/build/BUILD/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so';
> > > reason: Permission denied
> > > *** ERROR:: GDB exited with exit status 1 during index generation
> >
> > I managed to reproduce this locally. The file permissions look
> > normal, albeit the file is write-protected:
> >
> > -r-xr-xr-x. 1 rjones rjones 2885944 Nov 18 15:22
> > /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so
> >
> > I patched gdb-add-index to print the exact command which fails, and
> > that is:
> >
> > + objcopy --add-section
> > .gdb_index=/home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so.gdb-index
> > --set-section-flags .gdb_index=readonly
> > /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so
> >
> > /home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so
> > objcopy: unable to copy file
> > '/home/rjones/d/fedora/libguestfs/rawhide/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so';
> > reason: Permission denied
> >
> > It seems like it is trying to update the file in place, which is
> > interesting. Is that allowed? Anyway as the permissions of the file
> > are 0555 it won't be able to do that. Is this a recent change in
> > behaviour?
>
> Perhaps the same thing as this thread:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/GG4LQYBEKGWAGFSJ5PKTKJAOHLAB3A27/#QYIK5E642MDB4NGBXLRLLTMU7HAJOVV5
The symptoms look the same. This prompted me to go back to the last
successful libguestfs build to see if the same command failed but the
failure was ignored, and yes that's exactly what happened:
https://koji.fedoraproject.org/koji/buildinfo?buildID=2573135
https://kojipkgs.fedoraproject.org//packages/libguestfs/1.55.1/1.fc42/data/logs/x86_64/build.log
...
Extracting debug info from 13 files
objcopy: unable to copy file
'/builddir/build/BUILD/libguestfs-1.55.1-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so';
reason: Permission denied
objcopy: unable to copy file
'/builddir/build/BUILD/libguestfs-1.55.1-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so';
reason: Permission denied
DWARF-compressing 13 files
...
> ie, debugedit 5.1?
Yes it's this version.
I added this patch which fixed local builds, but it feels wrong somehow ...
diff --git a/libguestfs.spec b/libguestfs.spec
index 1ca2b3a..aa4d4f8 100644
--- a/libguestfs.spec
+++ b/libguestfs.spec
@@ -802,6 +802,10 @@ find $RPM_BUILD_ROOT -name .packlist -delete
find $RPM_BUILD_ROOT -name '*.bs' -delete
find $RPM_BUILD_ROOT -name 'bindtests.pl' -delete
+# debuginfo generation fails with debugedit >= 5.1 unless the files
+# are writable:
+find $RPM_BUILD_ROOT -name Guestfs.so -exec chmod u+w {} \;
+
# golang: Ignore what libguestfs upstream installs, and just copy the
# source files to %%{_datadir}/gocode/src.
%ifarch %{golang_arches}
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit
--
___
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: Findings by static analyzers in Fedora 42 Critical Path Packages
Hey, Thank you for doing this! I started taking apart systemd findings and reported a first issue against gcc [0], so we can hopefully squash the false positives from the results (at least the ones repored by gcc's -fanalyzer) and make them more useful. One thing that comes to mind (especially after the battle in [1]): how does the gcc's -fanalyzer handle optimized builds? In Fedora we currently (IIRC) build with -O2, and if I do a systemd build locally with both -O0 and -O2, the latter one generates more warnings. There's also several notes in the official documentation [2] that some of the checks might not work when optimizations are enabled, since the analyzer runs quite late in the compilation process. Which also raises question - does optimization make -fanalyzer more prone to false positives? And does it make the findings less accurate? Cheers, Frantisek [0] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117662 [1] https://github.com/csutils/cscppc/issues/46 [2] https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html On 11/14/24 08:47, Siteshwar Vashisht wrote: Hello, I am writing this message to get feedback from the community on new findings by static analyzers in Critical Path Packages that have changed in Fedora 42. TLDR: This report[1] contains 37330 findings. Please review the report and provide feedback. A mass scan was performed this week on the packages that have changed in Fedora 42. This report[1] contains all the new findings that have been identified in the packages listed in Critical Path Packages. Newly added findings since Fedora 41 are listed under ‘+’ column. Please review the report and fix or report any findings upstream that may be real bugs. Not all findings reported by OpenScanHub may be actual bugs, so please verify reported findings before investing time into fixing or reporting them. We hope this is helpful for the packages you maintain and for the upstream projects. Questions can be asked on the OpenScanHub mailing list[2]. If you want to see the full logs of the scans, they are available on the tasks[3] page. User documentation for performing a scan is available on the Fedora wiki[4]. Constructive feedback is appreciated. Thank you! [1] https://svashisht.fedorapeople.org/openscanhub/mass-scans/f42-13-Nov-2024/ [2] https://lists.fedoraproject.org/archives/list/openscan...@lists.fedoraproject.org/ [3] https://openscanhub.fedoraproject.org/task/ [4] https://fedoraproject.org/wiki/OpenScanHub -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B -- ___ 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: Bodhi 8.2 in production: changes to karma requirements
Il 18/11/24 16:34, Adam Williamson ha scritto: > On Mon, 2024-11-18 at 11:49 +, Zbigniew Jędrzejewski-Szmek wrote: >> If there is something that the policy text says that is stronger than >> what Bodhi requires, then we should update the policy text immediately. > As of now there is not, because in 8.2 I made the tool to implement > what the policy says, which is the way around things ought to be. :D > Before 8.2, this was the case, yes. > -- > Adam Williamson (he/him/his) > Fedora QA > Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org > https://www.happyassassin.net > I tried to summarize currently applied settings in a table: https://docs.google.com/spreadsheets/d/1pPdWOX7YKSu-6pF6-20V7nECRdrHyj6xr4YEV54f_qo/edit?usp=sharing Where settings are absent, defaults are used. The idea is: an update can be pushed to stable either manually or automatically only after , or before if it reaches . Autopush settings can be equal or greater. What is reported as "Stable by karma" in the Update page is just the autopush setting. Which can be confusing when the autopush is set to a higher value, so that we see, for example, "stable by karma = +5", but after +2 karma we get the "can be pushed to stable if maintainer wishes" message. Mattia -- ___ 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
Obtaining the RPM_ARCH etc. environment variables
Is eval `rpm --eval %___build_pre_env` the canonical way to obtain definitions of these environment variables, or is there a better alternative? 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: PSA: tuned breaks boot loader entries for systemd-boot
On Sun, Nov 17, 2024 at 05:45:12PM +0100, Kevin Kofler via devel wrote:
> Zbigniew Jędrzejewski-Szmek wrote:
> > Heh, that's a cool idea. But that's not how standards work.
> > You cannot just insert things at random points in low-level config
> > files or protols. How do you think this would work?
> > You insert "$tuned_params", I insert "{tuned_params}", and GNU people
> > insert "@TUNED_PARAMS@", all because the spec didn't say that's
> > forbidden?
>
> Unfortunately, that is exactly how standards work in the real world. Pretty
> much any standardized language has dialects with incompatible extensions.
> Sometimes even explicitly ignoring a rule in the standard that forbids an
> extension at this place (and if you are lucky, the implementation providing
> an off-by-default flag to actually enforce that rule, flag which may or may
> not work reliably). Expecting any particular implementation to actually
> strictly conform to a standard and to always flag all non-strictly-
> conforming input is not a realistic expectation.
Yes and no. I don't argue that extensions happen and that they even
are useful. The problem here is that the extension happened in a way
that was strictly incompatible with the existing implementations (and
to a large extent the very idea that lead to the creation of the format)
and was done on files in the location read by multiple implementations,
not some private directory.
So… taking your example, nowadays C is often used with GCC extensions.
systemd is a very heavy user of those, it won't even compile with a
compiler that doesn't have support. But the header files it installs
in /usr/include are standards-compliant. In fact we have a bunch of
tests, including compilation with '-ansi', to avoid introducing a
non-standard extension in a shared location. If we did that, we'd
effectively force anyone compiling against libsystemd to a higher
standard version. People would be understandably unhappy and it'd get
immediately reverted.
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: Bodhi 8.2 in production: changes to karma requirements
On Mon, 2024-11-18 at 17:32 +, Mattia Verga via devel wrote: > Il 18/11/24 16:34, Adam Williamson ha scritto: > > On Mon, 2024-11-18 at 11:49 +, Zbigniew Jędrzejewski-Szmek wrote: > > > If there is something that the policy text says that is stronger than > > > what Bodhi requires, then we should update the policy text immediately. > > As of now there is not, because in 8.2 I made the tool to implement > > what the policy says, which is the way around things ought to be. :D > > Before 8.2, this was the case, yes. > > -- > > Adam Williamson (he/him/his) > > Fedora QA > > Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org > > https://www.happyassassin.net > > > I tried to summarize currently applied settings in a table: > > https://docs.google.com/spreadsheets/d/1pPdWOX7YKSu-6pF6-20V7nECRdrHyj6xr4YEV54f_qo/edit?usp=sharing > > Where settings are absent, defaults are used. > The idea is: an update can be pushed to stable either manually or > automatically only after , or before if it > reaches . Autopush settings can be equal or greater. Yeah, that matches my understanding, and it matches the policy as currently written. > > What is reported as "Stable by karma" in the Update page is just the > autopush setting. Which can be confusing when the autopush is set to a > higher value, so that we see, for example, "stable by karma = +5", but > after +2 karma we get the "can be pushed to stable if maintainer wishes" > message. Yeah, I did want to make some changes in the UI to clarify things further, but I never got around to it and frontend stuff isn't natural for me so it takes a while :\ If anyone else wants to do it that'd be great. -- 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: RamaLama is now packaged up for Fedora.
On Mon, 18 Nov 2024 at 13:52, Daniel Walsh wrote: > RamaLama is now available as a package for Fedora 40,41 and Rawhide. > python-ramalama. > > dnf install ramalama > > You can also install it via pip/pipx from PyPi. > > Try it out for your AI Inferencing needs. > > github.com/containers/ramalama > > Slight correction. It will be available SOON in Fedora 40, 41 and is available in rawhide. It has been built for Fedora 40 and 41 and is in bodhi testing currently * Fedora 40 https://bodhi.fedoraproject.org/updates/FEDORA-2024-9012e88666 * Fedora 41 https://bodhi.fedoraproject.org/updates/FEDORA-2024-1752a399c4 Please test and let me know if there are problems. I will fix and update as needed. > -- > ___ > 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 > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren -- ___ 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: Fedora CI for large RPMs?
On Wed, Nov 13, 2024 at 12:38 PM František Lachman wrote: > Hi Nikita, > > I can't speak on behalf of Fedora CI or Zuul but I want to mention that in > the Packit team[0], we are trying to help in this situation of not having > much capacity to maintain existing CI solutions for dist-git. > > Since Packit already have a (quite advanced) integration for the Testing > Farm to be run on GitHub/GitLab pull requests, we decided to provide the > same for dist-git pull-requests as well so there is the same experience in > upstream and downstream. The code is mostly ready, but the hardest part is > to agree on how to enable/tweak workflow (or if we should make it the > default). And we are really happy to get feedback like this so we can learn > from it from the very start. > > The current plan is to provide a prototype people can play with by the end > of the year. > If you want to follow our work, we have an epic for this here: > https://github.com/packit/packit-service/issues/2453 > > A small note to avoid confusion: > This is independent of Packit's Fedora release automation. We can even > give this a different branding. > The thing that the Packit team will maintain the CI service and share a > significant part of the code with Packit might be read as a technical > detail. > And since we use Testing Farm to run actual tests, no change in test > definitions (thanks to tmt) should be needed. > Thanks, this sounds promising. We'd be happy to give this a try when it becomes available. I found this document with a bit more info than the issue: https://github.com/packit/research/blob/main/research/integrations/fedora-ci/index.md I'm not really familiar with packit's existing CI integrations -- do they abort pending builds on new pushes, or do they continue running like in Fedora CI / Zuul? And just a few notes on the Koji Scratch build overload: > * We are coordinating this effort with the Testing Farm team (that > currently manages Zuul and is trying to deprecate[1] Fedora-CI). If/when > Packit provides this functionality, the other two might be disabled (either > in general or per-package). > Yeah, we wouldn't really be able to use the packit-based CI (at least longer term) if we can't disable the old Fedora CI somehow, otherwise people will yell at us again :) > * Packit could use Copr instead to provide RPMs but this change of build > system between CI and reality is probably not wanted. > Yes, I agree that it's important to use the same build infrastructure as the "real" builds. For LLVM, we hit a different set of issues for each of copr, fedora koji, centos stream koji and rhel brew. The hardware pool is different each time and that can make a big difference for things like openmp tests. Regards, Nikita -- ___ 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: Bodhi 8.2 in production: changes to karma requirements
On Sun, Nov 17, 2024 at 10:12:58AM -0800, Adam Williamson wrote: > On Sun, 2024-11-17 at 18:35 +0100, Kevin Kofler via devel wrote: > > Kevin Kofler via devel wrote: > > > PS: I suspect the documentation was actually just an attempt to document > > > the previous broken Bodhi policy implementation. (See > > > https://github.com/fedora-infra/bodhi/issues/772 and > > > https://github.com/fedora-infra/bodhi/issues/1033 – both got closed, but > > > the issue was never properly fixed.) > > > > PPS: Sorry, one more thing, I have to correct myself: > > > > Actually, the issue was eventually fixed in that Bodhi has at some point > > started allowing to set the stable threshold even when unchecking the > > autopush checkbox, so it was possible before 8.2 to manually push updates > > to > > stable at +1. > > > Though I still do not understand how a threshold makes any sense at all for > > manual pushes. Manual pushes should just always require only the minimum > > required by policy, as the person setting the threshold (to any allowed > > value) is the same as the one doing the push. > > > > Settable thresholds have only ever made sense for automatic pushes. (So the > > bug was not that the threshold was not settable for manual pushes, but that > > the non-settable threshold was fixed to the wrong value, the default for > > automatic pushes (+3) instead of the minimum allowed (+1). Which is why I > > still do not consider this properly fixed.) > > Yes, to be clear, in rewriting this code, I had the same opinion as > you. The configurable thresholds only make sense as applying to > autopush. There is no reason I can see to consider them as applying to > manual push. Agreed. > That is in fact an interesting question, now I dig into it. Zbigniew > seems to have done substantial rewrites on the karma requirements in > 2021. These were: > > https://pagure.io/fesco/fesco-docs/c/e57f002ee55810d1636e4460fe0d2c3515897c0b?branch=main > https://pagure.io/fesco/fesco-docs/c/19bf26cef5d5e2a8d744ea28d8d54ec5374112e9?branch=main > https://pagure.io/fesco/fesco-docs/c/33c510e462f0b4118a716a89315f6afef6f5354c?branch=main [snip] > So on the whole, I think you have a good point here, thanks for raising > it. I will file a FESCo ticket and ask for them to consider the history > here and decide if they want to make any changes based on this > evaluation. > > I think the current policy is written in a much more sensible and > clearer form than the old one was, but the actual changes to the > requirements that happened along the way may have been unintentional. Yeah, the semantic changes to the policy text were either unintended or were introduced to match what Bodhi actually implemented. If there is something that the policy text says that is stronger than what Bodhi requires, then we should update the policy text immediately. For cases where the policy text and Bodhi agree, but are unnecessarilly strict, let's change both at the same time. The old state where the docs and code disagree was the least desirable. 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: ABI change in ImageMagick
Le 16/11/2024 à 22:46, Peter Pentchev a écrit :
Hm, ICBW, but, at least to me, this enum change looks like an actual
breaking ABI (not API) change. If a program was compiled to call that
function with the SentinelFilter value, the program code would pass
32 as a parameter and invoke the function. If loaded with the new
version of the library, this would cause the function to assume that
the caller wanted to pass MagicKernelSharp2013Filter and... do something
unexpected.
No, SentinelFilter is a special value keeping track of first free value
A program will never use this in an arg call (OK name is confusing)
Typical usage
if (filter < SentinelFilter) {
SetResampleFilter(RF, filter);
} else {
printf("Bad filter value\n");
exit(1);
}
Notice: the bad map change have been reverted,
so 7.1.1-41 is OK with same ABI than 7.1.1-39
Remi
--
___
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
Next Open NeuroFedora Meeting: Monday, 18 November 2024 (today) at 13:00 UTC
Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday, 18 November at 13:00 UTC. The meeting is a public meeting, and open for everyone to attend. You can join us over on Matrix in the Fedora Meeting channel: https://matrix.to/#/#meeting:fedoraproject.org You can use this link to see the local time for the meeting: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Open+NeuroFedora+Meeting&iso=20241118T13&p1=1440&ah=1 or you can use this command in a terminal: $ date -d 'Monday, November 18, 2024 13:00 UTC' The meeting will be chaired by @ankursinha. The agenda for the meeting is: - New introductions and roll call. - Tasks from last meeting: https://meetbot.fedoraproject.org/latest/neurofedora - Open Pagure tickets: https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+meeting - Package health check: https://packager-dashboard.fedoraproject.org/dashboard?groups=neuro-sig - Open package reviews check: https://bugzilla.redhat.com/show_bug.cgi?id=fedora-neuro - CompNeuro lab compose status check: https://koji.fedoraproject.org/koji/packageinfo?packageID=30691 - Neuroscience query of the week - Next meeting day, and chair. - Open floor. We hope to see you there! The meeting announcement is also posted on the NeuroFedora blog here: https://neuroblog.fedoraproject.org/2024/11/18/next-open-neurofedora-meeting-18-november-1300-utc.html You can learn more about NeuroFedora here: https://neuro.fedoraproject.org -- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London 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: HEADS UP: OpenImageIO 3.x SONAME bump
Sorry for the delay... $LIFE and $DAYJOB got in the way. Will be picking this back up soon. 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
