Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Hey folks, outside observer, and long-time Fedora user weighing in with some thoughts. First off, I've been hyped to see Fedora lead the way with finally making a real move to Wayland, and retire X11. And now I'm fairly disappointed to hear that there's a real chance that move will get killed.

Re: Failure on fedora default backgrounds

On Fri, Feb 2, 2024 at 2:04 AM Mamoru TASAKA wrote: > > Luya Tshimbalanga wrote on 2024/02/02 10:25: > > Hello team, > > > > It appears a change within %{_kde4_datadir} macro caused failures on > > Rawhide affecting default Fedora backgrounds starting from 21. > > Could someone from KDE SIG

[Bug 2262363] New: perl-DateTime-TimeZone-2.62 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2262363 Bug ID: 2262363 Summary: perl-DateTime-TimeZone-2.62 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DateTime-TimeZone Keywords: FutureFeature,

[EPEL-devel] Fedora EPEL 8 updates-testing report

The following Fedora EPEL 8 Security updates need testing: Age URL 29 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-3a29f0d349 python-paramiko-2.12.0-2.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-11fae9c7fb python-aiohttp-3.7.4-2.el8 The following

[EPEL-devel] Fedora EPEL 7 updates-testing report

The following Fedora EPEL 7 Security updates need testing: Age URL 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-54270ec4b3 clojure-1.8.0-2.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing baresip-3.9.0-1.el7 libre-3.9.0-1.el7

Re: [Test-Announce] Kernel 6.7 Test Week is underway!

On Thu, Feb 1, 2024 at 5:49 PM Leigh Scott wrote: > > > Thanks for holding the push to testing, I have managed to patch nvidia > > 545.xx and > > 550.xx so > 470.xx is also patched. > > I think it is ok to push the new kernel to testing, the legacy nvidia drivers > shouldn't hold up the new

Re: Failure on fedora default backgrounds

Luya Tshimbalanga wrote on 2024/02/02 10:25: Hello team, It appears a change within %{_kde4_datadir} macro caused failures on Rawhide affecting default Fedora backgrounds starting from 21. Could someone from KDE SIG address that issue? Thanks. Here is an extract of failure[1]  on for

Re: Failure on fedora default backgrounds

I'm the maintainer of those packages and I've already spoken with Neal Gompa about it. I'll be addressing that when I get home, I'm on the road until Sunday without my system to be able to commit to fix it. JT On Thu, Feb 1, 2024 at 8:26 PM Luya Tshimbalanga wrote: > Hello team, > > It appears

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Roberto Ragusa wrote: > On 2/1/24 14:29, Steve Cossette wrote: > >> And yes, that /is/ the whole point: We want to foster the use of Wayland, >> to increase it's adoption, to force people using it to hit snags along >> the road and fill tickets so those issues can be fixed. > "force people" "hit

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Steve Cossette wrote: > But I feel like I'm going off subject. I also think you are right, the KDE > COPR-solution would work as long as it is documented somewhere. We could > simply put it in the Fedora docs page, but also clearly note that those > packages are not supported, but will be updated

Failure on fedora default backgrounds

Hello team, It appears a change within %{_kde4_datadir} macro caused failures on Rawhide affecting default Fedora backgrounds starting from 21. Could someone from KDE SIG address that issue? Thanks. Here is an extract of failure[1]  on for f35-backgrounds built on Rawhide: RPM build

[Bug 2259686] perl-LWP-Protocol-https-6.12 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2259686 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|

[Bug 2258649] perl-SQL-Translator-1.65 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2258649 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-SQL-Translator-1.65-1. |perl-SQL-Translator-1.65-1.

Re: Self Introduction: Leo Sandoval

Welcome to Fedora! Drop by matrix, we don't bite (hard)! Le jeu. 1 févr. 2024, à 19 h 48, Leo Sandoval a écrit : > Dear Fedora Community! > > My name is Leonardo Sandoval, a software developer living in Guadalajara, > Mexico. I have been in the industry since 2006, most of the time close to >

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Steve Cossette wrote: > It would also introduce a precedent: What if later a proposal is made to > remove some old drivers from, let's say, the kernel, and someone decides > to package it, undermining the general efforts of that proposal? The kernel is actually a special case in that there is a

