BUILD UNSTABLE
Build URL
https://build.kde.org/job/Plasma/job/kwin/job/kf5-qt5%20FreeBSDQt5.15/1110/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Thu, 29 Apr 2021 05:39:09 +
Build duration:
34 min and counting
JUnit Tests
Name: projectroot Faile
BUILD FAILURE
Build URL
https://build.kde.org/job/Plasma/job/kwin/job/kf5-qt5%20FreeBSDQt5.15/1109/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Thu, 29 Apr 2021 05:34:40 +
Build duration:
4 min 12 sec and counting
CONSOLE OUTPUT
[...truncated 2
BUILD FAILURE
Build URL
https://build.kde.org/job/Plasma/job/kwin/job/kf5-qt5%20FreeBSDQt5.15/1108/
Project:
kf5-qt5 FreeBSDQt5.15
Date of build:
Thu, 29 Apr 2021 05:31:41 +
Build duration:
2 min 13 sec and counting
CONSOLE OUTPUT
[...truncated 2
On Wed, Apr 28, 2021 at 10:27 AM Vlad Zahorodnii
wrote:
>
> On 3/23/21 6:27 PM, Aleix Pol wrote:
> > I don't feel like there's a use-case for it.
> >
> > I also don't have the feeling that having 2 separate repositories help
> > with anything. Moving code from one side to another is cumbersome and
On 3/23/21 6:27 PM, Aleix Pol wrote:
I don't feel like there's a use-case for it.
I also don't have the feeling that having 2 separate repositories help
with anything. Moving code from one side to another is cumbersome and
makes history tracking more complex.
I think it would be even cool if we
On Wed, Apr 28, 2021 at 1:00 AM Aleix Pol wrote:
>
> Hi Marco,
> I'm not sure I fully understand what the plan is there. Why are you
> calling it plasma5support? Is it so it can be deprecated?
yes, the idea for dataengines and potentially other things is to be
deprecated and be gradually ported o
