Re: KDiagram - Persistent FTBFS for stable branch on Windows

[joerg pauly de]

Greetings, I have now accepted document that you presented to me yesterday.
Unfortunately, some important details are missing in it. Please add
information. You can discover your paper attached to the letter. 



On 2020-10-12 11:37, Calligra Suite developers and users mailing list wrote:

On 12.10.20 11:23, Milian Wolff wrote: > On Montag, 12. Oktober 2020
11:11:22 CEST Ben Cooksley wrote: >> Hi KDiagram Developers, >> >> The
stable branch of KDiagram has been persistently failing to build from >>
source now on Windows for a period greater than 5 days. > > Hey Ben, > >
can you link me to such a CI failure? Then I could try to blind-fix it, as
I > don't have a KDE-on-windows setup here. But maybe it's simple enough to
fix > even without that. Just FTR for everyone's benefit:
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows#Virtual_Machines
Ever so useful to have if one deals with windows breakage more than once a
year ;) HS<>

Re: KDiagram - Persistent FTBFS for stable branch on Windows

[Milian Wolff]

On Montag, 12. Oktober 2020 11:11:22 CEST Ben Cooksley wrote:
> Hi KDiagram Developers,
> 
> The stable branch of KDiagram has been persistently failing to build from
> source now on Windows for a period greater than 5 days.

Hey Ben,

can you link me to such a CI failure? Then I could try to blind-fix it, as I 
don't have a KDE-on-windows setup here. But maybe it's simple enough to fix 
even without that.

Cheers

> It would be appreciated if you could please remedy this situation without
> delay, as your failure prevents the CI system from operating services
> correctly for the following projects:
> - KStars
> - Konversation
> - Skrooge
> - Okteta
> - KDiff3
> - Alkimia
> - KMyMoney
> - KRename

-- 
Milian Wolff
m...@milianw.de
http://milianw.de

signature.asc
Description: This is a digitally signed message part.

Re: KDiagram - Persistent FTBFS for stable branch on Windows

[Milian Wolff]

On Montag, 12. Oktober 2020 11:28:45 CEST Ben Cooksley wrote:
> On Mon, Oct 12, 2020 at 10:24 PM Milian Wolff  wrote:
> > On Montag, 12. Oktober 2020 11:11:22 CEST Ben Cooksley wrote:
> > > Hi KDiagram Developers,
> > > 
> > > The stable branch of KDiagram has been persistently failing to build
> > > from
> > > source now on Windows for a period greater than 5 days.
> > 
> > Hey Ben,
> 
> Hi Milian,
> 
> > can you link me to such a CI failure? Then I could try to blind-fix it, as
> > I
> > don't have a KDE-on-windows setup here. But maybe it's simple enough to
> > fix
> > even without that.
> 
> I suspect the fix just needs cherry picking - hopefully it isn't too
> complicated to fix.
> 
> The failure log is at
> https://build.kde.org/job/Calligra/job/kdiagram/job/stable-kf5-qt5%20Windows
> MSVCQt5.15/4/consoleText More recent builds can be found at
> https://build.kde.org/job/Calligra/job/kdiagram/job/stable-kf5-qt5%20Windows
> MSVCQt5.15/

Thanks, but that's looking worse then I expected. I guess backporting 
`35e86e964908ee906dde4f0678c16a838e4712dd` is worth a shot.

@Dag: what do you say, should that be safe enough to do?

Cheers

-- 
Milian Wolff
m...@milianw.de
http://milianw.de

signature.asc
Description: This is a digitally signed message part.

Re: KDiagram - Persistent FTBFS for stable branch on Windows

[Harald Sitter]

On 12.10.20 11:23, Milian Wolff wrote:
> On Montag, 12. Oktober 2020 11:11:22 CEST Ben Cooksley wrote:
>> Hi KDiagram Developers,
>>
>> The stable branch of KDiagram has been persistently failing to build from
>> source now on Windows for a period greater than 5 days.
> 
> Hey Ben,
> 
> can you link me to such a CI failure? Then I could try to blind-fix it, as I 
> don't have a KDE-on-windows setup here. But maybe it's simple enough to fix 
> even without that.

Just FTR for everyone's benefit:
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows#Virtual_Machines

Ever so useful to have if one deals with windows breakage more than once
a year ;)

HS



signature.asc
Description: OpenPGP digital signature

Re: KDiagram - Persistent FTBFS for stable branch on Windows

[Ben Cooksley]

On Mon, Oct 12, 2020 at 10:24 PM Milian Wolff  wrote:

> On Montag, 12. Oktober 2020 11:11:22 CEST Ben Cooksley wrote:
> > Hi KDiagram Developers,
> >
> > The stable branch of KDiagram has been persistently failing to build from
> > source now on Windows for a period greater than 5 days.
>
> Hey Ben,
>

