Re: Figure out what killed an app (rhbz#2253099)
On Sun, 2024-02-04 at 14:03 +0200, Yanko Kaneti wrote: > The kernel killing the main evolution process which was set as having > rt priority by some webkit coincidence. Hi, there it is then. I see those: > Jan 31 10:49:22 localhost.localdomain rtkit-daemon[826]: > Successfully made thread 4820 of process 4640 (/usr/bin/evolution) > owned by '1000' RT at priority 5. in the journal make more sense now. Thank you all for the help on this. Bye, Milan -- ___ 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] 2024-02-05 @ 16:00 UTC - Fedora QA Meeting
# Fedora Quality Assurance Meeting # Date: 2024-02-05 # Time: 16:00 UTC (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) # Location: https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org Greetings testers! It's meeting time again, and once again we'll be on Matrix. If anyone has any other items for the agenda, please reply to this email and suggest them! Thanks. == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Fedora 40 check-in 3. Test Day / community event status 4. Open floor -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ 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
Re: suitesparse update/soname bump coming this weekend
Update has been submitted: https://bodhi.fedoraproject.org/updates/FEDORA-2024-a8ac931a22 Everything has been rebuilt except for julia which seems to be FTBFS due to tests never completing. On 2/1/24 17:48, Orion Poplawski wrote: I will be updating suitesparse to 7.6.0 with a new cmake build system. This is also a soname bump and I'll be rebuilding the deps in a side-tag. $ fedrq whatrequires suitesparse -F source ceres-solver coin-or-Clp freefem++ gegl04 glpk libpano13 naev octave psblas3 python-cvxopt qrmumps suitesparse sundials superlu_dist -- ___ 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 -- Orion Poplawski he/him/his - surely the least important thing about me IT Systems Manager 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
Tom Seewald wrote: > You were implying that Kevin was claiming to be an "unbiased observer" and > that him being banned from the KDE SIG means he has ulterior motives for > this beyond simply maintaining Plasma X11 packages. To make this clear, my motivation for maintaining Plasma X11 packages is very simple: I use Plasma on X11 daily and do not want to be forced to use Wayland. Oh, and I have also publicly promised [https://discussion.fedoraproject.org/t/f40-change-proposal-kde-plasma-6-system-wide/89794/5] I would submit those packages for review, and I tend to keep my promises. There is nothing more to it. Kevin Kofler -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
Naheem Zaffar wrote: > Wouldn't it be better to create a new totally different named SIG? > > Since bug reporting and crossover of people assuming it is official fedora > plasma are the concerns, a totally independent named SIG and an > independently named desktop should be considered serious options as that > way the extra work can be avoided for the current KDE SIG. > > That way you can even have a desktop with a different name so people will > not think to file bug reports with plasma etc., avoiding problems with > overloading the SIG with work. What I am packaging is still called KDE Plasma upstream, so calling it something completely different would be really confusing to the users and also fail to attribute upstream KDE Plasma for their work. (Keep in mind that upstream KDE is NOT dropping X11 support from Plasma/KWin.) Also, as explained here: https://pagure.io/fesco/issue/3165#comment-894020 I do not think making the packages completely independent of the Plasma packages (as calling it something completely different would likely imply) would be a good idea from a technical standpoint. If we want us Plasma on X11 maintainers to become a formal SIG, it will have to be named something like "KDE X11 SIG" or "Plasma X11 SIG" or some combination thereof. Kevin Kofler -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Fri, Feb 02, 2024 at 11:08:15AM +, Neal Gompa wrote: > On Fri, Feb 2, 2024 at 10:47 AM Peter Hutterer > wrote: > > > > On Thu, Feb 01, 2024 at 03:40:24PM +, Sérgio Basto wrote: > > > On Thu, 2024-02-01 at 15:31 +0100, Leon Fauster via devel wrote: > > > > Am 01.02.24 um 14:18 schrieb Sérgio Basto: > > > > > > > > > > > > > The problem is not KDE SIG not support X11, the problem is KDE SIG > > > > > want > > > > > drop X11 and force user to use wayland . > > > > > > > > > > > > Looking from the side I wonder If its the SIG or more the > > > > circumstances > > > > that everything is in a forward flow and the SIG is facing it. So, if > > > > the best time was not two or one year ago, and obviously also not > > > > now. > > > > When then? The fact is that there must be a point in time when the > > > > display server takes an evolution step forward. > > > > > > > > Pressure in such transition helps to get forward, so I understand the > > > > SIGs POV. Albeit, from the practical POV there are some issue and > > > > therefore X11 is still the place to be. > > > > > > > > Maybe some elaboration should be done about the current state of X11 > > > > vs > > > > Wayland (is it just nvidia?) and a timeframe calculation to have a > > > > resolution. Maybe it won't look so bad then and a interim solution is > > > > then more acceptable. > > > > > > > > > I have an obvious answer is when the authors decide, in this case Xorg, > > > when Xorg decides that it will stop supporting X11, like happened to > > > Python2 or PHP5 and 7 or Gnome > > > > X.org (the ppl doing X development) doesn't work that way, there won't > > be an official "we're no longer supporting this". More likely > > development will languish (except for Xwayland) and actual Xorg releases > > will be few and far in between, at unpredictable cadence and subject to > > someone wanting to do it. > > > > The last Xorg release (21.0) from the master branch was in Oct 2021. The > > only reason that one happened was because Povilas (who wanted a new > > feature in X) stepped up and did the work of collecting the MRs and > > doing the release maintainership. Every 21.x release since has been > > backports and, especially more recently, a huge percentage are CVE fixes. > > > > Fedora still ships the previous release, server 1.20.x, which was > > originally released from git master in 2018, the 1.20.14 version we're > > on (excluding fixes and CVEs) is from Dec 2021. > > > > Xwayland on the other hand (which lives in the same git repo) continues > > on its merry way with the 23.2 series branched as recently as last > > August. But an Xwayland release does not include Xorg because, well, > > there is little motivation to do more Xorg releases. > > > > When it comes down to it it "just" needs someone (trustworthy enough) to > > step up and do them. Whether the releases get picked up immediately like in > > the olden days is a different matter. But I doubt there'll be an X.org > > statement of "we no longer support Xorg" anytime soon, even though that > > is, to some extent functionally already true. > > > > And even before that, things were already only limping along. That was > happening for over a decade and in that timeframe *nobody* has wanted > to step up and work on it. Wayland is the future because otherwise we > have no graphics future, as things currently stand. It also doesn't help that the "it's the same people working on X and Wayland" argument means that, absent significant breakthroughs in space-time research, we can work on one or the other, not both. Something's got to give. Cheers, Peter > > This is why *every* graphical environment is *finally* working on > their Wayland environments if they have any development resources at > all. Last year, we had Cinnamon release its own experimental Wayland > session with v6.0. Budgie is working on replacing X11 with Wayland > this year. LXQt will be on Wayland with v2. Xfce is working on the > same for v4.20. MATE is looking at Wayfire after previously looking at > Mirco for Wayland. Pantheon has been working on it for over a year now > and has an experimental session. > > Everyone is making a path to Wayland a priority because finally enough > is done so that they can. -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Sun, Feb 4, 2024 at 9:04 PM Kevin Kofler via devel wrote: > > Jonathan Bennett via devel wrote: > > the KDE SIG doesn't have a track record of handing those kind of bans out > > flippantly. > > That is what they want you to believe. Sure, this used to be the case, a few > years ago. > “Understanding is a three-edged sword: your side, their side, and the truth.” - JMS I am uninterested in your side, nor their side, and I do not believe anyone has the full truth to share. -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Sun, 4 Feb 2024, 23:16 Sérgio Basto, wrote: > On Sun, 2024-02-04 at 03:55 +0100, Kevin Kofler via devel wrote: > > Neal Gompa wrote: > > > It's extremely obvious that people want to use it. You replied to > > > someone who did and denigrated their opinion. Frankly, I'm > > > disappointed in your response as well as the tone of you and Kevin. > > > > I cannot really speak for Sérgio. I do think his choice of words in > > the > > particular mail you are referring to could have been better. (In > > particular, > > I would not have used the word "crap" there.) But please keep in mind > > that > > he (like me) is not a native English speaker. > > > > I haven't time to read all messages on this thread > > My conclusion is, we have false arguments , that Xorg is old, that is > not maintained, that will give more work , even we got some lies on > some arguments and when we disassemble these arguments, they came up > with new ones, now is the tone . I know would be very fancy only have > wayland , modern etc etc . But the true is they have the work of > remove X11 and not the opposite. > > Other thought it is obvious that KDE 6 will be a disaster, I remember > Kevin step up from leader of KDE SIG, after move from KDE 3 for 4 or 4 > for 5 because the work was too much and we need have a life. > > And the problem here is, we haven't an agreement , since the first day > of proposal many people said that was not acceptable and there opinions > were ignored and the proposal haven't changed one bit. > > I think, I and Kevin so be added to the KDE SIG , please add me at > least (here is the request) . Wouldn't it be better to create a new totally different named SIG? Since bug reporting and crossover of people assuming it is official fedora plasma are the concerns, a totally independent named SIG and an independently named desktop should be considered serious options as that way the extra work can be avoided for the current KDE SIG. That way you can even have a desktop with a different name so people will not think to file bug reports with plasma etc., avoiding problems with overloading the SIG with work. > > I think is stupid and a waste of energy, IMO, do a kwin-x11 and plasma > -x11 , like I said KDE SIG had the work of remove X11 from the builds, > to enable kwin-x11 on Fedora Rawhide is just set %bcond to 1 on > kwin.spec [1] and plasma-workspace.spec [2], so I think that should be > enable. > Another way is build the entire package with X11 and conflict with the > original because will give us less work and we will have less doubts or > user use packages from KDE SIG or user use packages from KDE-X11 SIG > and can't use both. Like happens with ffmpeg where also Neal haven't > reach to an agreement with members of RPMFusion , so now we have ffmpeg > from RPMFUSion with one freeworld sub-package and we have fffmpeg-free > from Fedora and ffmpeg(s) conflicts each other . > > It never happened to me such thing , except recently and all cases with > Neal directly involved, so I see Neal as the problem, was ImageMagick , > was ffmpeg, was LSB , now KDE and one honest advice for Neal who > appears everywhere, try to do fewer things but be more focused > > > [1] > https://src.fedoraproject.org/rpms/kwin/blob/rawhide/f/kwin.spec#_2 > > [2] > > https://src.fedoraproject.org/rpms/plasma-workspace/blob/rawhide/f/plasma-workspace.spec#_2 > > > > > > I can, though, speak for myself, and I am frankly surprised that you > > are > > offended by the tone of my messages. Are you sure that it is not the > > content > > that upsets you rather than the tone? And if it is, try asking you > > why the > > content upsets you. Maybe because it points out inconvenient facts? > > > > > Neither of you are aligning with the Fedora Foundation of Friends, > > > and > > > the personal attacks were unwarranted and unwanted. > > > > We (the KDE SIG and me) stopped being Friends when you (the KDE SIG) > > unilaterally decided to ban me from all your communication channels, > > a ban > > that has still not been lifted years after the alleged misconduct (on > > IRC > > only, but the ban was extended to the mailing list and even your > > Pagure > > issue trackers!) you accused me of. > > > > Nevertheless, I am really trying hard to not make this personal. What > > I > > disagree with is the technical decision to remove X11 support from > > the > > Fedora Plasma packaging. I also objected right when you filed your > > Change > > Proposal that the KDE SIG has no authority to declare in the Change > > that > > Fedora will NOT ship something because other packagers are free to > > package > > it. A belief that at the time was actually shared by the KDE SIG, or > > at > > least by the one KDE SIG member who has publicly commented on it: > > > https://discussion.fedoraproject.org/t/f40-change-proposal-kde-plasma-6-system-wide/89794/11 > > Though the wording in the Change Proposal was not changed. Possibly > > because > > you did not believe at the
Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On Sun, 2024-02-04 at 03:55 +0100, Kevin Kofler via devel wrote: > Neal Gompa wrote: > > It's extremely obvious that people want to use it. You replied to > > someone who did and denigrated their opinion. Frankly, I'm > > disappointed in your response as well as the tone of you and Kevin. > > I cannot really speak for Sérgio. I do think his choice of words in > the > particular mail you are referring to could have been better. (In > particular, > I would not have used the word "crap" there.) But please keep in mind > that > he (like me) is not a native English speaker. > I haven't time to read all messages on this thread My conclusion is, we have false arguments , that Xorg is old, that is not maintained, that will give more work , even we got some lies on some arguments and when we disassemble these arguments, they came up with new ones, now is the tone . I know would be very fancy only have wayland , modern etc etc . But the true is they have the work of remove X11 and not the opposite. Other thought it is obvious that KDE 6 will be a disaster, I remember Kevin step up from leader of KDE SIG, after move from KDE 3 for 4 or 4 for 5 because the work was too much and we need have a life. And the problem here is, we haven't an agreement , since the first day of proposal many people said that was not acceptable and there opinions were ignored and the proposal haven't changed one bit. I think, I and Kevin so be added to the KDE SIG , please add me at least (here is the request) . I think is stupid and a waste of energy, IMO, do a kwin-x11 and plasma -x11 , like I said KDE SIG had the work of remove X11 from the builds, to enable kwin-x11 on Fedora Rawhide is just set %bcond to 1 on kwin.spec [1] and plasma-workspace.spec [2], so I think that should be enable. Another way is build the entire package with X11 and conflict with the original because will give us less work and we will have less doubts or user use packages from KDE SIG or user use packages from KDE-X11 SIG and can't use both. Like happens with ffmpeg where also Neal haven't reach to an agreement with members of RPMFusion , so now we have ffmpeg from RPMFUSion with one freeworld sub-package and we have fffmpeg-free from Fedora and ffmpeg(s) conflicts each other . It never happened to me such thing , except recently and all cases with Neal directly involved, so I see Neal as the problem, was ImageMagick , was ffmpeg, was LSB , now KDE and one honest advice for Neal who appears everywhere, try to do fewer things but be more focused [1] https://src.fedoraproject.org/rpms/kwin/blob/rawhide/f/kwin.spec#_2 [2] https://src.fedoraproject.org/rpms/plasma-workspace/blob/rawhide/f/plasma-workspace.spec#_2 > I can, though, speak for myself, and I am frankly surprised that you > are > offended by the tone of my messages. Are you sure that it is not the > content > that upsets you rather than the tone? And if it is, try asking you > why the > content upsets you. Maybe because it points out inconvenient facts? > > > Neither of you are aligning with the Fedora Foundation of Friends, > > and > > the personal attacks were unwarranted and unwanted. > > We (the KDE SIG and me) stopped being Friends when you (the KDE SIG) > unilaterally decided to ban me from all your communication channels, > a ban > that has still not been lifted years after the alleged misconduct (on > IRC > only, but the ban was extended to the mailing list and even your > Pagure > issue trackers!) you accused me of. > > Nevertheless, I am really trying hard to not make this personal. What > I > disagree with is the technical decision to remove X11 support from > the > Fedora Plasma packaging. I also objected right when you filed your > Change > Proposal that the KDE SIG has no authority to declare in the Change > that > Fedora will NOT ship something because other packagers are free to > package > it. A belief that at the time was actually shared by the KDE SIG, or > at > least by the one KDE SIG member who has publicly commented on it: > https://discussion.fedoraproject.org/t/f40-change-proposal-kde-plasma-6-system-wide/89794/11 > Though the wording in the Change Proposal was not changed. Possibly > because > you did not believe at the time that I was serious about submitting > those > packages, just like others did not believe you were serious about > removing > X11 support from Plasma packaging. But I am of the kind that when I > promise > something, I tend to deliver on it. > > > What we're doing is bold for sure, but aligns with two more of the > > Fedora > > Foundations, First and Features. > > I can see how it aligns with "First", but how does removing a major > feature > that users rely on align with "Features"? > > I also believe that denying users the choice of continuing to use X11 > despite upstream still supporting it does not align with the > "Freedom" and > "Friends" principles. > > > And for the first time in a long time, Fedora KD
Introduction
Hi, I'm a long time Fedora user and used to help develop the Ralink Wireless driver (rt2x00) that's been present in the kernel for a long time. I'm now entering the process of helping maintain the mixxx package over at rpmfusion. Hope to be useful with this new venture. Luis Correia -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
Kevin Kofler via devel wrote: > Steve Cossette wrote: >> There's also a secondary thing that I feel hasn't been discussed here >> though: I know work is being done right now to isolate the x11 >> components of plasma and add build-time options to strip out those >> components. What happens when we (as-in, the KDE sig) split off those >> components and now you got 10-15+ x11 packages people gotta install to >> make it all work? > > Then we will submit 10-15+ *-x11 packages for review. It can be done. PPS: I am fairly sure that, if such a state is ever reached, the KDE SIG will no longer be willing to maintain the kde6-x11-unsupported Copr. (Among other things, your statement quoted above pretty clearly implies that.) So that relativates the claim that my packages are unnecessary because people can just use that Copr. Kevin Kofler -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
> I'm fairly certain you should be > saying this to Kevin. I'm fairly certain it applies to everyone involved. -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
You were implying that Kevin was claiming to be an "unbiased observer" and that him being banned from the KDE SIG means he has ulterior motives for this beyond simply maintaining Plasma X11 packages. Call it what you want, but it doesn't make for a constructive discussion. -- ___ 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
[Package Review] MaterialX
Hello team, materialx package, needed for Blender, is ready for review. Currently, python support is disabled for the time being as unsure where to fix the path. As pointed out, upstream failed to adhere to FHS standard so heavy use of sed -i is needed so patch may be needed to submit to upstream. Here is: https://bugzilla.redhat.com/show_bug.cgi?id=2262694 Spec URL:https://download.copr.fedorainfracloud.org/results/@designsuite/blender/fedora-39-x86_64/06967755-materialx/materialx.spec SRPM URL:https://download.copr.fedorainfracloud.org/results/@designsuite/blender/fedora-39-x86_64/06967755-materialx/materialx-1.38.8-1.fc39.src.rpm Thanks in advance. -- 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
PS: Kevin Kofler via devel wrote: > The atmosphere on #fedora-kde IRC radically changed on 2020-07-13. I also think that that date was not a coincidence, because shortly after that date, the KDE SIG went through with such changes as: * Wayland by default for Plasma, * a push for KDE applications as Fedora Flatpaks, * creation of Kinoite, * systemd user sessions by default, etc., which would have been met by criticism and opposition from me and others. The moderation crackdown was successful at silencing that criticism. Kevin Kofler -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On 2/4/24 14:16, Tom Seewald wrote: On February 3, 2024 8:55:42 PM CST, Kevin Kofler via devel Jumping to an accusation of bad faith, rather than addressing anything that Kevin wrote, doesn't make for a productive discussion. I'm fairly certain you should be saying this to Kevin. -- ___ devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
Jonathan Bennett via devel wrote: > the KDE SIG doesn't have a track record of handing those kind of bans out > flippantly. That is what they want you to believe. Sure, this used to be the case, a few years ago. The atmosphere on #fedora-kde IRC radically changed on 2020-07-13. Until then, it was possible on that chan(nel) to discuss things only partially on topic, such as packaging issues with packages in Fedora that may affect KDE Plasma users but are not part of the KDE SIG's offering, hardware makers' support or non-support of GNU/Linux, etc. On that day (at least in the few hours before I was kicked out of the chan), suddenly, everyone (not just me!) attempting to discuss something like this was immediately greeted with an "off-topic warning". But what the KDE SIG resents the most is criticism. You can see that in this thread, too. So what happened is that they took offense at the *tone* of the criticism (something they are attempting here too: Neal Gompa wrote: > Frankly, I'm disappointed in your response as well as the tone of you > [= Sérgio] and Kevin. ) because that is a much more socially acceptable way to silence criticism than to do it based on its content. What they ended up holding against me was my puns that "name-called" companies and software projects, such as "NoVideo" instead of "NVidia" and some admittedly more vulgar ones. It shall be noted that I tried really hard to not "name-call" people that way, only companies or projects like Firefox. This was claimed to be a violation of the Fedora Code of Conduct even though that was at that time not stated anywhere in the letter of the CoC: https://web.archive.org/web/20200803212051/https://docs.fedoraproject.org/en-US/project/code-of-conduct/ (The current Fedora CoC is much longer: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ and now also bans, among many other things, "personal campaigns against other organizations or individuals", explicitly covering "organizations". That wording did not exist in 2020.) So what happened on that day is that the KDE SIG instantly decided to ban me along with the general moderation crackdown, without even giving me a chance to adapt to the new strict moderation. (They only gave me the "choice" to leave "voluntarily", which I obviously refused.) They claimed that those had always been the rules (which was clearly not the case, the moderation before and on/after 2020-07-13 was completely different) and that I had been warned often enough (but those "warnings" never drew any sanctions with them before 2020-07-13, neither for me nor for anybody else who was "warned"). And when I tried to appeal the unfair ban to the Fedora Council, the KDE SIG demanded "Acknowledgement that your past behaviour was unacceptable" as a precondition to be unbanned, which I consider particularly unfair and unacceptable because it demands that I plead guilty to a wrongdoing that I do not agree having ever committed. The Council also marked the ticket private against my wishes in an effort to prevent the public from reading about the unfair banning practices in parts of Fedora. So now, 3½ years later, I am still banned, because the KDE SIG is unwilling to give its old grudges of the distant past an expiry date. Kevin Kofler -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On February 4, 2024 2:16:55 PM CST, Tom Seewald wrote: >> On February 3, 2024 8:55:42 PM CST, Kevin Kofler via devel >> > >> Wait, you're banned from all the KDE channels in Fedora? I have no idea what >> led to >> that, though the KDE SIG doesn't have a track record of handing those kind >> of bans out >> flippantly. But regardless, that calls into question your position as an >> unbiased >> observer. > >Jumping to an accusation of bad faith, rather than addressing anything that >Kevin wrote, doesn't make for a productive discussion. No. I explicitly did not accuse him of bad faith. I am pointing out that being banned from the Fedora KDE effort puts him in a weird place, to now try to save the day. It's a conflict of interest. >-- >___ >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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
> On February 3, 2024 8:55:42 PM CST, Kevin Kofler via devel > > Wait, you're banned from all the KDE channels in Fedora? I have no idea what > led to > that, though the KDE SIG doesn't have a track record of handing those kind of > bans out > flippantly. But regardless, that calls into question your position as an > unbiased > observer. Jumping to an accusation of bad faith, rather than addressing anything that Kevin wrote, doesn't make for a productive discussion. -- ___ 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
[heads up] mass rebuild for opencv 4.9.0 with soname bump on rawhide
Hi, I will start a mass rebuild in a side-tag, very soon , the goal is finish and merge it before branch of Fedora 40, please let me know we have any thing that prevent to proceeding. Best regards, -- 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
Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
On February 3, 2024 8:55:42 PM CST, Kevin Kofler via devel wrote: >Neal Gompa wrote: >> It's extremely obvious that people want to use it. You replied to >> someone who did and denigrated their opinion. Frankly, I'm >> disappointed in your response as well as the tone of you and Kevin. > >I cannot really speak for Sérgio. I do think his choice of words in the >particular mail you are referring to could have been better. (In particular, >I would not have used the word "crap" there.) But please keep in mind that >he (like me) is not a native English speaker. > >I can, though, speak for myself, and I am frankly surprised that you are >offended by the tone of my messages. Are you sure that it is not the content >that upsets you rather than the tone? And if it is, try asking you why the >content upsets you. Maybe because it points out inconvenient facts? > >> Neither of you are aligning with the Fedora Foundation of Friends, and >> the personal attacks were unwarranted and unwanted. > >We (the KDE SIG and me) stopped being Friends when you (the KDE SIG) >unilaterally decided to ban me from all your communication channels, a ban >that has still not been lifted years after the alleged misconduct (on IRC >only, but the ban was extended to the mailing list and even your Pagure >issue trackers!) you accused me of. Wait, you're banned from all the KDE channels in Fedora? I have no idea what led to that, though the KDE SIG doesn't have a track record of handing those kind of bans out flippantly. But regardless, that calls into question your position as an unbiased observer. > >Nevertheless, I am really trying hard to not make this personal. What I >disagree with is the technical decision to remove X11 support from the >Fedora Plasma packaging. I also objected right when you filed your Change >Proposal that the KDE SIG has no authority to declare in the Change that >Fedora will NOT ship something because other packagers are free to package >it. A belief that at the time was actually shared by the KDE SIG, or at >least by the one KDE SIG member who has publicly commented on it: >https://discussion.fedoraproject.org/t/f40-change-proposal-kde-plasma-6-system-wide/89794/11 >Though the wording in the Change Proposal was not changed. Possibly because >you did not believe at the time that I was serious about submitting those >packages, just like others did not believe you were serious about removing >X11 support from Plasma packaging. But I am of the kind that when I promise >something, I tend to deliver on it. > >> What we're doing is bold for sure, but aligns with two more of the Fedora >> Foundations, First and Features. > >I can see how it aligns with "First", but how does removing a major feature >that users rely on align with "Features"? > >I also believe that denying users the choice of continuing to use X11 >despite upstream still supporting it does not align with the "Freedom" and >"Friends" principles. > >> And for the first time in a long time, Fedora KDE has generated >> significant buzz in the community and media. > >Any press is good press? I believe that the coverage only hurts the >reputation of the Fedora KDE SIG. If you see the discussions, many people >are grabbing their virtual pitchforks, or silently switching distributions >as a result of the news (even though it is actually fake news because I had >already stated back in September that I would reintroduce the X11 packages >should you remove them, a fact that the press has not bothered researching). >Sure, there are some very vocal fanboys screaming "Death to X11!", but I >really do not understand why, because nobody is forcing them to use X11. >There is no need to remove X11 to make Wayland great. > >> I'm excited for the future of Fedora KDE with Plasma Wayland, as well >> as what we're doing with the upstream KDE community. :) > >And nobody is taking that away. > >Kevin Kofler >-- >___ >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: Figure out what killed an app (rhbz#2253099)
On Sat, 2024-02-03 at 13:29 +0100, Ondrej Mosnáček wrote: > On Fri, 2 Feb 2024 at 17:52, Yanko Kaneti wrote: > > > > On Thu, 2024-02-01 at 09:44 +0100, Ondrej Mosnáček wrote: > > > On Thu, 1 Feb 2024 at 09:13, Milan Crha wrote: > > > > The kernel tracing log for sig==9 shows: > > > > > > > > gnome-terminal--2924[002] dN.2. 2520.462889: signal_generate: > > > > sig=9 errno=0 code=128 comm=alloc-too-much pid=3502 grp=1 res=0 > > > > > > > > There is no such thing (apart of the tracing log) when Evolution is > > > > suddenly killed, the logs are muted. That makes me believe it's not the > > > > OOM killer whom kills the application. I'm back at square 1; or maybe > > > > square 2, as I know possibly kernel sends it, but not why. > > > > > > Try running `echo stacktrace >/sys/kernel/tracing/trace_options` (as > > > root) and then collect the kernel trace again. That should give you a > > > backtrace of kernel functions from the signal generation, which could > > > help you/us to figure out the reason the process was killed. > > > > So, figured the easiest way to help trigger the kill here is to put load > > on the machine. > > > > $ stress-ng --cpu -1 --cpu-method all -t 5m --cpu-load 95 > > > > then starting evolution seems to do it almost every time shortly after > > start (I have around 200k messages in the folder its trying to display) > > > > I've enabled the stacktrace tracing option and like Milan set a sig==9 > > filter. And here is what I got in the trace buffer after it was killed > > > > # tracer: nop > > # > > # entries-in-buffer/entries-written: 34/34 #P:16 > > # > > #_-=> irqs-off/BH-disabled > > # / _=> need-resched > > # | / _---=> hardirq/softirq > > # || / _--=> preempt-depth > > # ||| / _-=> migrate-disable > > # / delay > > # TASK-PID CPU# | TIMESTAMP FUNCTION > > # | | | | | | > >evolution-9096[002] d..1. 1207.016489: signal_generate: sig=9 > > errno=0 code=128 comm=evolution pid=9096 grp=1 res=0 > >evolution-9096[002] d..1. 1207.016495: > > => trace_event_raw_event_signal_generate > > => __send_signal_locked > > => posix_cpu_timers_work > > => task_work_run > > => irqentry_exit_to_user_mode > > => asm_sysvec_apic_timer_interrupt > > So, browsing through the relevant kernel code, it seems the only cases > which could have led to this backtrace are: > 1. When a task's RT timeout goes over the RLIMIT_RTTIME hard limit > (see function check_thread_timers() in > kernel/time/posix-cpu-timers.c). > 2. When a task's CPU time goes over the RLIMIT_CPU hard limit (see > function check_process_timers() in kernel/time/posix-cpu-timers.c). > > I may have missed some code path, but these resource limits should be > the next thing to check. Thanks a lot for diving it. This is probably it. The kernel killing the main evolution process which was set as having rt priority by some webkit coincidence. Running with rtkit-daemon stoped and masked prevents the main evo process being prioritized and consequently killed with higher load. The fact that the kernel kills the (main)thread without a beep anywhere in the logs is strange to me. - Yanko -- ___ 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
License change for perl-Net-DHCP
Hello, all. The license tag on perl-Net-DHCP has been corrected from: GPL+ or Artistic to MIT Regards, Emmanuel -- ___ 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: just to let you know FESCo agreed to a preliminary injunction while we consider this issue
Kevin Kofler wrote: > > Any press is good press? I believe that the coverage only hurts the > reputation of the Fedora KDE SIG. If you see the discussions, many people > are grabbing their virtual pitchforks, or silently switching distributions > as a result of the news (even though it is actually fake news because I had > already stated back in September that I would reintroduce the X11 packages > should you remove them, a fact that the press has not bothered > researching). Sure, there are some very vocal fanboys screaming "Death to > X11!", but I really do not understand why, because nobody is forcing them > to use X11. There is no need to remove X11 to make Wayland great. > F39 is the only release that with Wayland the desktop haven't soft locked and turned gray seconds after login, so thats a huge improvement. I never been able to even test Wayland before F39. Lets try something basic like opening Kmail and read mails https://imgur.com/a/ZHYNqjq Maybe this “just works” in plasma6, but if it don’t and there is no easy way to change to X11, obviously people will choose the path of least resistance. I don’t even think people will know its because of Wayland and blame it on KDE instead. -- ___ 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