Re: [Test-Announce] Kernel 6.7 Test Week is underway!

On 2/2/24 10:48, Leigh Scott wrote: Thanks for holding the push to testing, I have managed to patch nvidia 545.xx and 550.xx so 470.xx is also patched. I think it is ok to push the new kernel to testing, the legacy nvidia drivers shouldn't hold up the new kernel. Thank you for doing this

Re: Self Introduction: Leo Sandoval

On Fri, Feb 2, 2024 at 12:48 AM Leo Sandoval wrote: > > Dear Fedora Community! > > My name is Leonardo Sandoval, a software developer living in Guadalajara, > Mexico. I have been in the industry since 2006, most of the time close to the > Linux kernel (openmax, gstreamer, glibc, yocto project,

suitesparse update/soname bump coming this weekend

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

Self Introduction: Leo Sandoval

Dear Fedora Community! My name is Leonardo Sandoval, a software developer living in Guadalajara, Mexico. I have been in the industry since 2006, most of the time close to the Linux kernel (openmax, gstreamer, glibc, yocto project, ltib, toolchains) and recently doing gitlab CI/CD, but all the

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Mattia Verga via devel wrote: > However, if the breakage could happen only one way, e.g. a KDE Plasma > update will possibly break -x11 packages, but no -x11 package could > break the "official" Wayland implementation, I'm for allowing the -x11 > packages in the main repos. I see no other reason

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Neal Gompa wrote: > My position as the KDE SIG lead based on discussions within the SIG is > that re-introducing these packages in the main distribution would > destroy the main point of our efforts: driving KDE Plasma Wayland to > be the best and most complete experience. The signal of dropping >

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Steven A. Falco wrote: > Bug 2239016 - Plasma(Wayland) does not honor window positioning when > setting window geometry > For 2239016 the response was "That's just how wayland works" As far as I know, there are actually some discussions about this issue in the upstream Wayland community, but

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Daniel P. Berrangé wrote: > The approved KDE change > https://fedoraproject.org/wiki/Changes/KDE_Plasma_6 indicates the intent > for existing Plasma X11 installs to switch to Wayland during the upgrade > process. > > There's no perfect answer as some users will be happy to switch to > Wayland,

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Alessandro Astone wrote: > Also "major changes" would be the ~fibonacci-weekly~ Plasma bugfix > release, as the -x11 package will require an exact version match of the > common libraries. Not really a rare occasion. -- This can be solved with communication. That said, if the KDE SIG does not

Re: [Test-Announce] Kernel 6.7 Test Week is underway!

> Thanks for holding the push to testing, I have managed to patch nvidia 545.xx > and > 550.xx so 470.xx is also patched. I think it is ok to push the new kernel to testing, the legacy nvidia drivers shouldn't hold up the new kernel. -- ___ devel

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Alessandro Astone wrote: > But am I supposed to ignore the fact that kkofler is already bullying the > KDE SIG into not breaking that one other package they maintain that > occasionally breaks on kde updates? See example: > https://bodhi.fedoraproject.org/updates/FEDORA-2023-977de87584 To make it

Re: [Test-Announce] Kernel 6.7 Test Week is underway!

> On Thu, Feb 1, 2024 at 1:45 AM Leigh Scott wrote: > > This is not accurate. The 6.7.3 (and 6.6.15) updates did break the > nvidia driver. It has nothing to do with debugging being enabled. A > proper and valid bugfix: > > 5ec8e8ea8b7783fab150cf86404fc38cb4db8800 mm/sparsemem: fix race in >

Re: Looking for a new maintainer for ode

Hi Gwyn, On 2/1/24 17:08, Gwyn Ciesla via devel wrote: > Hi! I'd be happy to take ode, Xaw3d, and libcddb. Great, thank you. I have handed over ownership of all three packages to you now. > Thank you for everything over the years. :) You're welcome. Regards, Hans > On Tuesday, January

Re: Package review ticket status change after approval

On Mon, Jan 29, 2024 at 7:47 PM Mattia Verga via devel wrote: > (snip) > > That said, I'd like to make a request and maybe make all reviewers aware > of a feature which was implemented some time ago. I've noticed many > reviewers change the ticket status from ASSIGNED to POST when they flag >

[Bug 2262294] perltidy-20240202 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2262294 Fedora Update System changed: What|Removed |Added Status|MODIFIED|CLOSED Resolution|---

[Bug 2262294] perltidy-20240202 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2262294 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #3 from

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2024-02-01 07:40, Sérgio Basto wrote: 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 In fact, it is something I've been thinking about, IMHO, downstream shouldn't

Re: Mounting USB Storage devices with "sync" option ?

On Wed, Jan 31, 2024 at 6:36 AM Leon Fauster via devel wrote: > > Am 31.01.24 um 09:57 schrieb Larina Loriasel via devel: > >> 'sync' has some strong downsides though: various operations become > >> painfully slow (this depends a lot on the hardware and its age, and > >> the history of previous

SQLAlchemy major version upgrade

Hi everybody, just a heads up: with the compat package for version 1.4 in place[1], I’m about to upgrade the main python-sqlalchemy package to version 2 in Rawhide. This is part of the SQLAlchemy 2 Change for Fedora 40[2] and when the upgraded package is available, we can verify whether or not

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2024-02-01 04:08, Steve Cossette wrote: So, if you all don't mind, I'd like to steer this discussion in a slightly different way: What /is/ the definition of a Fedora Change Proposal? I was under the impression it was an announcement of intent by the maintainers of a specific subset of

Re: Re: Re: A reminder: you cannot just "revert" package version bumps

On Thu, Feb 01, 2024 at 02:51:54AM +0100, Kevin Kofler via devel wrote: > kevin wrote: > > distro-sync is nice and all, but it's not a silver bullet. > > In cases of simple packages a downgrade may not break anything, but in > > cases where other things already built upon it, where the new one > >

Re: Mounting USB Storage devices with "sync" option ?

Such a way to dynamically mount and perform reads/writes to the device only when needed is truly an ideal solution, looking forward to udisks implementing such a feature. -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

Re: CI failure: Too many packages to install: 233 (threshold 100). Please use 'repository-file' artifact instead.

On 2/1/24 12:35 AM, Florian Weimer wrote: > How can we fix this error? > > > > > I think it's related to the fact that glibc has many subpackages. This > used to be a problem with slow tests timing out in Zuul, but

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Am 01.02.24 um 17:44 schrieb Neal Gompa: That is not necessarily true. For your example about window placement, there is this:https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264 Am 01.02.24 um 17:46 schrieb Neal Gompa: Sorry, I meant to point to this as well:

Re: [Test-Announce] Kernel 6.7 Test Week is underway!

On Thu, Feb 1, 2024 at 1:45 AM Leigh Scott wrote: > > Kernel-6.7.3 still has debugging enabled which will break the nvidia driver This is not accurate. The 6.7.3 (and 6.6.15) updates did break the nvidia driver. It has nothing to do with debugging being enabled. A proper and valid bugfix:

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2/1/24 11:46 AM, Neal Gompa wrote: I'd like to think that the gaps will be fixed, but it seems to me that because of policy, some gaps (like apps controlling their own window placement) will never be fixed. That is not necessarily true. For your example about window placement, there is

[Bug 2261449] perl-Prima-1.71-3.fc40: FTBFS in F40: img/codec_Xpm.c:635:28: error: assignment to ‘Bool (*)(struct ImgCodec *, struct _ImgLoadFileInstance *)’ {aka ‘long int (*)(struct ImgCodec *, stru

https://bugzilla.redhat.com/show_bug.cgi?id=2261449 Petr Pisar changed: What|Removed |Added Link ID||CPAN 151523 -- You are receiving this

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On Thu, Feb 1, 2024 at 4:44 PM Neal Gompa wrote: > > On Thu, Feb 1, 2024 at 4:40 PM Steven A. Falco wrote: > > > > On 2/1/24 11:28 AM, Neal Gompa wrote: > > > On Thu, Feb 1, 2024 at 4:21 PM Roberto Ragusa > > > wrote: > > >> > > >> On 2/1/24 14:29, Steve Cossette wrote: > > >> > > >>> And yes,

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On Thu, Feb 1, 2024 at 4:40 PM Steven A. Falco wrote: > > On 2/1/24 11:28 AM, Neal Gompa wrote: > > On Thu, Feb 1, 2024 at 4:21 PM Roberto Ragusa wrote: > >> > >> On 2/1/24 14:29, Steve Cossette wrote: > >> > >>> And yes, that /is/ the whole point: We want to foster the use of Wayland, > >>> to

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2/1/24 11:28 AM, Neal Gompa wrote: On Thu, Feb 1, 2024 at 4:21 PM Roberto Ragusa wrote: On 2/1/24 14:29, Steve Cossette wrote: And yes, that /is/ the whole point: We want to foster the use of Wayland, to increase it's adoption, to force people using it to hit snags along the road and

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On Thu, Feb 1, 2024 at 4:21 PM Roberto Ragusa wrote: > > On 2/1/24 14:29, Steve Cossette wrote: > > > And yes, that /is/ the whole point: We want to foster the use of Wayland, > > to increase it's adoption, to force people using it to hit snags along the > > road and fill tickets so those

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2024-02-01 11:21 a.m., Roberto Ragusa wrote: On 2/1/24 14:29, Steve Cossette wrote: And yes, that /is/ the whole point: We want to foster the use of Wayland, to increase it's adoption, to force people using it to hit snags along the road and fill tickets so those issues can be fixed.

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2/1/24 14:29, Steve Cossette wrote: And yes, that /is/ the whole point: We want to foster the use of Wayland, to increase it's adoption, to force people using it to hit snags along the road and fill tickets so those issues can be fixed. "force people" "hit snag" With this kind of

[rpms/perl-Term-Cap] PR #1: Package tests

jplesnik merged a pull-request against the project: `perl-Term-Cap` that you are following. Merged pull-request: `` Package tests `` https://src.fedoraproject.org/rpms/perl-Term-Cap/pull-request/1 -- ___ perl-devel mailing list --

Re: Looking for a new maintainer for ode

Hi! I'd be happy to take ode, Xaw3d, and libcddb. Thank you for everything over the years. :) --  Gwyn Ciesla she/her/hers   in your fear, seek only peace  in your fear, seek only love -d. bowie Sent with Proton Mail secure email. On Tuesday,

[Bug 2262294] perltidy-20240202 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2262294 --- Comment #2 from Upstream Release Monitoring --- the-new-hotness/release-monitoring.org's scratch build of perltidy-20240202-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=112741397 -- You are

[rpms/perl-Term-Cap] PR #1: Package tests

jplesnik opened a new pull-request against the project: `perl-Term-Cap` that you are following: `` Package tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Term-Cap/pull-request/1 -- ___ perl-devel mailing list --

[Bug 2262294] perltidy-20240202 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2262294 --- Comment #1 from Upstream Release Monitoring --- Created attachment 2014404 --> https://bugzilla.redhat.com/attachment.cgi?id=2014404=edit Update to 20240202 (#2262294) -- You are receiving this mail because: You are on the CC list

[Bug 2262294] New: perltidy-20240202 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2262294 Bug ID: 2262294 Summary: perltidy-20240202 is available Product: Fedora Version: rawhide Status: NEW Component: perltidy Keywords: FutureFeature, Triaged

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2024-02-01 10:27 a.m., Peter Boy wrote: Sorry, a bit off-topic here, but nevertheless: Am 01.02.2024 um 15:14 schrieb Steve Cossette : Hello Pgnd, I honestly do appreciate your point of view. Especially from a business owner standpoint. I do manage small business servers, and I feel

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2024-01-30 8:04 a.m., Germano Massullo wrote: What does it mean that FESCo is applying an injunction? -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Sorry, a bit off-topic here, but nevertheless: > Am 01.02.2024 um 15:14 schrieb Steve Cossette : > > Hello Pgnd, > > I honestly do appreciate your point of view. Especially from a business owner > standpoint. I do manage small business servers, and I feel you in that regard. > > I do have to

Re: Orphaned python-mccabe (dependency of pylint)

Excellent, thank you both! --  Gwyn Ciesla she/her/hers   in your fear, seek only peace  in your fear, seek only love -d. bowie Sent with Proton Mail secure email. On Thursday, February 1st, 2024 at 2:52 AM, Michel Lind wrote: > On Thu,

[Bug 2261449] perl-Prima-1.71-3.fc40: FTBFS in F40: img/codec_Xpm.c:635:28: error: assignment to ‘Bool (*)(struct ImgCodec *, struct _ImgLoadFileInstance *)’ {aka ‘long int (*)(struct ImgCodec *, stru

https://bugzilla.redhat.com/show_bug.cgi?id=2261449 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED Hardware|Unspecified

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

* Richard W. M. Jones: >> We will have to fix this again (and wrap-find-debuginfo.sh and as well) >> once Fedora adopts the standard RISC-V paths. > > Shouldn't we adopt the normal Fedora paths instead? No, we should use the official RISC-V paths because we might need them if we want to adopt

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

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.

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

On Thu, Feb 1, 2024 at 4:10 PM David Abdurachmanov wrote: > > On Thu, Feb 1, 2024 at 3:44 PM Richard W.M. Jones wrote: > > > > On Thu, Feb 01, 2024 at 02:24:10PM +0100, Florian Weimer wrote: > > > * David Abdurachmanov: > > > > > > > Hi Florian, > > > > > > > > I was trying to build the latest

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

On Thu, Feb 1, 2024 at 3:44 PM Richard W.M. Jones wrote: > > On Thu, Feb 01, 2024 at 02:24:10PM +0100, Florian Weimer wrote: > > * David Abdurachmanov: > > > > > Hi Florian, > > > > > > I was trying to build the latest glibc [0] in Fedora 40 for riscv64, > > > but it failed. It seems to be

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

On Thu, Feb 01, 2024 at 02:24:10PM +0100, Florian Weimer wrote: > * David Abdurachmanov: > > > Hi Florian, > > > > I was trying to build the latest glibc [0] in Fedora 40 for riscv64, > > but it failed. It seems to be related to your last commit. > > > > [..] > > + ln -s libBrokenLocale.so.1

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On 2024-02-01 8:18 a.m., Sérgio Basto wrote: On Thu, 2024-02-01 at 07:08 -0500, Steve Cossette wrote: So, if you all don't mind, I'd like to steer this discussion in a slightly different way: What is the definition of a Fedora Change Proposal? Proposal was not accepted by many members of the

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

* David Abdurachmanov: > Hi Florian, > > I was trying to build the latest glibc [0] in Fedora 40 for riscv64, > but it failed. It seems to be related to your last commit. > > [..] > + ln -s libBrokenLocale.so.1 usr/lib64/libBrokenLocale.so > + for sl in `find $RPM_BUILD_ROOT/$pfx$lib -maxdepth 1

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On Thu, 2024-02-01 at 07:08 -0500, Steve Cossette wrote: > So, if you all don't mind, I'd like to steer this discussion in a > slightly different way:  > > What is the definition of a Fedora Change Proposal? Proposal was not accepted by many members of the community try accept that . > I was

[rpms/perl-TermReadKey] PR #2: Package tests

jplesnik merged a pull-request against the project: `perl-TermReadKey` that you are following. Merged pull-request: `` Package tests `` https://src.fedoraproject.org/rpms/perl-TermReadKey/pull-request/2 -- ___ perl-devel mailing list --

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Another option is to allow the x11-compatible packages but as a clearly forked desktop with a clearly different name On Thu, 1 Feb 2024, 12:10 Steve Cossette, wrote: > So, if you all don't mind, I'd like to steer this discussion in a slightly > different way: > > What *is* the definition of a

[rpms/perl-TermReadKey] PR #2: Package tests

jplesnik opened a new pull-request against the project: `perl-TermReadKey` that you are following: `` Package tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-TermReadKey/pull-request/2 -- ___ perl-devel mailing list --

Re: "noarch sysroot subpackages" commit breaks glibc compile on riscv64

[Adding Fedora devel] On Thu, Feb 01, 2024 at 02:29:41PM +0200, David Abdurachmanov wrote: > Hi Florian, > > I was trying to build the latest glibc [0] in Fedora 40 for riscv64, > but it failed. It seems to be related to your last commit. > > [..] > + ln -s libBrokenLocale.so.1

[rpms/perl-threads] PR #2: Package tests

jplesnik merged a pull-request against the project: `perl-threads` that you are following. Merged pull-request: `` Package tests `` https://src.fedoraproject.org/rpms/perl-threads/pull-request/2 -- ___ perl-devel mailing list --

[rpms/perl-threads] PR #2: Package tests

jplesnik opened a new pull-request against the project: `perl-threads` that you are following: `` Package tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-threads/pull-request/2 -- ___ perl-devel mailing list --

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

So, if you all don't mind, I'd like to steer this discussion in a slightly different way: What *is* the definition of a Fedora Change Proposal? I was under the impression it was an announcement of intent by the maintainers of a specific subset of the fedora project to "change" something. Once

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

Thank you for clarifying. -- ___ 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

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On Thu, Feb 01, 2024 at 07:51:59AM +, Neal Gompa wrote: [snip] > My position as the KDE SIG lead based on discussions within the SIG is > that re-introducing these packages in the main distribution would > destroy the main point of our efforts: driving KDE Plasma Wayland to > be the best and

Re: Orphaning python-represent

On Wed, Jan 24, 2024 at 05:48:58PM +0100, Lumír Balhar wrote: > Hello. > > I'm going to orphan python-represent. I updated it to the latest version so > if you take it, there is nothing to be done now. It's a leaf package and I > don't have any use for it. > I've taken it, thanks! -- Michel

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On Wed, Jan 31, 2024 at 09:27:52PM -, Alessandro Astone wrote: > I can support that. > > But am I supposed to ignore the fact that kkofler is already bullying the KDE > SIG into not breaking that one other package they maintain that occasionally > breaks on kde updates? See example: >

Re: Orphaned python-mccabe (dependency of pylint)

On Thu, Feb 01, 2024 at 01:03:55AM +0100, Miro Hrončok wrote: > On 01. 02. 24 0:51, Michel Lind wrote: > > I see limb already took the package (thanks limb) - note that the > > default bugzilla assignee still seems to be 'orphan', I'm assuming that > > will fix itself eventually > > Not by

Re: Re: A reminder: you cannot just "revert" package version bumps

On Thu, Feb 1, 2024 at 3:11 AM Kevin Kofler via devel wrote: > > If the distro-sync (which should be the default way to do updates > at least on Rawhide, if not everywhere) mentions a package being downgraded, > that is much more likely to be noticed. > I look forward to your formal change

Re: Mounting USB Storage devices with "sync" option ?

On 1/31/24 07:43, Abyss Ether via devel wrote: I created a simple PoC udev rule to mount USB Storage devices with the "sync option. Available here : https://github.com/larina3315/personal-stuff/blob/main/linux/10-usb-storage.rules Currently, USB Storage devices are mounted without the "sync"

Re: Figure out what killed an app (rhbz#2253099)

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

Re: Figure out what killed an app (rhbz#2253099)

On Wed, 2024-01-31 at 13:40 -0500, Paul Grosu wrote: > 2) Or you can completely disable it: Hi, I do not want to disable the oom service. Remember, it does that on user machines, not only on mine. Telling people: "you want to use app a, b, c, then disable oom" as a new Fedora 40 feature