devel January 2024

devel@lists.fedoraproject.org

163 participants
252 discussions

runaway fork() in Lua script
by Jerry James 30 Jan '24

30 Jan '24

For the second time in two days, running "fedpkg build" gave me a few dozen lines that say: warning: runaway fork() in Lua script before the usual build messages start appearing. Is this a known issue? It looks like I am not the only one to encounter this: https://github.com/QubesOS/qubes-issues/issues/8771 -- Jerry James http://www.jamezone.org/

3 2

Fedora Linux 40 Mass Rebuild Finished
by Samyak Jain 30 Jan '24

30 Jan '24

Hi all, Per the Fedora Linux f40 schedule and the challenges [1], we started a mass rebuild for Fedora Linux f40 on 2024-01-22. We did a mass rebuild for Fedora Linux f40 for changes like: - https://fedoraproject.org/wiki/Changes/GNUToolchainF40 - https://fedoraproject.org/wiki/Changes/Java21 check the tracker for more details: https://pagure.io/releng/issues?status=Open&tags=mass+rebuild&tags=f40&tags… The mass rebuild was done in a side tag (f40-rebuild) and moved over to f40. Failures can be seen at https://kojipkgs.fedoraproject.org/mass-rebuild/f40-failures.html Things still needing rebuilding https://kojipkgs.fedoraproject.org/mass-rebuild/f40-need-rebuild.html 21971 builds have been tagged into f40, there are currently 991 failed builds that need to be addressed by the package maintainers. FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng by dropping an email to our list [2], or joining #releng:fedoraproject.org on Matrix, or filing an issue in pagure [3]. Regards, Samyak Jain Fedora Release Engineering [1] https://fedorapeople.org/groups/schedule/f-40/f-40-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ -- _______________________________________________ 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

1 0

[Test-Announce] [Test Day] Fedora 40 KDE Plasma 6 2024-01-29 through 2024-02-05
by Sumantro Mukherjee 29 Jan '24

29 Jan '24

Hey Folks, KDE SIG x Fedora QA hosts the KDE Plasma 6 Test Week. If you are willing to test new Desktop Environments or use KDE for some time; this is your time. Contribute to testing the new KDE and finding bugs ahead of the F40 release. The instructions are simple, and can be found in the wiki[0] and the results can be submitted on the results page[1] [0] https://fedoraproject.org/wiki/Test_Day:2024-01-29_KDE_Plasma_6_Test_Week [1] https://testdays.fedoraproject.org/events/174 Happy Testing! -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- _______________________________________________ test-announce mailing list -- test-announce(a)lists.fedoraproject.org To unsubscribe send an email to test-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/test-announce@lists.fedorapro… Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

1 0

Announce: Log Detective - AI tool to analyze build logs failures
by Jiri Kyjovsky 29 Jan '24

29 Jan '24

Hey, Fedora devs! Ever find yourself lost in the labyrinth of build logs, desperately seeking the elusive culprit behind a failed build? Enter Log Detective – your future personal AI guru dedicated to unravelling the mysteries of build log failures within the RPM community. *What is Log Detective?* Log Detective will be an AI tool for analyzing failed build logs in the RPM community. We are currently in the early stage of development and plan to train the AI using real-world data from maintainers, creating a specialized model for error identification. Thus we created a data collection portal [1], where you can contribute your failed build logs. *Why Log Detective?* Diving into build logs feels like navigating a jungle of thousands of lines. When a build fails, spotting the glitch easily turns into a head-scratcher even for pros. "ERROR" in logs doesn't guarantee always a quick fix, and these errors don't reveal themselves at the log's end. Untangling this requires a keen understanding of packaging difficulties. *Help us shape the future of Log Detective!* We're reaching out to developers like you to contribute by uploading your recent failed build logs on our website [1] and explaining why the build failed. Your input is crucial in building the dataset that will train Log Detective's AI model. By participating, you're playing a key role in creating a tool to streamline error resolution for the entire RPM community. Join us in making Fedora even more powerful! *How to contribute data to Log Detective data collection website?* Visit log-detective.com [1] and share your recent failed build. We can fetch the logs from build systems like Copr [2], Koji [3], services like Packit [4] or arbitrary URL. Highlight the lines in the log associated with the failure and describe how it can be fixed. The more detailed, the merrier for our final tool, and the more hints for you and other developers when your build fails in future. *Join the Log Detective!* Drop by our GitHub repository [5] to share your ideas. Let's collaborate to build a tool that changes the game for handling build log failures. Log Detective isn't just a tool, it's your AI sidekick for defeating build log challenges. Be part of the revolution! Cheers, The Log Detective Crew [1] - https://log-detective.com/ [2] - https://copr.fedorainfracloud.org/ [3] - https://koji.fedoraproject.org/ [4] - https://packit.dev/ [5] - https://github.com/fedora-copr/log-detective-website

