devel July 2025

devel@lists.fedoraproject.org

142 participants
219 discussions

Please don't commit significant changes and leave them to be built by the mass rebuild
by Adam Williamson 05 Aug '25

05 Aug '25

Hey folks! I figured a wider heads-up about this might be useful. The owner of the "Dropping of cert.pem file" Change[0] committed the change to dist-git but did not build it, instead leaving it to be built as part of the mass rebuild[1]. This, unfortunately, was a really bad idea. Mass rebuild changes bypass automated testing and gating, and land all at once in a huge lump. This has several consequences if a mass rebuild build breaks things: 1) The change is not gated as it might be if it went through gating, but immediately goes out and breaks real-world cases 2) Unrelated subsequent updates may get gated because tests on them fail due to the change 3) Investigating the breakage is difficult and time-consuming because the 'suspect pool' of packages is *every single package in the mass rebuild* Please, *always*, only land significant changes when you are ready to build and submit them as regular updates. In general, the delta between what is currently in Rawhide and what the mass rebuild will build should be *as small as possible*. Any unbuilt/blocked change sitting in dist-git prior to the mass rebuild is essentially a time bomb. [0] https://fedoraproject.org/wiki/Changes/dropingOfCertPemFile [1] https://bugzilla.redhat.com/show_bug.cgi?id=2360110#c2 -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

11 25

Retiring nodejs18
by Jan Stanek 05 Aug '25

05 Aug '25

Hello! The recent mass rebuild brought to my attention [1] that we have not yet retired the nodejs18 package. NodeJS 18 is considered EOL upstream [2], and will not receive any further updates (not even security ones). Thus, I intend to retire the package by the start of next week. Let me know if you have any objections or opinions. [1]: https://bugzilla.redhat.com/show_bug.cgi?id=2385215 [2]: https://nodejs.org/en/about/previous-releases#release-schedule Best regards! -- Jan Stanek Software Engineer Red Hat IM: @jstanek

1 1

Proposal: Drop Intel-based Macbook dual boot release criterion
by Kamil Paral 05 Aug '25

05 Aug '25

Hi folks, we have published a release criteria change proposal at Fedora Discussion: https://discussion.fedoraproject.org/t/proposal-drop-intel-based-macbook-du… This is a notification to make sure everybody can see it and post feedback, even when not watching Fedora Discussion regularly. When replying, **please**, reply to the Discussion topic. Logging in through FAS is trivial. We want a unified discussion in one place, instead of having it split between multiple places. Thank you. Kamil Paral Fedora Quality

1 1

openapv SONAME bump in Rawhide
by Dominik 'Rathann' Mierzejewski 04 Aug '25

04 Aug '25

Hi, I'm updating openapv to 0.2.0.0 release in Rawhide only (at this time). There don't seem to be any consumers, so no packages need a rebuild. This release brings in only new APIs, so if anyone is using it outside Fedora, a simple rebuild should suffice. Upstream release notes: https://github.com/AcademySoftwareFoundation/openapv/releases/tag/v0.2.0.0 Regards, Dominik -- Fedora https://fedoraproject.org Deep in the human unconscious is a pervasive need for a logical universe that makes sense. But the real universe is always one step beyond logic. -- from "The Sayings of Muad'Dib" by the Princess Irulan

1 2

F43 Change Proposal: Hare Programming Language (self-contained)
by Aoife Moloney via devel-announce 01 Aug '25

01 Aug '25

Wiki - https://fedoraproject.org/wiki/Changes/HareProgrammingLanguage Discussion thread - https://discussion.fedoraproject.org/t/f43-change-proposal-hare-programming… This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == Introduce packages for [https://harelang.org/ Hare], a systems programming language designed to be simple, stable, and robust. Hare is still under development, the language, its standard library and its reference tool chain are still subject to breaking changes. == Owner == * Name: [[User:dridi|Dridi Boukelmoune]], [[User:mroche|Mike Rochefort]], [[User:fnux|Timothee Floure]], [[User:fed500|Benson Muite]] * Email: dridi dot boukelmoune at gmail, mroche at omenos dot dev, timothee dot floure at posteo dot net, benson_muite at emailplus dot org  == Detailed Description == Hare is a systems programming language designed to be simple, stable, and robust. Hare uses a static type system, manual memory management, and a minimal runtime. It is well-suited to writing operating systems, system tools, compilers, networking software, and other low-level, high performance tasks. The Hare tool chain on Fedora will include: * `hare` (build driver) * `harec` (compiler front-end, already available in Fedora) * `qbe` (compiler back-end, already available in Fedora) * `binutils` (for assembly and static linking) * `gcc` (for dynamic linking, it also works with other C compilers) Leaving `binutils` and GCC aside, bootstrapping a Hare tool chain only takes a few minutes. The Hare tool chain can target the `x86_64`, `aarch64` and `riscv64` architectures, and will be configured to rely by default on `gcc-<arch>-linux-gnu` and `binutils-<arch>-linux-gnu` for cross compilation. The `hare` source package will produce the following packages: * `hare` (build driver, `haredoc` utility and manuals) * `hare-stdlib` (standard library) * `hare-rpm-macros` (packaging utilities) In addition, a `hare-update` package will be provided to assist Hare developers deal with breaking changes when a new Hare release is available, until the language and its standard library become stable. == Feedback == None. == Benefit to Fedora == Developers can begin using the Hare language in their projects. Package maintainers can ship applications written in Hare. Unlike other language tool chains, Hare modules are meant to be the responsibility of system package managers like DNF. Packaging Hare modules and applications should result in little friction. == Scope == * Proposal owners: ** submit `hare` and `hare-update` packages for review ** create RPM macros for Hare packaging *** `%hare_arches` already submitted to `redhat-rpm-config` ** handle the `hare` package bootstrap ** add dependency generators for Hare modules ** draft packaging guidelines * Other developers: N/A (not needed for this Change) * Release engineering: N/A (not needed for this Change) * Policies and guidelines: ** There ideally should be Hare packaging guidelines submitted as part of this change, otherwise at a later point. ** See https://pagure.io/packaging-committee/pull-request/1472 * Trademark approval: N/A (not needed for this Change) * Alignment with the Fedora Strategy: none == Upgrade/compatibility impact == The Hare specification is still a draft, so the Hare language, tool chain and standard library are still subject to relatively frequent breaking changes. Package updates containing breaking changes should be limited to Fedora releases. == How To Test == Once the `hare` package is available, the upstream [introduction https://harelang.org/tutorials/introduction] to the language walks you through the hello world below before covering language concepts. Hello world: <pre>$ cat >main.ha <<EOF use fmt; export fn main() void = { fmt::println("Hello world!")!; }; EOF $ hare build -o example main.ha 4/4 tasks completed (100%) $ ./example Hello world!</pre> == User Experience == == Dependencies == None. == Contingency Plan == * Contingency mechanism: N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == * https://harelang.org/documentation/ * https://harelang.org/tutorial * https://harelang.org/specification * https://harelang.org/blog == Release Notes == -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)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-announce@lists.fedorapr… Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

3 5

long latencies on fedpkg srpm
by Leo Sandoval 01 Aug '25

01 Aug '25

This week I am experimenting long latencies when running `fedpkg srpm` (around 5 minutes, real time). `strace -c fedpkg srpm` is telling me that the 'wait4' syscall is the one consuming most of the time (85%) My network connection is not the fastest but running the rhpkg srpm I basically got instant results. Also, I am not sure if these delays started after the data center move but perhaps that may be a factor. Any idea how to debug this one?

3 4

HEADS UP: gdal-3.11.3 landing in rawhide
by Sandro Mani 31 Jul '25

31 Jul '25

Hi I'm building gdal-3.11.3 (as the first Fedora build of the 3.11.x series) in rawhide in the f43-build-side-115762. As it carries as soname bump, I'll be rebuilding the following dependencies: GMT mapserver liblas python-fiona postgis merkaartor mod_mapcache qmapshack PDAL ncl vfrnav python-pyogrio python-rasterio vtk paraview kealib OpenSceneGraph cloudcompare grass mapnik opencv mingw-opencv osgearth qgis gazebo Thanks Sandro

2 2

bodhi testing arguments/environment variables
by Pavol Sloboda 31 Jul '25

31 Jul '25

Hello, I am currently reworking the tests for bodhi for Mariadb from STI to TMT as per the fedora change [0] and I came across an issue with the versioned vs unversioned rpms of Mariadb (this issue seems to be present in the STI tests as well), where the versioned mariadb rpms are named differently than the unversioned ones and I want to preferably keep the same tests for both kinds of packages by setting a flag for tmt or using the `-e` flag (or any other option) in `tmt run` to set an environment variable during the testing process in bodhi. Is there a way to do something like this? How exactly are the tests called inside of bodhi? I have gone over the documentation but I haven't found anything on this topic. [0] https://fedoraproject.org/wiki/Changes/DisableSTI Thank you, Pavol.

4 3

Help needed for scotch FTBFS: illegal instruction of ppc64le - gcc regression?
by Sandro Mani 31 Jul '25

31 Jul '25

Hi scotch is currently FTBFS on ppc64le (affects the current 7.0.7, the previous 7.0.6, as well as the new 7.0.8 release), failing with [1] gmake[2]: *** [src/libscotch/CMakeFiles/ptscotchf_h.dir/build.make:77: src/include/ptscotchf.h] Illegal instruction (core dumped) 7.0.6 previously successfully built with gcc-0:15.0.1-0.3.fc42.1.ppc64le and now fails with gcc-0:15.1.1-5.fc43.1.ppc64le, so this looks like a gcc regression. Being this on ppc64le and having no access to such a machine, how can I debug this? Thanks Sandro [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=135363441

5 12

(Not quite) orphaning mingw-libgnurx (a regex library)
by Richard W.M. Jones 31 Jul '25

31 Jul '25

This is a very basic regexp library that as far as I can tell has no active upstream and hasn't been updated in about a decade. It seems like at some point in the distant past (> 18 years ago) it was extracted from glibc and made to work under mingw, but hasn't been kept up to date with the glibc code. [Please tell me if I'm wrong about this, but I was unable to find much about its history.] It failed in the mass rebuild, but I managed to "rescue" it for now by compiling the package with -std=c99. It also gives lots of non-fatal warnings about modern C stuff. It seems it is not used by any other package in Fedora, assuming my repoquery-fu is right: # dnf repoquery --enablerepo=\* --arch=src --whatrequires mingw-libgnurx (nothing) Probably you should be using PCRE (mingw64-pcre2) instead of this. Anyway I didn't actually orphan it but will do if it causes any more trouble. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW

1 0

← Newer
1
2
3
4
5
6
7
...
22
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel July 2025