<div dir="ltr"><div dir="ltr">On Wed, Jul 24, 2024 at 11:11 AM Ralf Habacker <<a href="mailto:ralf.habacker@freenet.de">ralf.habacker@freenet.de</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"><u></u>
<div>
<div>Am 23.07.24 um 23:36 schrieb Albert
Astals Cid:<br>
</div>
<blockquote type="cite"><span style="white-space:pre-wrap">
</span>
<pre>You didn't answer this question :)
Does that seem like a reasonable way to fix the problem? Or should we just let
people use the old kdevelop or not have php support?
We need to figure out what to do at least CI wise because it's currently
failing
<a href="https://invent.kde.org/sdk/umbrello/-/pipelines/739701" target="_blank">https://invent.kde.org/sdk/umbrello/-/pipelines/739701</a>
If you are OK with disabling the php support for now for 24.08 that seems ok
for me too.</pre>
</blockquote>
<p>I guess it depends on the expected time frame for a solution. I'm
not familiar with configuring KDE CI, so someone else would have
to do this or give me detailed instructions to enable the old
kdevelop, which would probably take some time. So disabling php
support in CI seems to be the easiest solution.</p></div></blockquote><div><br></div><div>There are a couple of pieces that need to be slotted in to make this work. </div><div>I should note that we don't like keeping old releases around so this is a temporary measure at best so you need to prioritise migrating to Qt 6.</div><div><br></div><div>1) We need to register kdev-php within the CI job seed files to ensure that the Qt 5 version within release/24.05 continues to be built. </div><div>2) You need to switch away for @same within .kde-ci.yml to the @stable tag instead.</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"><div>
<p>Ralf</p></div></blockquote><div><br></div><div>Cheers,</div><div>Ben </div></div></div>