3 3

Intend to unretire stgit
by Felix Maurer 29 Jan '24

29 Jan '24

Hi, I intend to get stgit unretired and want to maintain it in the future. The package has been in Fedora up to f38 but has since been orphaned and, following that, retired. The reason for orphaning it was lack of time of the maintainer, especially as stgit got rewritten in Rust and required significant packaging effort to get all dependencies into Fedora. The dependencies are now all packaged (thanks to all the packagers dealing with these numerous Rust dependencies!). As stgit has been retired for a while, a re-review is needed. I already created the review request for stgit at [1]. Thanks, Felix [1]: https://bugzilla.redhat.com/show_bug.cgi?id=2260849

1 0

SWIG 4.2 Python transition
by Florian Weimer 29 Jan '24

29 Jan '24

Quoting CHANGES from SWIG 4.2.0: “ 2023-12-20: wsfulton #2190 Replace SWIG_Python_str_AsChar with SWIG_PyUnicode_AsUTF8AndSize. SWIG_Python_str_AsChar has undefined behaviour when Py_LIMITED_API is defined as it returns a pointer to a string in a PyBytes object that no longer exists. SWIG_PyUnicode_AsUTF8AndSize is an efficient replacement, but requires a different API and the caller to decrement the refcount on the intermediate PyObject in the Py_LIMITED_API < 0x030A0000 implementation. The alternative would have required copying the returned char * string as was done in a previous implementation requiring a call to the defunct SWIG_Python_str_DelForPy3 function. *** POTENTIAL INCOMPATIBILITY *** ” This function is somewhat widely used: <https://codesearch.debian.net/search?q=SWIG_Python_str_AsChar&literal=1> I tried to fix the ldns bindings like this: diff --git a/contrib/python/ldns_rdf.i b/contrib/python/ldns_rdf.i index 5d7448fd..60daf1a7 100644 --- a/contrib/python/ldns_rdf.i +++ b/contrib/python/ldns_rdf.i @@ -56,7 +56,11 @@ */ %typemap(arginit, noblock=1) const ldns_rdf * { +#if SWIG_VERSION >= 0x040200 + PyObject *$1_bytes = NULL; +#else char *$1_str = NULL; +#endif } /* @@ -66,11 +70,17 @@ %typemap(in, noblock=1) const ldns_rdf * (void* argp, $1_ltype tmp = 0, int res) { if (Python_str_Check($input)) { + const char *argstr; +#if SWIG_VERSION >= 0x040200 + argstr = SWIG_PyUnicode_AsUTF8AndSize($input, NULL, &$1_bytes); +#else $1_str = SWIG_Python_str_AsChar($input); - if ($1_str == NULL) { + argstr = $1_str; +#endif + if (argstr == NULL) { %argument_fail(SWIG_TypeError, "char *", $symname, $argnum); } - tmp = ldns_dname_new_frm_str($1_str); + tmp = ldns_dname_new_frm_str(argstr); if (tmp == NULL) { %argument_fail(SWIG_TypeError, "char *", $symname, $argnum); } @@ -90,10 +100,17 @@ */ %typemap(freearg, noblock=1) const ldns_rdf * { +#if SWIG_VERSION >= 0x040200 + if ($1_bytes != NULL) { + /* Is not NULL only when a conversion form string occurred. */ + Py_XDECREF($1_bytes); + } +#else if ($1_str != NULL) { /* Is not NULL only when a conversion form string occurred. */ SWIG_Python_str_DelForPy3($1_str); /* Is a empty macro for Python < 3. */ } +#endif } %nodefaultctor ldns_struct_rdf; /* No default constructor. */ Submitted upstream as <https://github.com/NLnetLabs/ldns/pull/232>. Maybe that will get some useful comments; I don't know much about SWIG. (The core of the change above is the call to SWIG_PyUnicode_AsUTF8AndSize and Py_XDECREF call for the bytes object.) In the past, this kind of problem would have just compiled and resulted in a run-time error when the Python extension module is loaded. In some cases, issues went completely unnoticed because the Python bindins were unused. But with GCC 14, it is necessary to fix calls to undeclared functions. Thanks, Florian

2 1

Self Introduction: Neftali Yagua
by Neftalí Yagua 29 Jan '24

29 Jan '24

Dear Community! My name is Neftalí Yagua, a Software Engineer from Venezuela since 2004, I'm worked with Linux since 1997, my beginnings with RHEL have been with RedHat, but I have been using Fedora for about 10 years, and I love it, I want to be an active part of the community, develop and maintain sources for Fedora. I would even like to make a distribution based on Fedora. I am currently working on the development of plugins for Cockpit, to try to integrate myself and at the same time have some control over the projects. http://links.neftaliyagua.com/ls/click?upn=lAjBpxZAYTGU0gh6HQsXzgI75bmeb7Uj… Additionally, I will be collaborating with the translations into Spanish. I have experience in multiple programming languages. Please, if you think I can contribute something to a project you are working on, invite me. http://links.neftaliyagua.com/ls/click?upn=lAjBpxZAYTGU0gh6HQsXzi95GQNLYugm… http://links.neftaliyagua.com/ls/click?upn=lAjBpxZAYTGU0gh6HQsXzuW-2BqCohBe… http://links.neftaliyagua.com/ls/click?upn=lAjBpxZAYTGU0gh6HQsXzr8QK3Perh2B… Linux User: 507122 Ubuntu User: 30642 -- Regards, Neftali Yagua

2 1

Self Introduction: Jacek Migacz
by Jacek Migacz 29 Jan '24

29 Jan '24

Dear Community! My name is Jacek Migacz; a software engineer from Poland. I'm currently maintaining curl and emacs on Red Hat Enterprise Linux. I am eager to learn from the collective wisdom of the community and contribute in meaningful ways. -- Regards, Jacek

3 2

mingw packaging: equivalent of %cmake_build, %cmake_install macros?
by Eric Smith 29 Jan '24

29 Jan '24

I'm trying to add mingw build support to the fmt package spec. I've done this previously with the pugixml and zipios packages, and submitted the spec diffs to the package maintainer of those.. Both packages use cmake. Both in the %build section use %cmake then %cmake_build, and in the %install section use %cmake_install. As expert neither on cmake nor on mingw, I'm somewhat baffled as to why there are %cmake_build and %cmake_install macros, but no corresponding %mingw_cmake_build and %mingw_cmake_install macros. Is there some equivalent that just happens to not be obvious to me? What I found worked for both pugixml and zipios was: original: %cmake; %cmake_build original install: %cmake_install added for mingw build: %mingw_cmake (and did not add anything equivalent to %cmake_build) added for mingw install: %mingw_make_install; %{?mingw_debug_install_post) Unfortunately this simple attempt failed for fmt. The %mingw_cmake doesn't cause an error, but also doesn't build fmt. The attempted %mingw_make_install results in: "make: *** No rule to make target 'install'. Stop." Perhaps this has to do with the fmt build also using Ninja, which pugixml and zipios do not. If anyone can offer advice, it would be much appreciated. I started from the specs from the packages: pugixml-1.13-4 zipios-2.2.5.0-7 fmt-10.0.0-3 My modified spec files are at: http://www.brouhaha.com/~eric/fedora-packaging-test/ Best regards, Eric @brouhaha

2 1

Next Open NeuroFedora Meeting: Monday, 29 January 2024 (today) at 13:00 UTC
by Sandro 29 Jan '24

29 Jan '24

Hello everyone, Please join us at the next Open NeuroFedora team meeting on Monday, 29 January 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+… or you can use this command in a terminal: $ date --date='Monday, 13:00 UTC' The meeting will be chaired by @Penguinpee. 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+m… - 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 for F40: 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/01/26/next-open-neurofedora-meetin… You can learn more about NeuroFedora here: https://neuro.fedoraproject.org Cheers, -- Sandro FAS: gui1ty Matrix: Penguinpee Elsewhere: [Pp]enguinpee

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
26
Older →

Jump to page:

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 January 2024