Self-Introduction: Peter Pentchev
Hi, My name is Peter Pentchev. I am a software developer who has been wrangling computers since 1986 and free/libre-software OS's and distributions since 1997 (Slackware and RedHat (way before RHEL) at first, then a decade or two of FreeBSD, then a decade or two of Debian). I have maintained packages for FreeBSD since the year 2000, for Debian since 2004-2005, and (unofficially, in personal and vendor repositories) for CentOS and RHEL since 2013. My main interests lie in system and network programming, but I have dabbled in almost all areas of software development over the years with varying degrees of success. My longest programming experience is in C and Perl, but lately I prefer a mixture of Rust, type-checked Python, and, when absolutely necessary, very carefully written POSIX shell and Bash. If my packager group application is accepted, I will try to help several packaging teams within Fedora (Python, Perl, Rust, maybe some other topic-based ones) and probably separately package some tools that I use on a daily basis, some written by me, some by others. Thanks for reading this, and thanks for working on Fedora - it takes so many different kinds of people doing so many different kinds of tasks to create and maintain a working software distrubition! G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org pe...@morpheusly.com PGP key:http://people.FreeBSD.org/~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
[Test-Announce] [Proposal] TestDays Category TestCase Tags
Hello Testers, Fedora QA has been hosting loads of test days for sometime (ie 15 test days/release) which is why we author test cases. These test cases are sometimes for features which may never see the light of day (at least not in that particular release). Sometimes, these test cases are integration test cases and are very hard to categorize in package-specific test cases. Many times, due to their non-blocking nature, they are not associated with "Release Criterion". This makes test cases authored for a particular test day, extremely hard to find and check for bitrot. I propose the following: a) Add a new category Category:CoreOS Test Cases b) Add new Category TestDay:NAME c) We already track the release cycle, Category:Fedora 41 Test Days Benefits: a) In the long run add more filtering functions to testday-stats on test cases added b) Easier navigation of test cases, written just for a test day and updation of the same c) Establishing scope for blocking criteria for upcoming features that get tested in Rawhide Test Days I would like to know your concerns and comments. If people are okay, I can go do the homework :) -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Test-Announce] [RFC] Rawhide Test Days
Hey Folks, Since some time, we have been asking more and more developers to test features as they get to Rawhide or Copr. This gives the community and QA by large, more room to test and find out bugs. Timely done, this effort not only increases the quality of Fedora releases but also gives more time to developers to fix these issues before they become blockers. One part of this process is implementing Rawhide Test Days. Rawhide Test Days aims to use Rawhide as the base to test the upcoming features/changes. The Test Days still follow the vanilla test day SOP[0]. The context of the Rawhide Test Days has been drafted here [1]. This is a good time, for us to register feedback and if you are a team/team member; get involved, feel free to comment in the pagure ticket[2] or this email! Thanks a lot for the continued support and special thanks to DNF5 and the Podman team who participated as pilots and tested their recent features and changes! [0] https://fedoraproject.org/wiki/QA/SOP_Test_Day_management [1] https://fedoraproject.org/wiki/User:Sumantrom/Draft/QA:SOP_Rawhide_TestDay [2] https://pagure.io/fedora-qa/issue/777 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED -- ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
ISPC soversion bumped to 1.24.0
Hello team, ISPC is bumped in version 1.24.0 affecting the following packages: * embree * embree3 * oidn * openvkl Please use the command "fedpkg build --target=f41-build-side-90079" to rebuild the listed packages. Thank you. -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer -- ___ 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: Will there be a gnu/hurd spin when a 64bit hurd is released?
A very very long time ago, I helped set up the filename structure for downloads that Fedora uses now of `/pub/fedora/linux` when I set up the 'new' Red Hat Linux download structure for mirrors in 2000. The reason was that I figured that at some point we might expand to Hurd, a BSD, or other items as products might grow. When Fedora set up its file structure around 2003, this naming structure was kept and has been around for the last 20 years. In that time, it has been proposed multiple times that `we should do a `, but no one has actually done the work to make it happen. It takes a LOT more than just proposing something on a mailing list to make a new port or release work. It takes a lot of hard work to first learn how the other operating system works, how it compiles, can the tools which make an operating system 'Fedora' be ported to that tool, and it then takes the work of making those things happen more than once. At that point, it takes a lot of ground effort to figure out how much of the software in the Fedora ecosystem can be compiled for the new operating system and will actually work in it. Going from the amount of time it took to get the original Debian Hurd and BSD to actually work (with some idea of how much work the people getting a RiscV port have done)... my guess would be it would take about 10-15 people with about 2x that many systems and about 2 to 4 years to get it to a port where it could be 'releasable' outside of that small group of people interested in it. Which I think is why after 24 years, there isn't any other base kernel under /pub/fedora/ than linux. Just getting a port to a new architecture takes anywhere from 5-10 people multiple years to make a stable and repeatable release cycle. These are people who have worked in Linux for a long time and have experience with the many tools which 'make Fedora' with previous porting efforts. It would take people who have been running HURD in some way to know what it does and know how to make things like rpm, mock, dnf work on a different fundamental architecture (Micro kernel based versus unikernel). I wish the people who are interested in it as much luck as I can give. On Mon, 27 May 2024 at 16:39, Ryan Bach via devel < devel@lists.fedoraproject.org> wrote: > That would be awesome. Thoughts? > -- > ___ > 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: Will there be a gnu/hurd spin when a 64bit hurd is released?
Debian seems to be working on it. https://wiki.debian.org/Ports/hurd-amd64 -- ___ 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
Will there be a gnu/hurd spin when a 64bit hurd is released?
That would be awesome. Thoughts? -- ___ 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: FAS login not possible
On 27/05/2024 18.16, Kevin Fenzi wrote: On Mon, May 27, 2024 at 06:07:10PM GMT, Björn Persson wrote: Kevin Fenzi wrote: I am unaware of any recent auth issues aside this kernel app one. Everything has been working great since we moved the ipsilon servers to f39 on march 27th. If there are, please let us know. Logging in to src.fedoraproject.org or pagure.io has been flaky to me in recent weeks. I got Gateway Timeout a few minutes ago when logging in to src.fedoraproject.org. I tried again and then it worked. Other times I've gotten errors when logging in, but when I tried again I was logged in without submitting the login form a second time. It sounds like perhaps a proxy is misbehaving... if there's any way you could enable debug console next time you login and see what proxy you were hitting when the timeout or issue happened that might be good info for us. I can confirm the experiences of Björn. It occurs from time to time. It sometimes is a time out, and sometimes a bad request. I will try to collect data about it and let you know. The issue is the FAS login screen, it is not related to any service that uses its token. -- ___ 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: Roseline Bassey - Community Architect Intern Introduction
Hello, Roseline! On Monday, 27 May 2024 at 17:26, Roseline Bassey wrote: [...] > I’m excited to bring my experience and skills and to contribute to and > support various Fedora teams and the broader community during my > internship. Welcome to Fedora! 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 -- ___ 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: Thunderbird FTBFS f41,f40; suspecting broken Rust bindings generation
Hi, On Monday, 2024-05-27 15:56:30 +0200, Eike Rathke wrote: > I'm out of clues and hopefully someone can provide some insights. Apparently bindgen with clang 18 is broken in this case. Kudos to @sharkcz Dan Horák for a solution to use clang 17 instead. Eike -- GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A 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: FAS login not possible
On Mon, May 27, 2024 at 06:07:10PM GMT, Björn Persson wrote: > Kevin Fenzi wrote: > > I am unaware of any recent auth issues aside this kernel app one. > > Everything has been working great since we moved the ipsilon servers to > > f39 on march 27th. If there are, please let us know. > > Logging in to src.fedoraproject.org or pagure.io has been flaky to me in > recent weeks. I got Gateway Timeout a few minutes ago when logging in to > src.fedoraproject.org. I tried again and then it worked. Other times > I've gotten errors when logging in, but when I tried again I was logged > in without submitting the login form a second time. It sounds like perhaps a proxy is misbehaving... if there's any way you could enable debug console next time you login and see what proxy you were hitting when the timeout or issue happened that might be good info for us. 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: FAS login not possible
Kevin Fenzi wrote: > I am unaware of any recent auth issues aside this kernel app one. > Everything has been working great since we moved the ipsilon servers to > f39 on march 27th. If there are, please let us know. Logging in to src.fedoraproject.org or pagure.io has been flaky to me in recent weeks. I got Gateway Timeout a few minutes ago when logging in to src.fedoraproject.org. I tried again and then it worked. Other times I've gotten errors when logging in, but when I tried again I was logged in without submitting the login form a second time. Björn Persson pgpRSPnk1kLU2.pgp Description: OpenPGP digital signatur -- ___ 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: FAS login not possible
On Mon, May 27, 2024 at 10:45:34AM GMT, Marius Schwarz wrote: > Hi, > > ATM FAS Login is not possible. For you, to what? anything? > The ironic part is: you need to login to take part in the infrastructure > ticket about not able to login ;) > > https://pagure.io/fedora-infrastructure/issue/11949 > > You get this message: > > "400 - Bad Request - Invalid transaction id" > > when you try to login via the website or api. So, that ticket is about the kernel test app: https://kerneltest.fedoraproject.org/ It was changed a while back to use a new auth mode and the script for submitting authenticated results is not currently working. This is tracked in: https://pagure.io/kernel-tests/issue/50 The workarounds include just anonymous submitting, or logging into the web app with a browser and uploading the tests. Hopefully someone will look into this after the long weekend/holiday. So, is it just that you cannot submit kernel test results? Or can you not login to anything else? > Direct messages to "infrastruct...@lists.fedoraproject.org" are also not > possible, you need to be on the list to do that. Yes. If you cannot auth to update/file a ticket: https://docs.fedoraproject.org/en-US/infra/day_to_day_fedora/#_emergencyauthentication_issues I am unaware of any recent auth issues aside this kernel app one. Everything has been working great since we moved the ipsilon servers to f39 on march 27th. If there are, please let us know. 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
Roseline Bassey - Community Architect Intern Introduction
Hello, Fedora devel. My name is Roseline Bassey, and I’m from Nigeria. I’m thrilled to begin my internship today as a Community Architect Intern with Fedora through the Outreachy internship program. My interest in the inner workings of managing global open source communities has driven my passion for community management. This led me to become a community builder for the Women in Cloud Native community. I’m excited to bring my experience and skills and to contribute to and support various Fedora teams and the broader community during my internship. If you need to reach me, I’ll be active on the following platforms: Fedora Discussions: @roseline-bassey Matrix: @roseline:matrix.org Email: roseline-bas...@fedoraproject.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
Disabling Fedora 38 chroots in Copr
Hello, tl;dr, we have just disabled Fedora 38 chroots in Copr. According to the Fedora wiki [1], Fedora 38 reached the end of its life [4] and therefore we are disabling it in Copr. That effectively means that from this moment, it is no longer possible to submit builds for the following chroots: - fedora-38-x86_64 - fedora-38-i386 - fedora-38-ppc64le - fedora-38-aarch64 - fedora-38-armhfp - fedora-38-s390x Additionally, according to Outdated chroots removal policy [2], Copr is going to preserve existing build results in those chroots for another 180 days and then automatically remove them unless you take an action and prolong the chroots life span in your projects. Read more about this feature in the Copr - Removing outdated chroots blog post [3]. [1] https://fedoraproject.org/wiki/End_of_life [2] https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html [3] http://frostyx.cz/posts/copr-removing-outdated-chroots [4] https://fedorapeople.org/groups/schedule/f-40/f-40-all-tasks.html Pavel -- ___ 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
Thunderbird FTBFS f41,f40; suspecting broken Rust bindings generation
Hi, Thunderbird FTBFS on f41 and f40, earlier only f41, I suspect some Rust toolchain problem when generating bindings. Please see https://bugzilla.redhat.com/show_bug.cgi?id=2261180#c7 and following. I'm out of clues and hopefully someone can provide some insights. Thanks Eike -- GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A 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: Tosin Adesola - Community Architect Intern Introduction
Good to see you here Tosin. Welcome :-) On Mon, May 27, 2024 at 9:51 AM TosinDoreen wrote: > Hello Fedora folks!🫡 > > I'm Tosin Adesola, excited to join your ranks as a community architect > intern. I'm calling Nigeria home, and while my Linux experience is mostly > through Outreachy, I'm eager to dive deeper into the Fedora universe. > > Community building is my jam – I love bringing people together, > coordinating events, and making sure everyone feels included. I'm thrilled > to bring that passion to Fedora and learn all I can about Git, tech > writing, and crafting engaging social content. Let's collaborate! > > Connect with me on: > > Email: tosindor...@gmail.com > Matrix: @tosin_doreen:matrix.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 > -- ___ 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
Tosin Adesola - Community Architect Intern Introduction
Hello Fedora folks!🫡 I'm Tosin Adesola, excited to join your ranks as a community architect intern. I'm calling Nigeria home, and while my Linux experience is mostly through Outreachy, I'm eager to dive deeper into the Fedora universe. Community building is my jam – I love bringing people together, coordinating events, and making sure everyone feels included. I'm thrilled to bring that passion to Fedora and learn all I can about Git, tech writing, and crafting engaging social content. Let's collaborate! Connect with me on: Email: tosindor...@gmail.com Matrix: @tosin_doreen:matrix.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
Tosin Adesola - Community Architect Intern Introduction
Hello Fedora folks!🫡 I'm Tosin Adesola, excited to join your ranks as a community architect intern. I'm calling Nigeria home, and while my Linux experience is mostly through Outreachy, I'm eager to dive deeper into the Fedora universe. Community building is my jam – I love bringing people together, coordinating events, and making sure everyone feels included. I'm thrilled to bring that passion to Fedora and learn all I can about Git, tech writing, and crafting engaging social content. Let's collaborate! Connect with me on: Email: tosindor...@gmail.com Matrix: @tosin_doreen:matrix.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
No FESCO meeting today
Hi, We have Memorial Day in the USA and no new topics on the agenda, so I'm cancelling today's meeting. See y'all next weeek! 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
Fedora rawhide compose report: 20240527.n.0 changes
OLD: Fedora-Rawhide-20240526.n.0 NEW: Fedora-Rawhide-20240527.n.0 = SUMMARY = Added images:0 Dropped images: 2 Added packages: 4 Dropped packages:0 Upgraded packages: 40 Downgraded packages: 0 Size of added packages: 1.03 MiB Size of dropped packages:0 B Size of upgraded packages: 496.37 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 15.12 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: KDE live aarch64 Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20240526.n.0.iso Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20240526.n.0.iso = ADDED PACKAGES = Package: loguru-2.2.0^20230406git4adaa18-1.fc41 Summary: A lightweight C++ logging library RPMs:loguru loguru-devel loguru-doc loguru-lnav Size:704.83 KiB Package: mogui-0.2.2-2.fc41 Summary: Graphical User Interface for Environment Modules RPMs:mogui Size:77.86 KiB Package: redfish-finder-0.4-12.fc41 Summary: Utility for parsing SMBIOS information and configuring canonical BMC access RPMs:redfish-finder Size:22.00 KiB Package: rust-ssh-key-0.6.6-1.fc41 Summary: Pure Rust implementation of SSH key file format decoders/encoders RPMs:rust-ssh-key+alloc-devel rust-ssh-key+crypto-devel rust-ssh-key+default-devel rust-ssh-key+dsa-devel rust-ssh-key+ecdsa-devel rust-ssh-key+ed25519-devel rust-ssh-key+encryption-devel rust-ssh-key+getrandom-devel rust-ssh-key+p256-devel rust-ssh-key+p384-devel rust-ssh-key+p521-devel rust-ssh-key+rand_core-devel rust-ssh-key+rsa-devel rust-ssh-key+serde-devel rust-ssh-key+std-devel rust-ssh-key+tdes-devel rust-ssh-key-devel Size:247.96 KiB = DROPPED PACKAGES = = UPGRADED PACKAGES = Package: bcm283x-firmware-20240524-1.458df3a.fc41 Old package: bcm283x-firmware-20240229-3.dc94391.fc41 Summary: Firmware for the Broadcom bcm283x/bcm271x used in the Raspberry Pi RPMs: bcm2711-firmware bcm2835-firmware bcm283x-firmware bcm283x-overlays Size: 7.01 MiB Size change: 11.07 KiB Changelog: * Sun May 26 2024 Peter Robinson - 20240524-1.458df3a - Update to latest firmware Package: bubblemail-1.9-1.fc41 Old package: bubblemail-1.8-9.fc40 Summary: Extensible mail notification service RPMs: bubblemail Size: 1.05 MiB Size change: -5.10 KiB Changelog: * Sun May 26 2024 Alexander Ploumistos - 1.9-1 - Update to 1.9 Package: cppcheck-2.14.1-1.fc41 Old package: cppcheck-2.14.0-1.fc41 Summary: Tool for static C/C++ code analysis RPMs: cppcheck cppcheck-gui cppcheck-htmlreport Size: 18.73 MiB Size change: 25.55 KiB Changelog: * Sun May 26 2024 Wolfgang St??ggl - 2.14.1-1 - Update to 2.14.1 Package: crawl-0.31.0-1.fc41 Old package: crawl-0.30.2-2.fc40 Summary: Roguelike dungeon exploration game RPMs: crawl crawl-common-data crawl-tiles Size: 123.04 MiB Size change: 3.29 MiB Changelog: * Sun May 26 2024 Antonio Trande - 0.31.0-1 - Release 0.31.0 Package: dvgrab-3.5-35.20231130git8a368f4.fc41 Old package: dvgrab-3.5-34.20160616gite46042.fc40 Summary: Utility to capture video from a DV camera RPMs: dvgrab Size: 401.39 KiB Size change: -162 B Changelog: * Sun May 26 2024 Antonio Trande - 3.5-35.20231130git8a368f4 - Commit 8a368f4 Package: faketpm-0.0.1-2.fc41 Old package: faketpm-0.0.1-1.fc41 Summary: Fake TPM for systems that lack a real one RPMs: faketpm faketpm-selinux Size: 30.94 KiB Size change: 215 B Changelog: * Sun May 26 2024 Davide Cavalca - 0.0.1-2 - Tighten permissions for the TPM state Package: freedroidrpg-1.0-5.fc41 Old package: freedroidrpg-1.0-5.fc40 Summary: Role playing game with Freedroid theme and Tux as the hero RPMs: freedroidrpg freedroidrpg-data Size: 227.30 MiB Size change: -613 B Package: gdcm-3.0.23-6.fc41 Old package: gdcm-3.0.23-5.fc41 Summary: Grassroots DiCoM is a C++ library to parse DICOM medical files RPMs: gdcm gdcm-applications gdcm-devel gdcm-doc python3-gdcm Size: 14.44 MiB Size change: -5.20 KiB Changelog: * Mon May 27 2024 Benjamin A. Beasley - 3.0.23-6 - Fix unowned directory /usr/share/gdcm-3.0/ Package: golang-github-burntsushi-toml-1.4.0-1.fc41 Old package: golang-github-burntsushi-toml-1.2.0-5.fc40 Summary: TOML parser for Golang with reflection RPMs: golang-github-burntsushi-toml golang-github-burntsushi-toml-devel Size: 4.44 MiB Size change: 37.98 KiB Changelog: * Sun Feb 11 2024 Maxwell G - 1.2.0-6 - Rebuild for golang 1.22.0 * Sun May 26 2024 Mikel Olasagasti Uranga - 1.4.0-1 - Update to 1.4.0 - Closes rhbz#2283185 Package: jupyterlab-4.2.1-1.fc41 Old package: jupyterlab-4.2.0-1.fc41 Summary: JupyterLab computational environment RPMs
Intent to bump SVT-AV1
Hello, This week, I will rebuild svt-av1 and its dependencies in a side tag. Tests were done this weekend on COPR and compatibility with FFmpeg 6.1.1 was determined to be functional. I will need the help from RPM fusion people. Libheif and Libheif-freeworld will be updated during the process (minor release but allow to build with svt-av1). It will also backport a fix for a small CVE. Best regards, Robert-André -- ___ 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: Node.js 22.x coming to Rawhide/F41
Yes thanks, for some reason COPR pulled the release -1 during my build instead of -9. It works now. Best regards, Robert-André On Mon, May 27, 2024, 02:07 Sérgio Basto wrote: > On Sun, 2024-05-26 at 21:29 +0200, Robert-André Mauchin wrote: > > On 21/05/2024 15:53, Stephen Gallagher wrote: > > > tl;dr I screwed up and accidentally made two critical mistakes: > > > > > > 1) Node.js 22 got into Rawhide as the default early. I'm not sure > > > of > > > how to back that out safely. > > > 2) A change made in Node.js 20 to split out two libraries > > > (cjs-module-lexer and undici) that we were bundling in prior > > > releases > > > has introduced issues with Node.js 22 because it can't find them > > > (and > > > the ones from Node.js 20 are older). I'll probably re-bundle them > > > in > > > the short term to unbreak things. > > > > Hello, > > > > Do we have a fix for this, I still see several package failure. Do we > > have to change something in dependent SPEC? > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2282103 > > nodejs22-22.2.0-9.fc41 works for me > > > Thanks, > > > > Robert-André > > -- > > ___ > > 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 > > -- > 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 > -- ___ 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: FAS login not possible
Hey Marius, Once try by removing cache also. May be it'll work. On 27/05/24 14:41, Christopher Klooz wrote: Unfortunately, such errors are not a seldom phenomenon (at least in my case). You can try again, it will work at some time usually. I have seen bad request and time outs so far. Usually trying it again once or twice should be enough. In any case, do not return with the button but refresh the login page before the next attempt. Just to ensure this is not the issue. We had topics in discourse and such about the issue before, but I expect it is indirectly a matter of money for infra. If you still experience the issue, you should contact ad...@fedoraproject.org -> they can help you in such cases, and you do not need to login 🙂 You can expect a quick and helpful response there. Best, Chris On 27/05/2024 10.45, Marius Schwarz wrote: Hi, ATM FAS Login is not possible. The ironic part is: you need to login to take part in the infrastructure ticket about not able to login ;) https://pagure.io/fedora-infrastructure/issue/11949 You get this message: "400 - Bad Request - Invalid transaction id" when you try to login via the website or api. Direct messages to "infrastruct...@lists.fedoraproject.org" are also not possible, you need to be on the list to do that. best regards, Marius Schwarz -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ 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: FAS login not possible
Unfortunately, such errors are not a seldom phenomenon (at least in my case). You can try again, it will work at some time usually. I have seen bad request and time outs so far. Usually trying it again once or twice should be enough. In any case, do not return with the button but refresh the login page before the next attempt. Just to ensure this is not the issue. We had topics in discourse and such about the issue before, but I expect it is indirectly a matter of money for infra. If you still experience the issue, you should contact ad...@fedoraproject.org -> they can help you in such cases, and you do not need to login 🙂 You can expect a quick and helpful response there. Best, Chris On 27/05/2024 10.45, Marius Schwarz wrote: Hi, ATM FAS Login is not possible. The ironic part is: you need to login to take part in the infrastructure ticket about not able to login ;) https://pagure.io/fedora-infrastructure/issue/11949 You get this message: "400 - Bad Request - Invalid transaction id" when you try to login via the website or api. Direct messages to "infrastruct...@lists.fedoraproject.org" are also not possible, you need to be on the list to do that. best regards, Marius Schwarz -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
FAS login not possible
Hi, ATM FAS Login is not possible. The ironic part is: you need to login to take part in the infrastructure ticket about not able to login ;) https://pagure.io/fedora-infrastructure/issue/11949 You get this message: "400 - Bad Request - Invalid transaction id" when you try to login via the website or api. Direct messages to "infrastruct...@lists.fedoraproject.org" are also not possible, you need to be on the list to do that. best regards, Marius Schwarz -- ___ 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: Adding additional flag in cmake-rpm-macros to disallow the use of the FetchContent module
On 2024/05/27 10:09, Vitaly Zaitsev via devel wrote: On 27/05/2024 02:46, Kan-Ru Chen wrote: It is documented that FIND_PACKAGE_ARGS argument in FetchContent_Declare should instruct it to find system packages first. This only works as expected in very rare cases. The library name in FetchContent() must match the name in find_package(). In principle this can be handled with FIND_PACKAGE_ARGS + NAMES. But there are more nuances that the dependent project must have compatibility ALIAS targets, or equivalent handling on the consumer side. Overall I think the upstream packages should make these transitions, and wherever possible Fedora packagers should help propose these. Regarding FETCHCONTENT_FULLY_DISCONNECTED=ON, I think that could be a good idea, but it needs a bit more implementation to work, e.g. exposing the FetchContent deps folder so that we can populate them manually. This would be the equivalent of the vendored packaging in go or rust, where we specify additional Source to be downloaded. This would not be a recommended packaging process, but it's good to reduce the initial workload when dealing with dependency chains. -- ___ 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: Adding additional flag in cmake-rpm-macros to disallow the use of the FetchContent module
On 27/05/2024 02:22, Byoungchan Lee via devel wrote: In well-maintained Fedora packages, the use of the FetchContent module is generally discouraged because dependencies are already available in the Fedora repositories. FetchContent never worked on Fedora because the builders have no network access. The maintainers have to patch it out. Check this for example: https://github.com/eliaskosunen/scnlib/pull/112 While it's uncertain if build workers in Fedora have internet access, to improve security, I believe it is recommended to entirely disallow the use of the FetchContent module. To achieve this, I propose adding a flag in the cmake-rpm-macros to disable the FetchContent module. Tried it several times, but it doesn't work reliably and in very rare cases. The library name in FetchContent() must match the name in find_package(), which almost never happens in real projects. It will instantly fail but with another error. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.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: Adding additional flag in cmake-rpm-macros to disallow the use of the FetchContent module
On 27/05/2024 02:46, Kan-Ru Chen wrote: It is documented that FIND_PACKAGE_ARGS argument in FetchContent_Declare should instruct it to find system packages first. This only works as expected in very rare cases. The library name in FetchContent() must match the name in find_package(). This is probably going to break packages. I think a change proposal would be good. No, this won't break anything since Fedora builders have no network access and all FetchContent() calls will fail instantly. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.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: [Test-Announce] Kernel 6.9 Test Week 2024-05-26 to 2024-06-02
On 26/05/2024 12:36, Alicja Brook wrote: As usual, the Fedora QA team will hangout at #fedora-test-day(a)libera.chat The LiberaChat Matrix gate has been closed and all chats are now only available in Matrix. You should replace all links with #fedora-test-day:fedoraproject.org. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.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
