On Mon, Feb 29, 2016 at 2:46 AM, David Faure wrote:
> On Sunday 28 February 2016 08:09:38 Ben Cooksley wrote:
> > On Sun, Feb 28, 2016 at 1:51 AM, Sandro Knauß wrote:
> > > Hey,
> > >
> > >> There are a couple of issues, namely:
> > >> a) For some reason it depends on plasma-workspace - this see
Hey,
> Yep, this sounds like ktimezoned should move to KF5.
>
> How are non-plasma users supposed to get correct timezones in e.g. PIM apps
> otherwise?
non-plamsa users are currently doomed :D Mostly I wanted a happy CI to do the
rewrite from KDateTime,KTimezone etc. to theire QT5 replacements
On Sunday 28 February 2016 08:09:38 Ben Cooksley wrote:
> On Sun, Feb 28, 2016 at 1:51 AM, Sandro Knauß wrote:
> > Hey,
> >
> >> There are a couple of issues, namely:
> >> a) For some reason it depends on plasma-workspace - this seems
> >> completely wrong to me. Please be careful when adding item
Hey,
> There are a couple of issues, namely:
> a) For some reason it depends on plasma-workspace - this seems
> completely wrong to me. Please be careful when adding items to the
> dependency chain
this was added because of ktimezoned, that is part of plasma-workspace to run
tests in kcalccore
On Sun, Feb 28, 2016 at 1:51 AM, Sandro Knauß wrote:
> Hey,
>
>> There are a couple of issues, namely:
>> a) For some reason it depends on plasma-workspace - this seems
>> completely wrong to me. Please be careful when adding items to the
>> dependency chain
>
> this was added because of ktimezone
sandbox is where I test new features. Namely we are pushing docker builds.
There is a new icu so we have to rebuild everything.
There are more issues. For stable-kf5-qt5 only some of the pim stack has
Applications 15.12 in the metadata so of course only part of the stack can
build due to missing d
