DevHeads.net

PIM dependency metadata

Hi all,

Can someone take a look at the dependency metadata please for PIM?

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

b) kblog is unbuildable, due to CalendarCore being absent. I've no
idea where to find this. See
<a href="https://build-sandbox.kde.org/job/kblog%20master%20kf5-qt5/3/PLATFORM=Linux,compiler=gcc/console" title="https://build-sandbox.kde.org/job/kblog%20master%20kf5-qt5/3/PLATFORM=Linux,compiler=gcc/console">https://build-sandbox.kde.org/job/kblog%20master%20kf5-qt5/3/PLATFORM=Li...</a>

Thanks,
Ben

Comments

Re: PIM dependency metadata

By Sandro =?ISO-88... at 02/27/2016 - 08:51

Hey,

this was added because of ktimezoned, that is part of plasma-workspace to run
tests in kcalccore successfully. For further discussion see:
<a href="https://phabricator.kde.org/T1147" title="https://phabricator.kde.org/T1147">https://phabricator.kde.org/T1147</a>

kcalcore is the needed package. But the Build runs successfully, don't see any
problems.

Btw. what is the difference between
<a href="https://build-sandbox.kde.org" title="https://build-sandbox.kde.org">https://build-sandbox.kde.org</a> and <a href="https://build.kde.org" title="https://build.kde.org">https://build.kde.org</a>

Regards,

sandro

Re: PIM dependency metadata

By Ben Cooksley at 02/27/2016 - 15:09

On Sun, Feb 28, 2016 at 1:51 AM, Sandro KnauƟ < ... at kde dot org> wrote:
ktimezoned needs to move out of Plasma then, or the relevant classes
need to be rewritten....

That's now fixed.

build.kde.org is the production system - it uses KVM hosted VMs to run builds.

build-sandbox.kde.org is the upcoming replacement to it, and uses
Docker hosted containers to run builds (on Linux anyway, Windows will
end up using KVM when we deploy that)

Cheers,
Ben

Re: PIM dependency metadata

By David Faure at 02/29/2016 - 03:46

On Sunday 28 February 2016 08:09:38 Ben Cooksley wrote:
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?

Re: PIM dependency metadata

By Martin Klapetek at 02/29/2016 - 14:23

Note that this daemon is used these days only to signal a timezone change
iirc,
you can get current/any timezone by using QTimeZone.

Cheers

Re: PIM dependency metadata

By Sandro =?ISO-88... at 02/29/2016 - 09:46

Hey,

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. And If I
understood people right ktimezond is than not needed anymore.

But nether the less ktimezond should live outside plasma.

Regards,

sandro

Re: PIM dependency metadata

By Scarlett Clark at 02/27/2016 - 10:04

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 dependencies.
Please update logical-module-structure to have all or none of pim in the
stable builds.
Thanks,
Scarlett

Re: PIM dependency metadata

By Boudhayan Gupta at 02/26/2016 - 19:10

Hi,

KF5CalendarCore is in kcalcore, and looking at the logs it seems to be
in the list of deps.

-- Boudhayan