On Wednesday, 3 April 2024 01:48:47 CEST Kevin Fenzi wrote:
> On Tue, Apr 02, 2024 at 04:06:45PM -0400, Steve Cossette wrote:
> > Alright, so a substantial amount of information changed since the original
> > submission of the change proposal. We aren't necessarily thinking of
> > demoting Gnome.
On Saturday, 10 February 2024 01:11:03 CET Kevin Kofler via devel wrote:
> By the way, what that link does not mention when it talks about "multiple
> packages for the same thing" is browsers / web engines. The Spin ships
> several applications using QtWebEngine, e.g., KMail, so that engine is not
On Friday, 9 February 2024 11:53:01 CET Sérgio Basto wrote:
> so you agree that are giving the overhead to us (the people who want
> keep X11 as it is )
Yes!!! OF COURSE!
If you wanna maintain something you need to handle the overhead! Not the other
way around!
--
On Friday, 9 February 2024 04:15:17 CET Kevin Kofler via devel wrote:
> Well, then kwin-x11 will also no longer depend on kwin
YE
> and your argument
> that it is a problem because it introduces a hard version lock will be moot.
Well, there would be no argument to be "moot" because there
On Thursday, 8 February 2024 20:21:19 CET Roy Bekken wrote:
> You mean the proposal from kde-sig that they wanted changing to plasma 6 and
> dropping X11 because they have no interest of supporting it?
>
Yes. Interest *and* resources.
> Don’t see why that should prevent someone else from
On Thursday, 8 February 2024 12:33:29 CET Sérgio Basto wrote:
> you are removing X11 from the builds deliberately ,
Yes. And the moment this: https://invent.kde.org/plasma/kwin/-/issues/139 gets
implemented we will not have to remove anything.
(remember that the Change Proposal was approved)
>
On Wednesday, 7 February 2024 13:21:15 CET Peter Boy wrote:
> If KDE Sig wants to attract users to Wayland, then the only good strategy is
> to make Wayland better than the previous way (i.e. Xorg) and promote that
> fact actively.
Does something make you think that we do not?
> Simply banning
On Sunday, 4 February 2024 03:55:42 CET Kevin Kofler via devel wrote:
> 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
>
On Friday, 2 February 2024 00:38:56 CET Kevin Kofler via devel wrote:
> To make it clear about the situation of that particular package: The KDE SIG
> never notifies me in advance about kdepim bumps.
To make it clear about this particular package:
- we have _forgotten_ indeed to notify the
On Friday, 2 February 2024 00:49:19 CET Kevin Kofler via devel wrote:
> This can be solved with communication.
>
That is dealing with the situation your packages would cause, not solving it.
( I don't mean ill will, it just a statement)
> That said, if the KDE SIG does not want to have to
On Wednesday, 7 February 2024 05:07:28 CET Garry T. Williams wrote:
> I went to compose an E-mail message using kmail and its composer
> window and noticed it was broken.[*] I couldn't even find a bug
> report about this. I fear it's because many others just ignored the
> various bugs and went
On Saturday, 3 February 2024 17:52:42 CET Adam Williamson wrote:
> Why? This is the part I don't understand. Can you explain it in more
> detail? Thanks.
If we update plasma-workspace and kwin we are likely gonna break binary
compatibility with the proposed packages.
They will need to be
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
On Tuesday, 30 January 2024 15:57:12 CET Steven A. Falco wrote:
> I'm delighted that there are like-minded folks who want to maintain X11.
> Please allow them to do so.
I will just quote you what Stephen said:
> This is
> misleading, as the move to Wayland is specifically because the
> upstream
On Tuesday, 30 January 2024 14:04:29 CET Germano Massullo wrote:
> What does it mean that FESCo is applying an injunction?
Only that the packages in question are "on hold" until a decision can be
taken.
The word sounds way worse than what it really is.
--
On Saturday, 28 October 2023 11:59:55 CEST Marc Deop i Argemí wrote:
> > * f40-build-side-76474
> > * f39-build-side-76476
> > * f38-build-side-76478
> >
>
>
> I will take care of this today (2023-10-28)
Powerdevil has been rebui
On Thursday, 26 October 2023 22:57:28 CEST Qiyu Yan wrote:
> Hi all,
>
> It is nearly a full month since last mail. And seems that koji has
> recycled the side tags due to inactivity. I re-created them:
>
> * f40-build-side-76474
> * f39-build-side-76476
> * f38-build-side-76478
>
> Seems
/plasma/discover/-/merge_requests/500
[4] https://copr.fedorainfracloud.org/coprs/g/kdesig/discover-distro-upgrade/
[5] https://blog.marcdeop.com/?p=267
[6] https://matrix.to/#/#kde:fedoraproject.org
Best regards,
--
Marc Deop i Argemí
System Engineer
On Thursday, 23 February 2023 09:48:36 CET Marc Deop i Argemí wrote:
> > - kde-runtime
> > - kdebase3
> > - kdelibs
I created a side-tag: f39-build-side-63924 and rebuilt kdelibs and kde-
runtime.
However, it turns out I don't have commit access to kdebase3. I submitted
all the needed packages there?
Thanks,
--
Marc Deop i Argemí
System Engineer
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraprojec
On Tuesday, 14 February 2023 19:13:39 CET Mattia Verga wrote:
> To the kstars maintainers: I can take care to upgrade the package, if
> you want (it's just a simple version bump and upload new sources).
>
> To the stellarium maintainers: I will wait for a patch from upstream
> before pushing the
On Friday, 10 February 2023 15:11:19 CET Marc Deop i Argemí wrote:
> On Friday, 10 February 2023 14:47:19 CET Ben Cotton wrote:
>
> > 3. kwin — kwin_wayland often crashed when used as the sddm Wayland
> > compositor and logging out of Plasma resulting in a black scree
On Friday, 10 February 2023 14:47:19 CET Ben Cotton wrote:
> 3. kwin — kwin_wayland often crashed when used as the sddm Wayland
> compositor and logging out of Plasma resulting in a black screen — NEW
> ACTION: Maintainer to diagnose issue
Before spending any significant amount of time on this,
On Monday, 8 March 2021 11:52:10 CET Miro Hrončok wrote:
> nload cicku, fab, fale, orphan 2 weeks
> ago
I'll take that one :-)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Tuesday 22 April 2014 06:34:48 Lennart Poettering wrote:
On Wed, 16.04.14 12:46, Bill Nottingham (nott...@splat.cc) wrote:
Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) said:
On Mon, Apr 14, 2014 at 04:20:16PM -0400, Bill Nottingham wrote:
Jaroslav Reznik (jrez...@redhat.com) said:
On Wednesday 17 July 2013 03:20:42 Lennart Poettering wrote:
As mentioned before, if people run programs that require
/var/log/messages they should simply install rsyslog and be done with
it.
That terribly sounds like my way or the high way.
Many people have raised concerns not only about
On Wednesday 17 July 2013 15:39:23 Lennart Poettering wrote:
On Wed, 17.07.13 14:36, Denys Vlasenko (dvlas...@redhat.com) wrote:
instead of administrators simply adding rsyslog or syslog-ng manually
at install time or to their ks snippets.
And this too was answered several times
On Monday 15 July 2013 16:29:08 Thomas Bendler wrote:
2013/7/15 Lennart Poettering mzerq...@0pointer.de
[...]
Well, assuming that bash is entirely in memory. And also, note that
neither cat, nor cp, nor tail are actually bash builtins and will not
work. It's pretty hard (though certainly
On Monday 15 July 2013 13:23:29 Lennart Poettering wrote:
Hence, the choice between journal by default + syslog optional and
journal optional + syslog by default does not exist. The choice
between journal by default + syslog by default and journal by default
+ syslog optional however does.
I
On Monday 15 July 2013 17:55:34 Lennart Poettering wrote:
On Tue, 16.07.13 00:55, Dan Fruehauf (malko...@gmail.com) wrote:
+1 - same here. You're far from being alone.
I'm still trying to get used to the new systemd in Fedora and still trying
to think why I need it. Altogether for my
On Monday 15 July 2013 13:34:58 Lennart Poettering wrote:
On Mon, 15.07.13 13:17, Martin Briza (mbr...@redhat.com) wrote:
BTW, I have some more multi-seat hardware to give away to folks who want
to add true automatic multi-seat to stuff like display managers.
It's a USB box that will
On Tuesday 19 March 2013 09:27:16 Christof Damian wrote:
Fixing an apostrophe – no
Fixing our UTF-8 handling – definitely yes
The issue here is not only about the Fedora's release name rather than fixing
our UTF-8 handling. Sounds like an important bug to fix, at least to me
Fixing them
On Thursday 31 May 2012 02:20:26 Pádraig Brady wrote:
On 05/30/2012 04:16 PM, Marc Deop wrote:
On Wednesday 30 May 2012 10:04:49 Pádraig Brady wrote:
I've some notes about 256 colors here:
http://www.pixelbeat.org/docs/terminal_colours/#256
That information is mostly fine. There are
33 matches
Mail list logo