Hi Milian,


>
> can you link me to such a CI failure? Then I could try to blind-fix it, as
> I
> don't have a KDE-on-windows setup here. But maybe it's simple enough to
> fix
> even without that.
>

I suspect the fix just needs cherry picking - hopefully it isn't too
complicated to fix.

The failure log is at
https://build.kde.org/job/Calligra/job/kdiagram/job/stable-kf5-qt5%20WindowsMSVCQt5.15/4/consoleText
More recent builds can be found at
https://build.kde.org/job/Calligra/job/kdiagram/job/stable-kf5-qt5%20WindowsMSVCQt5.15/


>
> Cheers
>

Cheers,
Ben


>
> > It would be appreciated if you could please remedy this situation without
> > delay, as your failure prevents the CI system from operating services
> > correctly for the following projects:
> > - KStars
> > - Konversation
> > - Skrooge
> > - Okteta
> > - KDiff3
> > - Alkimia
> > - KMyMoney
> > - KRename
>
> --
> Milian Wolff
> m...@milianw.de
> http://milianw.de

KDiagram - Persistent FTBFS for stable branch on Windows

[Ben Cooksley]

Hi KDiagram Developers,

The stable branch of KDiagram has been persistently failing to build from
source now on Windows for a period greater than 5 days.

It would be appreciated if you could please remedy this situation without
delay, as your failure prevents the CI system from operating services
correctly for the following projects:
- KStars
- Konversation
- Skrooge
- Okteta
- KDiff3
- Alkimia
- KMyMoney
- KRename

Regards,
Ben

KDiagram 2.6.0 released

[Friedrich W. H. Kossebau]

Hi,

KDiagram 2.6.0 has been tagged and is now available on the KDE servers.

http://download.kde.org/stable/kdiagram/2.6.0/src/
kdiagram-2.6.0.tar.xz.mirrorlist
commit 56aaece273f615da52e2f7ddd93c4b04d66c2fed
sha256 02788dad7e15c64b74a2d1073c5910469ab4cf46ba905030c1713dce45981882

KDiagram is the bundle of KChart (library for creating all kind of charts) and 
KGantt (library for creating Gantt diagrams).

Known users of either of those libraries are ...
... already:
  * Massif Visualizer
... in upcoming release:
  * KMyMoney
  * KDE PIM EventViews & IncidenceEditor
  * Calligra Plan & chart component
... perhaps in some upcoming release:
  * KReport/Kexi

For some background info on KDiagram see
https://marc.info/?l=kde-core-devel=142335191017238=2

Cheers
Friedrich

Re: KDiagram

[Friedrich W. H. Kossebau]

Hi Dag,

Am Freitag, 28. Oktober 2016, 16:49:50 CET schrieb Dag:
> As for KDiagram, I have a few issues.

Issues, but no showstoppers for the initial release, did I understand that 
correctly?

> KChart:
> When I remove or add datasets, the labels are not updated. Labels are
> updated if I refresh the chart so it can clearly be fixed from outside
> KChart, so no big issue.

How can I reproduce that exactly? Please file that also as a bug, best for 
kdiagram:KChart, so it can be tracked.

Cheers
Friedrich

Re: KDiagram

[Friedrich W. H. Kossebau]

Hi,

Am Freitag, 28. Oktober 2016, 16:49:50 CET schrieb Dag:
> KGantt:
> Printing on multiple pages seems to be possible only "horizontally" as I
> can specify a time span to print.
> However, if I have more tasks than can fit on one page "vertically" the
> printout is scaled to fit the page. I can't see how I can split this on
> multiple pages.
> I think this requires new API.
> 
> Zooming in/out switches between different time scales to make it easier
> for user to see where he is. The switching isn't optimal most notably in
> the low end (Day/Hour) and in the high end (Year/Month). Inge made a
> very useful layout for Year/Day in 2.x but KDAB has totally rewritten
> this part of the code so we can't use it :(
> They have also added api to add a custom layout, which could be useful,
> but maybe we should make it possible to set layouts for all cases.
> I would suspect kontact would have an issue with the Day/Hour layout
> too.

Currently I have just subscribed to working on release management of KDiagram, 
no time available for working on KGantt itself. So allow me to forward this 
discussion to the PIM people and also Andreas, hoping for some synergy :)

(Context: Calligra Plan, a project management program, where Dag is author & 
maintainer, uses KGantt from KDiagram. See https://calligra.org/plan/)

Cheers
Friedrich

KDiagram

[Dag]

Hi Friedrich.
First, a big thanks for the enormous amount of work you have put in to 
port to qt5/kf5.


As for KDiagram, I have a few issues.

KChart:
When I remove or add datasets, the labels are not updated. Labels are 
updated if I refresh the chart so it can clearly be fixed from outside 
KChart, so no big issue.


KGantt:
Printing on multiple pages seems to be possible only "horizontally" as I 
can specify a time span to print.
However, if I have more tasks than can fit on one page "vertically" the 
printout is scaled to fit the page. I can't see how I can split this on 
multiple pages.

I think this requires new API.

Zooming in/out switches between different time scales to make it easier 
for user to see where he is. The switching isn't optimal most notably in 
the low end (Day/Hour) and in the high end (Year/Month). Inge made a 
very useful layout for Year/Day in 2.x but KDAB has totally rewritten 
this part of the code so we can't use it :(
They have also added api to add a custom layout, which could be useful, 
but maybe we should make it possible to set layouts for all cases.
I would suspect kontact would have an issue with the Day/Hour layout 
too.


Cheers, Dag

Re: kdiagram in calligra project component?

[Jaroslaw Staniek]

On 7 September 2016 at 10:26, Ben Cooksley  wrote:

> Hi,
>
> Sorry, I don't see what I need to answer here?
>

Ben, ​Sorry, actually you're CCd here but I see you already presented
valuable  perspective in the comments of https://phabricator.kde.org/D2659.
The final choice for hierarchy belongs Friedrich, the maintainer.
​

regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek

Re: kdiagram in calligra project component?

[Ben Cooksley]

Hi,

Sorry, I don't see what I need to answer here?

Cheers,
Ben

Re: kdiagram in calligra project component?

[Jaroslaw Staniek]

On 5 September 2016 at 02:47, Friedrich W. H. Kossebau <kosse...@kde.org> wrote:
>
> Hi Jarosław,
>
> Am Montag, 5. September 2016, 01:03:32 CEST schrieb Jaroslaw Staniek:
> > Hi,
> > Background: The kde:sysadmin/repo-metadata git repo now replaces the
> > project.kde.org stuff.
> > I am moving kdb, kreport and kproperty repo metadata to projects/calligra
> > from playground/libs as I see them more fit to the new location and they
> > are, well, developed within our master project Calligra anyway, regardless
> > of repo fragmentation.
> >
> > That's not my play, the kde:releaseme tool which I'd be trying to use for
> > preparing releases depends on the projects metadata so it's good to have
> > the metadata as correct as possible.
> >
> > Now, that's mostly a question to Friedrich:
> >
> > There is projects/extragear/graphics/kdiagram. It describes "Powerful
> > libraries (KChart, KGantt) for creating business diagrams". Do you think
> > that kdiagram better fits to calligra/ and not so much to graphics/?
> > KChart clearly implements office-oriented objects: data charts and Gantt
> > charts.
>
> For one, those paths in the repo hierachy are just legacy and long-term will
> be dropped, for a flat list of repos.

That changes some of what I wrote but not the directory hierarchy, right?

> Then, that description is copied unchanged from marketing-buzzword loaded
> origin :)
>
> I had put kdiagram into projects/extragear/graphics after discussion as
> diagrams can be used for lots of things. There is a (business) world outside
> offices :)
> Current users known to me of either KChart or KGantt are Massif-Visualizer,
> something in KDEPIM, KMyMoney, Plan, a Calligra shape plugin and a KReport
> plugin.
> So KDiagram is a project shared by many KDE projects, nothing Calligra-centric
> there. So I do not see a reason to move this.

There's a graph for project organization, there's graph related to
what purposes are supported.
We won't simplify that in other way than tagging.
On thing sure is that the two libs from KDiagram form a framework. So
is the place within frameworks/ too? See my question below.

> More, as long as that legacy adressing hierarchy of repos exists, I would
> rather recommend to move non-Calligra-only stuff like KDb, KReport & KProperty
> somewhere into the generic extragear namespace, as those libs target
> developers, unlike the "apps" which make up what currently is known as
> Calligra and what is about end user products. By being in the generic
> extragear namespace this might help stressing the libs general usability
> outside of the existing set of Calligra apps.

I'd like to be consistent with what we said about extragear. You
didn't like it in the "State of Proposal to improving KDE Software
Repository Organization" thread and also Ben "would like to see the
Extragear moniker dropped." I agree.

I have to admit that I had to run deep-search to find kdiagram dir in
sysadmin/repo-metadata.git. I can imagine people may need the same for
kdb, etc.

Question: Based on what we say here ideally I'd like the
KDb/KProperty/KReport to be seen as projects/frameworks/. Is it right
place? At many levels there's no connection for these projects with
KF5.

Please review the current draft https://phabricator.kde.org/D2659 -
from what already not very right solution.

> My 2 cents on that :)

Thanks.

-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek

Re: kdiagram in calligra project component?

[Friedrich W. H. Kossebau]

Hi Jarosław,

Am Montag, 5. September 2016, 01:03:32 CEST schrieb Jaroslaw Staniek:
> Hi,
> Background: The kde:sysadmin/repo-metadata git repo now replaces the
> project.kde.org stuff.
> I am moving kdb, kreport and kproperty repo metadata to projects/calligra
> from playground/libs as I see them more fit to the new location and they
> are, well, developed within our master project Calligra anyway, regardless
> of repo fragmentation.
> 
> That's not my play, the kde:releaseme tool which I'd be trying to use for
> preparing releases depends on the projects metadata so it's good to have
> the metadata as correct as possible.
> 
> Now, that's mostly a question to Friedrich:
> 
> There is projects/extragear/graphics/kdiagram. It describes "Powerful
> libraries (KChart, KGantt) for creating business diagrams". Do you think
> that kdiagram better fits to calligra/ and not so much to graphics/?
> ​KChart clearly implements office-oriented objects: data charts and Gantt
> charts.

For one, those paths in the repo hierachy are just legacy and long-term will 
be dropped, for a flat list of repos.

Then, that description is copied unchanged from marketing-buzzword loaded 
origin :)

I had put kdiagram into projects/extragear/graphics after discussion as 
diagrams can be used for lots of things. There is a (business) world outside 
offices :)
Current users known to me of either KChart or KGantt are Massif-Visualizer, 
something in KDEPIM, KMyMoney, Plan, a Calligra shape plugin and a KReport 
plugin.
So KDiagram is a project shared by many KDE projects, nothing Calligra-centric 
there. So I do not see a reason to move this.

More, as long as that legacy adressing hierarchy of repos exists, I would 
rather recommend to move non-Calligra-only stuff like KDb, KReport & KProperty 
somewhere into the generic extragear namespace, as those libs target 
developers, unlike the "apps" which make up what currently is known as 
Calligra and what is about end user products. By being in the generic 
extragear namespace this might help stressing the libs general usability 
outside of the existing set of Calligra apps.

My 2 cents on that :)
Friedrich

Re: kdiagram in calligra project component?

[Jaroslaw Staniek]

On 5 September 2016 at 01:03, Jaroslaw Staniek <stan...@kde.org> wrote:

> Hi,
> Background: The kde:sysadmin/repo-metadata git repo now replaces the
> project.kde.org stuff.
> I am moving kdb, kreport and kproperty repo metadata to
> ​​
> projects/calligra from playground/libs
>

​Actually I invented ​projects/calligra/frameworks even, why not? It more
nicely groups by purpose. So I propose to keep kdiagram there.



> as I see them more fit to the new location and they are, well, developed
> within our master project Calligra anyway, regardless of repo fragmentation.
>
> That's not my play, the kde:releaseme tool which I'd be trying to use for
> preparing releases depends on the projects metadata so it's good to have
> the metadata as correct as possible.
>
> Now, that's mostly a question to Friedrich:
>
> There is projects/extragear/graphics/kdiagram. It describes "Powerful
> libraries (KChart, KGantt) for creating business diagrams". Do you think
> that kdiagram better fits to calligra/ and not so much to graphics/?
> ​KChart clearly implements office-oriented objects: data charts and Gantt
> charts.
>
> --
> regards, Jaroslaw Staniek
>
> KDE:
> : A world-wide network of software engineers, artists, writers, translators
> : and facilitators committed to Free Software development - http://kde.org
> Calligra Suite:
> : A graphic art and office suite - http://calligra.org
> Kexi:
> : A visual database apps builder - http://calligra.org/kexi
> Qt Certified Specialist:
> : http://www.linkedin.com/in/jstaniek
>



-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek

kdiagram in calligra project component?

[Jaroslaw Staniek]

Hi,
Background: The kde:sysadmin/repo-metadata git repo now replaces the
project.kde.org stuff.
I am moving kdb, kreport and kproperty repo metadata to projects/calligra
from playground/libs as I see them more fit to the new location and they
are, well, developed within our master project Calligra anyway, regardless
of repo fragmentation.

That's not my play, the kde:releaseme tool which I'd be trying to use for
preparing releases depends on the projects metadata so it's good to have
the metadata as correct as possible.

Now, that's mostly a question to Friedrich:

There is projects/extragear/graphics/kdiagram. It describes "Powerful
libraries (KChart, KGantt) for creating business diagrams". Do you think
that kdiagram better fits to calligra/ and not so much to graphics/?
​KChart clearly implements office-oriented objects: data charts and Gantt
charts.

-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek