[Bug 2262599] perl-Tie-Cycle-1.228 is available

2024-02-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2262599 --- Comment #2 from Upstream Release Monitoring --- the-new-hotness/release-monitoring.org's scratch build of perl-Tie-Cycle-1.228-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=112904787 -- You

[Bug 2262599] perl-Tie-Cycle-1.228 is available

2024-02-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2262599 --- Comment #1 from Upstream Release Monitoring --- Created attachment 2014969 --> https://bugzilla.redhat.com/attachment.cgi?id=2014969=edit Update to 1.228 (#2262599) -- You are receiving this mail because: You are on the CC list for

[Bug 2262599] New: perl-Tie-Cycle-1.228 is available

2024-02-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2262599 Bug ID: 2262599 Summary: perl-Tie-Cycle-1.228 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Tie-Cycle Keywords: FutureFeature, Triaged

Re: List of long term FTBFS packages to be retired in February

2024-02-03 Thread Mamoru TASAKA
Miro Hrončok wrote on 2024/02/04 2:17: Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 40 approximately one week before branching. 5 weekly reminders are required, hence the retirement will happen approximately in 4

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

2024-02-03 Thread Kevin Kofler via devel
Kevin Kofler via devel wrote: > Then we will submit 10-15+ *-x11 packages for review. It can be done. PS: Users will only have to install plasma-workspace-x11. If there is some optional library that needs an ld.so.conf.d override or a plugin to support X11, it can be conditionally dragged in

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

2024-02-03 Thread Kevin Kofler via devel
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

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

2024-02-03 Thread Kevin Kofler via devel
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

Re: sd_notify in mock

2024-02-03 Thread Vít Ondruch
Ping? Anybody? Vít Dne 11. 01. 24 v 15:00 Vít Ondruch napsal(a): Working on update of rubygem-puma, I observe following test failure trying build rubygem-rails in Mock: ~~~ /usr/share/ruby/socket.rb:68:in `connect': Errno::EACCES: Permission denied - connect(2) for /run/host/notify

[Bug 2262550] New: perl-Catalyst-Manual-5.9012 is available

2024-02-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2262550 Bug ID: 2262550 Summary: perl-Catalyst-Manual-5.9012 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Catalyst-Manual Keywords: FutureFeature,

Retirement of sundials2 seqan seqan2 wise2

2024-02-03 Thread Antonio T. sagitter
Hi all. Following packages will be retired in Rawhide branch: seqan (deprecated by seqan3), https://src.fedoraproject.org/rpms/seqan seqan2 (deprecated by seqan3), https://src.fedoraproject.org/rpms/seqan2 wise2 (unmaintained by upstream, no longer needed in Fedora),

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

2024-02-03 Thread Dominique Martinet
(Not involved in any way here so feel free to ignore most of what I'm saying) Marc Deop i Argemí wrote on Sat, Feb 03, 2024 at 03:16:47PM +0100: > - If a user decided to install the X11 package and has an issue: who do you > think they are going to reach? who is gonna get the "bad publicity" for

Re: Failure on fedora default backgrounds

2024-02-03 Thread Luya Tshimbalanga
On 2024-02-03 12:12, JT wrote: > Thank you all for the solution. I notice I lack access to commit changes on  f21-backgrounds so proven packagers are welcome to do so. Thanks As I said on Monday when I replied to this ticket, I had talked to Neil about this already, I'm aware of the fix,

Re: Failure on fedora default backgrounds

2024-02-03 Thread JT
> Thank you all for the solution. I notice I lack access to commit changes on f21-backgrounds so proven packagers are welcome to do so. Thanks As I said on Monday when I replied to this ticket, I had talked to Neil about this already, I'm aware of the fix, but as I am on the road and unable to

Re: Failure on fedora default backgrounds

2024-02-03 Thread Luya Tshimbalanga
On 2024-02-03 01:27, Dan Horák wrote: On Fri, 2 Feb 2024 23:55:43 -0800 l...@fedoraproject.org wrote: On 2024-02-01 11:26 p.m., Neal Gompa wrote: 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

[Test-Announce] [Fedora Test Days] KDE Plasma 6 Test Week

2024-02-03 Thread Sumantro Mukherjee
Hey Folks, As many of you may know, FOSDEM is going on but still, we are hosting the KDE test weeks. You can still submit the results here[0]. KDE is very important for our community members and testing this way ahead of time helps us find bugs and eliminate them!! Thanks for testing! [0]

List of long term FTBFS packages to be retired in February

2024-02-03 Thread Miro Hrončok
Dear maintainers. Based on the current fail to build from source policy, the following packages should be retired from Fedora 40 approximately one week before branching. 5 weekly reminders are required, hence the retirement will happen approximately in 4 weeks, i.e. around 2024-02-28. Since

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

2024-02-03 Thread Adam Williamson
On 2024-02-03 06:16, Marc Deop i Argemí wrote: - As the packages stand right now, the KDE general updates will have to wait for the proposed packages to be updated by their maintainers or we will have to do the updates ourselves (which defeats completely the point of our change proposal). Why?

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

2024-02-03 Thread Steven A. Falco
On 2/3/24 01:12 AM, Kevin Kofler via devel wrote: Any interested people can already request comaintainership now (e.g., by replying to this mail), and I will almost certainly grant it (though I will have reservations about some specific types of requests, such as blanket admin permissions for

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

2024-02-03 Thread Marc Deop i Argemí
On Friday, 2 February 2024 20:56:22 CET Gary Buhrmaster wrote: > regarding tracking (and taking) bugs, and > lack of timely updates, for something as > visible as the entire desktop. Here you are highlighting some of my (I speak for me, not the KDE SIG) main concerns: - If a user decided to

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

2024-02-03 Thread Steve Cossette
On 2024-02-03 9:01 a.m., Björn Persson wrote: Neal Gompa wrote: It's extremely obvious that people want to use it. It's extremely obvious that *some* people want to use Wayland. It's equally obvious that some other people want to use X. It's also obvious that certain people want to make

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

2024-02-03 Thread Björn Persson
Neal Gompa wrote: > It's extremely obvious that people want to use it. It's extremely obvious that *some* people want to use Wayland. It's equally obvious that some other people want to use X. It's also obvious that certain people want to make *everybody else* use Wayland. On the other hand I'm

[Bug 2262451] perl-URI-5.26 is available

2024-02-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2262451 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from

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

2024-02-03 Thread Ondrej Mosnáček
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: > > >

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

2024-02-03 Thread Neal Gompa
On Fri, Feb 2, 2024 at 1:05 PM Sérgio Basto wrote: > > On Fri, 2024-02-02 at 01:34 -0600, Jonathan Bennett via devel wrote: > > 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

Re: Package review ticket status change after approval

2024-02-03 Thread Neal Gompa
On Sat, Feb 3, 2024, 11:04 AM Mattia Verga via devel < devel@lists.fedoraproject.org> wrote: > Il 01/02/24 22:44, Fabio Valentini ha scritto: > > 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

Re: Package review ticket status change after approval

2024-02-03 Thread Mattia Verga via devel
Il 01/02/24 22:44, Fabio Valentini ha scritto: > 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

Re: Failure on fedora default backgrounds

2024-02-03 Thread Dan Horák
On Fri, 2 Feb 2024 23:55:43 -0800 l...@fedoraproject.org wrote: > > > On 2024-02-01 11:26 p.m., Neal Gompa wrote: > > 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