[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: Re: Plamsa Stable Build.kde.org failures
From: David Edmundson <david () davidedmundson ! co ! uk>
Date: 2016-07-01 10:41:24
Message-ID: CAGeFrHAWddeLib9xHdbH69QnZ=TF6HHbwrCsSH_2akMjth_80A () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Jun 30, 2016 at 10:25 PM, Ben Cooksley <bcooksley@kde.org> wrote:
> Hi David,
>
> On Fri, Jul 1, 2016 at 12:50 AM, David Edmundson
> <david@davidedmundson.co.uk> wrote:
> > I wanted to write up why Plasma stable is failing on CI so that we have a
> > written down record. (and so we don't keep getting told off by sysadmins
> for
> > not fixing it)
>
> Sorry if it seems like we've done that.
> I don't see any issue with the situation we're in here - Qt version
> upgrades happen.... (although advance notice of needing it is nice so
> we can be ready in advance)
>
> >
> > Plasma 5.7 requires Qt 5.6
> > The "stable-kf5-qt5 " layer on CI builds against Qt 5.5
> >
> > Can we set Plasma stable to use latest Qt/Frameworks (the kf5-qt5 layer
> > master uses):
> >
> > Yes, but:
> > [10:06] <bcooksley> you'll just end up without a CI on your master
> >
> >
> > Can we update the stable-kf5-qt5 layer to use a newer Qt:
> > Not without upping the Qt used by Applications/16.04
> >
> > Could we add another layer:
> >
> > [10:04] <bcooksley> new layer is even more painful
> > [10:04] <bcooksley> requires adjusting the DSL
> > [10:04] <bcooksley> and building Qt another time
> > [10:05] <bcooksley> plus all of Frameworks
> > [10:05] <bcooksley> and anything else which Plasma happens to need in
> there
> >
> > Is there a long term plan:
> >
> > Michael Pyne/Ben have a thread redesigning logical-module-strucutre in
> that
> > long email thread somewhere. See thread
> > "Proposal to improving KDE Software Repository Organization"
>
> Anyone interested in helping with this point?
>
> >
> >
> > Is there a short term plan:
> >
> > Personally I think our our only viable short term options are:
> > - forcing Qt5.6 on the stable branches of applications. Theoretically
> it
> > won't break anything (though in practice who knows)
> > - turning off the CI for Plasma stable for now.
>
> Option #1 from that list is probably the easiest thing.
> Applications doesn't actually need Qt 5.5 - it just happens to be what
> is there currently.
>
> It does mean a carefully orchestrated rebuild of everything on
> stable-kf5-qt5 is necessary though, due to Qt's issues with
> compatibility.
>
> Does carefully orchestrated mean clicking "rebuild now" on everything in a
vaguely valid order until it works?
If so I can do that. Just give me the go ahead and I'll make the changes
David
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 30, \
2016 at 10:25 PM, Ben Cooksley <span dir="ltr"><<a href="mailto:bcooksley@kde.org" \
target="_blank">bcooksley@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi David,<br> <span><br>
On Fri, Jul 1, 2016 at 12:50 AM, David Edmundson<br>
<<a href="mailto:david@davidedmundson.co.uk" \
target="_blank">david@davidedmundson.co.uk</a>> wrote:<br> > I wanted to write \
up why Plasma stable is failing on CI so that we have a<br> > written down record. \
(and so we don't keep getting told off by sysadmins for<br> > not fixing \
it)<br> <br>
</span>Sorry if it seems like we've done that.<br>
I don't see any issue with the situation we're in here - Qt version<br>
upgrades happen.... (although advance notice of needing it is nice so<br>
we can be ready in advance)<br>
<span><br>
><br>
> Plasma 5.7 requires Qt 5.6<br>
> The "stable-kf5-qt5 " layer on CI builds against Qt 5.5<br>
><br>
> Can we set Plasma stable to use latest Qt/Frameworks (the kf5-qt5 layer<br>
> master uses):<br>
><br>
> Yes, but:<br>
> [10:06] <bcooksley> you'll just end up without a CI on your master<br>
><br>
><br>
> Can we update the stable-kf5-qt5 layer to use a newer Qt:<br>
> Not without upping the Qt used by Applications/16.04<br>
><br>
> Could we add another layer:<br>
><br>
> [10:04] <bcooksley> new layer is even more painful<br>
> [10:04] <bcooksley> requires adjusting the DSL<br>
> [10:04] <bcooksley> and building Qt another time<br>
> [10:05] <bcooksley> plus all of Frameworks<br>
> [10:05] <bcooksley> and anything else which Plasma happens to need in \
there<br> ><br>
> Is there a long term plan:<br>
><br>
> Michael Pyne/Ben have a thread redesigning logical-module-strucutre in that<br>
> long email thread somewhere. See thread<br>
> "Proposal to improving KDE Software Repository Organization"<br>
<br>
</span>Anyone interested in helping with this point?<br>
<span><br>
><br>
><br>
> Is there a short term plan:<br>
><br>
> Personally I think our our only viable short term options are:<br>
> - forcing Qt5.6 on the stable branches of applications. Theoretically it<br>
> won't break anything (though in practice who knows)<br>
> - turning off the CI for Plasma stable for now.<br>
<br>
</span>Option #1 from that list is probably the easiest thing.<br>
Applications doesn't actually need Qt 5.5 - it just happens to be what<br>
is there currently.<br>
<br>
It does mean a carefully orchestrated rebuild of everything on<br>
stable-kf5-qt5 is necessary though, due to Qt's issues with<br>
compatibility.<br>
<span><br></span></blockquote><div>Does carefully orchestrated mean clicking \
"rebuild now" on everything in a vaguely valid order until it \
works?<br><br></div><div>If so I can do that. Just give me the go ahead and I'll \
make the changes<br><br></div><div>David<br></div><div> \
<br></div></div><br></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic