[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-frameworks-devel
Subject: Re: kf6 vs. kf5 conflict report
From: Ben Cooksley <bcooksley () kde ! org>
Date: 2023-03-10 8:41:04
Message-ID: CA+XidOHjQ_HgBNXk=QwNqHN0NK5qaU=nML-OuNSahDUkiVnQRA () mail ! gmail ! com
[Download RAW message or body]
On Thu, Mar 9, 2023 at 4:56 AM Aleix Pol <aleixpol@kde.org> wrote:
> On Wed, Mar 8, 2023 at 3:13 PM Nicolas Fella <nicolas.fella@gmx.de> wrote:
> >
> > On 3/8/23 14:02, Harald Sitter wrote:
> > > with kf6 progressing nicely here's a first conflict report of files
> > > that appear in both kf6 and kf5 under the same name. this largely
> > > affects translations and docs it seems. this list may not be entirely
> > > comprehensive, I've only thrown together a script in a couple minutes.
> >
> > Thanks Harald!
> >
> > > one question is whether ECM should be co-installable, not sure if that
> > > has been discussed
> >
> > It has come up, and the answer seems to be "No, it will not be
> > coinstallable". This implies that ECM master will continue to support
> > Qt5/KF5, but that should not be a huge burden.
>
From my perspective this has been incredibly poorly communicated to the
point that it is not an actual valid decision.
It is also not what was set in the branch-rules.yml files within the
metadata (which was committed by a Frameworks devel) and was not what was
confirmed by Frameworks developers when I put together the list of projects
to have KF5 master branch builds removed from the CI artifacts store.
This state of affairs has been the source of a degree of CI breakage we
have been experiencing (things are a mess at the moment, I don't even want
to look at any of it)
> >
> > > report for /usr:
> > > https://collaborate.kde.org/s/3gz2KfoGLsS4TF5
> > >
> > > furthermore the following files outside /usr clash between kf6 and 5:
> > > '/etc/xdg/accept-languages.codes'
> > > '/etc/xdg/kshorturifilterrc'
> > > '/etc/xdg/autostart/baloo_file.desktop'
> > > '/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules'
> > >
> > > HS
>
> If ECM master has to support KF5, why do we have a kf5 branch? In
> fact, I'm pretty sure I switched it eventually because there were
> regressions.
>
> Aleix
>
Regards,
Ben
[Attachment #3 (text/html)]
<div dir="ltr"><div dir="ltr">On Thu, Mar 9, 2023 at 4:56 AM Aleix Pol <<a \
href="mailto:aleixpol@kde.org">aleixpol@kde.org</a>> wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Mar 8, 2023 at \
3:13 PM Nicolas Fella <<a href="mailto:nicolas.fella@gmx.de" \
target="_blank">nicolas.fella@gmx.de</a>> wrote:<br> ><br>
> On 3/8/23 14:02, Harald Sitter wrote:<br>
> > with kf6 progressing nicely here's a first conflict report of files<br>
> > that appear in both kf6 and kf5 under the same name. this largely<br>
> > affects translations and docs it seems. this list may not be entirely<br>
> > comprehensive, I've only thrown together a script in a couple \
minutes.<br> ><br>
> Thanks Harald!<br>
><br>
> > one question is whether ECM should be co-installable, not sure if that<br>
> > has been discussed<br>
><br>
> It has come up, and the answer seems to be "No, it will not be<br>
> coinstallable". This implies that ECM master will continue to support<br>
> Qt5/KF5, but that should not be a huge \
burden.<br></blockquote><div><br></div><div>From my perspective this has been \
incredibly poorly communicated to the point that it is not an actual valid \
decision.</div><div><br></div><div>It is also not what was set in the \
branch-rules.yml files within the metadata (which was committed by a Frameworks \
devel) and was not what was confirmed by Frameworks developers when I put together \
the list of projects to have KF5 master branch builds removed from the CI artifacts \
store.</div><div><br></div><div><div>This state of affairs has been the source of a \
degree of CI breakage we have been experiencing (things are a mess at the moment, I \
don't even want to look at any of it)</div></div><div> </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> ><br>
> > report for /usr:<br>
> > <a href="https://collaborate.kde.org/s/3gz2KfoGLsS4TF5" rel="noreferrer" \
target="_blank">https://collaborate.kde.org/s/3gz2KfoGLsS4TF5</a><br> > ><br>
> > furthermore the following files outside /usr clash between kf6 and 5:<br>
> > '/etc/xdg/accept-languages.codes'<br>
> > '/etc/xdg/kshorturifilterrc'<br>
> > '/etc/xdg/autostart/baloo_file.desktop'<br>
> > '/lib/udev/rules.d/61-kde-bluetooth-rfkill.rules'<br>
> ><br>
> > HS<br>
<br>
If ECM master has to support KF5, why do we have a kf5 branch? In<br>
fact, I'm pretty sure I switched it eventually because there were<br>
regressions.<br>
<br>
Aleix<br></blockquote><div><br></div><div>Regards,</div><div>Ben </div></div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic