Re: Release, pretty please?

[Jonathan Riddell]

I don't think there's any reason why this should be necessary for
distros.  A simple message to say "don't build krita from Calligra,
build it from the standalone krita 3 now" should be enough.  Of course
a Calligra 3 ported to KF5 would also focus attention.

Jonathan


On 2 November 2016 at 13:36, Boudewijn Rempt  wrote:
> Hi...
>
> I've seen that Ubuntu has updated Krita (and Calligra) for Zesty.
> Sort of yay, but it's still only 2.9.11 and that's because there
> has been no release of Calligra 3, and packaging Krita 3 would
> conflict with the packaging of calligra 2.9.11...
>
> I would say that there should be either a Calligra 2.9.12 release
> without Krita, or a Calligra 3.0 release. If the problem is that
> there's nobody around to make tarballs and upload a Calligra 3.0
> release, well, I can do that...
>
> But I really don't want distributions to go on providing Krita
> 2.9 instead of 3.0 only because they're stuck with Calligra 2.9.
>
> --
> Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: calligra 3.0.0 tarball

[Jonathan Riddell]

Ooh exciting :)

Note this tar is available publically.  I'm not sure if that's what
you want at this stage.  It means that you can't just remove or
replace the tar because then the mirror system might break, you'd need
to find a different name for the tar and then I think you can remove
this one and make it into a symlink to the new one.

Jonathan


On 5 December 2016 at 09:24, Boudewijn Rempt  wrote:
> Hi,
>
> I've tagged v3.0.0 and created a tarball and uploaded it: 
> http://download.kde.org/stable/calligra-3.0.0 .
>
> Please check if everything is okay, and if not, fix it; then I can move the 
> tag and repack and re-upload.
>
> --
> Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

Re: calligra 3.0.0 tarball

[Jonathan Riddell]

Also there's no PGP signature with the tar which isn't following
current best practice.  Release scripts such as releaseme will do this
for you

Jonathan


On 5 December 2016 at 10:07, Dag  wrote:
> Thanks Boudewijn
>
> Boudewijn Rempt skrev den 2016-12-05 10:24:
>>
>> Hi,
>>
>> I've tagged v3.0.0 and created a tarball and uploaded it:
>> http://download.kde.org/stable/calligra-3.0.0 .
>>
>> Please check if everything is okay, and if not, fix it; then I can
>> move the tag and repack and re-upload.
>
> Yes there are problems. I sort of hoped you had picked up on the problems
> with i18n which means we can't release yet.
> I think I have fixed the problems, I'm still testing.
>
> That said, I see that there is no po files (except calligra.po) in your
> tarball. I thought the po files available in trunk should have been
> included?
>

Re: calligra 3.0.0 tarball

[Jonathan Riddell]

On 7 December 2016 at 10:03, Boudewijn Rempt  wrote:
> Yes, that worked. I've removed and re-uploaded a new tarball.

As I said this will confuse mirrors which often won't mirror a changed
file on the server.  If you want to upload files before they are ready
to publish you should set permissions 660 so they can't be ready by
the web server.  Now that it is public you need to find a different
file name (you can then remove the old one and make it a symlink to
the new one).  You could move it to follow the more common directory
pattern of calligra/3.0.0/calligra-3.0.0.tar.gz for example.

Always amazing how our top devs struggle with gpg.  If the gpg-agent
isn't working then kill it, maybe remove it's files and remove any
settings in ~/.gnupg/gpg.conf

I've got it building now from git master in KDE neon (dev stable branch for now)
http://build.neon.kde.org/job/xenial_stable_calligra_calligra_bin_amd64/1/console

Which of these missing build-deps do I need to care about?
Phonon4Qt5Experimental (required version == 4.9.51)
Vc (required version >= 1.1.0) , Portable, zero-overhead SIMD library
for C++ , 
PopplerXPDFHeaders , XPDF headers in the Poppler Qt5 interface library
, 
Libgit2
Libqgit2
Cauchy , Cauchy's M2MML, a Matlab/Octave to MathML compiler ,


Jonathan

Re: calligra 3.0.0 tarball

[Jonathan Riddell]

 Did I hear that Brainbump isn't built?  It does get built in my build
from master

Jonathan


On 7 December 2016 at 10:30, Jonathan Riddell  wrote:
> On 7 December 2016 at 10:03, Boudewijn Rempt  wrote:
>> Yes, that worked. I've removed and re-uploaded a new tarball.
>
> As I said this will confuse mirrors which often won't mirror a changed
> file on the server.  If you want to upload files before they are ready
> to publish you should set permissions 660 so they can't be ready by
> the web server.  Now that it is public you need to find a different
> file name (you can then remove the old one and make it a symlink to
> the new one).  You could move it to follow the more common directory
> pattern of calligra/3.0.0/calligra-3.0.0.tar.gz for example.
>
> Always amazing how our top devs struggle with gpg.  If the gpg-agent
> isn't working then kill it, maybe remove it's files and remove any
> settings in ~/.gnupg/gpg.conf
>
> I've got it building now from git master in KDE neon (dev stable branch for 
> now)
> http://build.neon.kde.org/job/xenial_stable_calligra_calligra_bin_amd64/1/console
>
> Which of these missing build-deps do I need to care about?
> Phonon4Qt5Experimental (required version == 4.9.51)
> Vc (required version >= 1.1.0) , Portable, zero-overhead SIMD library
> for C++ , <https://github.com/VcDevel/Vc>
> PopplerXPDFHeaders , XPDF headers in the Poppler Qt5 interface library
> , <http://poppler.freedesktop.org>
> Libgit2
> Libqgit2
> Cauchy , Cauchy's M2MML, a Matlab/Octave to MathML compiler ,
> <https://bitbucket.org/cyrille/cauchy>
>
> Jonathan

Calligra and Okular versions

[Jonathan Riddell]

Recently Okular's internal version changed and so did the requirement
for Okular by Calligra.

Okular is now set to 0.99.0 for the stable Applications/16.12 branch
and Calligra wants 0.99.60.

How before these versions changed I had a version of Calligra master
(due to become 3.0.0 shortly) which compiled fine with Okular from
Applications/16.12
http://build.neon.kde.org/job/xenial_stable_calligra_calligra_bin_amd64/1/

It would be a shame if Calligra released without a version of Okular
that it worked with also being released.  Does Calligra work with
Okular from Applications/16.12 ?

Jonathan

Re: Calligra and Okular versions

[Jonathan Riddell]

> Depending on whether 16.12.0 tarballs have already been made either Calligra
> needs to adapt to that now, or Okular could still get fixed.

tars have been made for 16.12 but aren't released until next week so
maybe Albert can update that

Jonathan

Re: Calligra and Okular versions

[Jonathan Riddell]

On Fri, Dec 09, 2016 at 07:55:30PM +0100, Andreas Sturmlechner wrote:
> On Friday, 9 December 2016 at 15:49, Jonathan Riddell wrote:
> > Okular is now set to 0.99.0 for the stable Applications/16.12 branch
> > and Calligra wants 0.99.60.
> 
> I was puzzled how that could happen again, since I made the calligra commit 
> that dialled back the okular requirement from 1.0.0 to 0.99.60 (which worked 
> a 
> few weeks ago). That was necessary due to okular commit   
> ebeeac8d72b258b516929344b43ceec3a57e06e7 setting version to
> 
> 0.99.${KDE_APPLICATIONS_VERSION_MICRO}
> 
> which was bound to break (go backwards) when moving from beta/RC numbers 
> 16.11.60 to 16.12.0 release.

I highlighted a related issue not long ago
https://marc.info/?l=kde-devel&m=147929111915475&w=2

Jonathan

Re: calligra 3.0.0 tarball

[Jonathan Riddell]

On 7 December 2016 at 11:06, Dag  wrote:
> Jonathan Riddell skrev den 2016-12-07 11:33:
>>
>> Did I hear that Brainbump isn't built?  It does get built in my build
>> from master
>
> Debug build yes, should not be built in release builds.
> (Same with stage and flow)

I've changed Neon packaging to use Release builds. However this is an
unusual way to use the build type flag.  Most distros will use Debug
builds to get debug symbols (which are then extracted into a separate
package). So I expect other distros will end up with Braindump being
built in their packages.

Jonathan

Re: calligra 3.0.0 tarball

[Jonathan Riddell]

On 12 December 2016 at 13:05, Boudewijn Rempt  wrote:

> Debug or RelWithDebInfo? Because plain Debug makes things pretty slow
> and enables asserts, doesn't it?

Possibly I'm wrong and worrying about nothing. We actually set cmake
build type to Debian which is a custom type we inherit from Debian and
I don't remember what's different or where that's set

Jonathan

Re: calligra 3.0.0 tarball

[Jonathan Riddell]

Debian packagers seem to think that using build type to build
different products is wrong
https://lists.alioth.debian.org/pipermail/pkg-kde-talk/2016-December/002451.html
but it's hardly rare for packagers and coders to disagree.

What's the status of releasing Calligra?  It's been on download.kde
for 10 days now

Jonathan


On 12 December 2016 at 13:38, Jonathan Riddell  wrote:
> On 12 December 2016 at 13:05, Boudewijn Rempt  wrote:
>
>> Debug or RelWithDebInfo? Because plain Debug makes things pretty slow
>> and enables asserts, doesn't it?
>
> Possibly I'm wrong and worrying about nothing. We actually set cmake
> build type to Debian which is a custom type we inherit from Debian and
> I don't remember what's different or where that's set
>
> Jonathan

Re: Future releases

[Jonathan Riddell]

On 20 December 2016 at 08:12, Dag  wrote:
> - Who can generate the final release tarball. (pnt 4 below)
>   It must be someone with a trusted pgp key (I'm not trusted, so can't do
> it).
>   It should take <30 minutes, so is there somebody out there who could help?

Any pgp key will do, the only requirement is a packager like myself
can verify it's the one the Calligra devs used which is usually done
by putting it on a pgp key server and putting the full fingerprint on
the release announcement web page and/or e-mails (not on a wiki as
Kirigami devs like to do).

> - Somewhere to upload tarball for testing/checking before released to
> download.kde.org.
>   I thought about ftp://upload.kde.org/incoming but I don't think that is
> possible?

You can't use upload.kde.org no but you could use share.kde.org or any
other of 100 services like Google Drive or Dropbox.

> 6. Publish tarball on download.kde.org (or possibly upload.kde.org)

very few people have direct access to download.kde.org, the normal
process is upload.kde.org and sysadmin request.

> 7. Notify packagers and wait some time (a week?) for feedback

A week feels a bit much to me but as you wish

Jonathan

Re: Future releases

[Jonathan Riddell]

On 20 December 2016 at 11:29, Dag  wrote:
>> Any pgp key will do, the only requirement is a packager like myself
>> can verify it's the one the Calligra devs used which is usually done
>> by putting it on a pgp key server and putting the full fingerprint on
>> the release announcement web page and/or e-mails (not on a wiki as
>> Kirigami devs like to do).
>
> Thought that was what the trust part should do, anybody could create a key
> and say they where a calligra dev.
> OTOH probably some of us would protest if calligra was released and none of
> us knew about it ;)

Put it on a trusted place like calligra.org and voila, it's trusted.
It's important to include in any announcement to packagers though so
we know what key we should be looking for.

See for example my key on https://www.kde.org/info/plasma-5.8.0.php

I do share Boud's frustration with gpg-agent, it's a tricksy beastie
which sometimes works and sometimes doesn't. But it should be possible
to turn it off and just enter any password in directly.

>>> 7. Notify packagers and wait some time (a week?) for feedback
>>
>>
>> A week feels a bit much to me but as you wish
>
> Less is more in this case. What would you suggest would be enough?

Both Plasma and Applications seem to use Thursday to Tuesday.
Frameworks leaves a week still.  With automated testing there
shouldn't be a need for so long is the thinking these days.

Jonathan

Re: 3.0.0.1 tarball + signature

[Jonathan Riddell]

Share.kde.org exists to share files or put on depot with the permissions
hidden from world readable

On Wednesday, 28 December 2016, Boudewijn Rempt  wrote:

> Hi,
>
> I've finally figured out how to fix gpg-agent, so next to
>
> http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz
>
> there's now also
>
> http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz.sig
>
> which you can use to check whether I've done everything correctly...
>
> This should be the corresponding public key:
>
> http://valdyas.org/~boud/0x58b9596c722ea3bd.asc
>
> (anyone know of a better place to put that? My webserver isn't
> configured to use https yet...)
>
> --
> Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
>

Re: 3.0.0.1 tarball + signature

[Jonathan Riddell]

On 28 December 2016 at 14:05, Boudewijn Rempt  wrote:
> http://valdyas.org/~boud/0x58b9596c722ea3bd.asc

gpg --send-key 722ea3bd

should make it appear on keyservers and you can link to it

e.g. https://sks-keyservers.net/pks/lookup?op=vindex&search=0xEC94D18F7F05997E

Re: 3.0.0.1 tarball + signature

[Jonathan Riddell]

Interestingly that gives a Bad gpg signature.  What did you use to
make the signature?

The command I use is
gpg2 --armor --detach-sign -o foo.tar.xz.sig foo.tar.xz

Jonathan

On 28 December 2016 at 14:05, Boudewijn Rempt  wrote:
> Hi,
>
> I've finally figured out how to fix gpg-agent, so next to
>
> http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz
>
> there's now also
>
> http://valdyas.org/~boud/calligra-3.0.0.1.tar.xz.sig
>
> which you can use to check whether I've done everything correctly...
>
> This should be the corresponding public key:
>
> http://valdyas.org/~boud/0x58b9596c722ea3bd.asc
>
> (anyone know of a better place to put that? My webserver isn't
> configured to use https yet...)
>
> --
> Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org

cmake error

[Jonathan Riddell]

Neon is finding a problem in the top level cmake file

09:20:14 CMake Error at CMakeLists.txt:486 (if):
09:20:14   if given arguments:
09:20:14
09:20:14 "KReport_FOUND" "AND" "GREATER" "80"
09:20:14
09:20:14   Unknown arguments specified


added earlier today
commit 84091746c37a80dc907c412d0903d7baae16415c
Author: Dag Andersen 
Date:   Fri Jan 6 09:05:22 2017 +0100

Jonathan

KReport version found is not stable

[Jonathan Riddell]

Currently our build of calligra doesn't build Plan because
"KReport version found is not stable", same for KPropertyWidgets
cmakelists.txt says this is deliberate
"This is a temporary measure to avoid that the whole calligra build
fails on build.kde.org"
but we're building the latest kreport and kpropertywidgets and
calligra.  should we hold back versions of kreport/propertywidgets? Or
just not build plan? or remove that temporary measure?

Jonathan

Re: 3.0.1 RC1 of Kexi/KDb/KProperty/KReport released

[Jonathan Riddell]

kproperty no longer has translations
3.0.0 had kproperty-3.0.0/po/pt/kproperty_qt.po files, these are not
in the 3.0.1 tar

Jonathan


On 13 March 2017 at 12:25, Jaroslaw Staniek  wrote:
> Hi,
> 3.0.1 uploaded:
> https://community.kde.org/Kexi/Releases#3.0.1_Downloads
>
> They contain minor changes compared to RC1. kexi and kdb packages have po
> folders with that we have so far, this is why their file versions are
> 3.0.1.1, not 3.0.1 (this is to address bug
> https://bugs.kde.org/show_bug.cgi?id=377488). Translations are not yet fully
> set up in the KDE infra because the libraries are under a kdereview process.
>
> The packages will be announced today unless there's a critical blocker.
>
>
> On 6 March 2017 at 00:36, Jaroslaw Staniek  wrote:
>>
>> Dear All,
>> RC1 of 3.0.1 Kexi/KDb/KProperty/KReport is available at
>> https://share.kde.org/index.php/s/Qqw6vGAS8TVox8n
>> Please test, if there are no issues reported we would release in a week.
>>
>> Order of building as always: KDb, KProperty, KReport, Kexi.
>>
>> Note: Kexi 3.0.1 depends on the libraries in version 3.0.x. Libraries in
>> version 3.1 are incompatible.
>>
>> Changelog: https://community.kde.org/Kexi/Releases#3.0.1_Changes
>>
>> Release schedule: https://community.kde.org/Kexi/Schedules#3.0.1
>>
>> --
>> 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

Re: 3.0.1 RC1 of Kexi/KDb/KProperty/KReport released

[Jonathan Riddell]

One warning on compile you may want to fix

W: kexi: desktop-mime-but-no-exec-code 
usr/share/applications/org.kde.kexi.desktop

https://lintian.debian.org/tags/desktop-mime-but-no-exec-code.html

Jonathan

Re: Release 3.0.1

[Jonathan Riddell]

The usual way to pre-release them is to upload them to the same place
as normal but keep permissions non-public so they don't end up on
download.kde.org but are accessible to packagers.

Jonathan


On 20 March 2017 at 13:30, Dag  wrote:
> Ok, git tagged v3.0.1 and tarball created.
>
> Files can be found here:
> https://share.kde.org/index.php/s/yanrJWiQFB3rrvc
>
> My public key is here:
> https://share.kde.org/index.php/s/pYwk5c7UNcXGYfP
>
> Please test.
>
> Upload etc planned for next week.
>
> Cheers,
> Dag
>

calligra master broken

[Jonathan Riddell]

Latest commit to calligra master seems to have broken compile for neon

http://build.neon.kde.org/job/xenial_stable_calligra_calligra_bin_amd64/56/console

15:17:50 /workspace/build/plan/kptview.cpp: In member function ‘void
KPlato::View::createReportView(const QDomDocument&)’:
15:17:50 /workspace/build/plan/kptview.cpp:2687:14: error:
‘ViewListReportsDialog’ was not declared in this scope
15:17:50  QPointer vd = new
ViewListReportsDialog( this, *m_viewlist, doc, this );

Jonathan

no stable translations

[Jonathan Riddell]

There's no stable translations for kexi or calligra in the stable branches

https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/calligra/


Is this deliberate or an oversight?  It messes up building packages in neon

Jonathan

Re: no stable translations

[Jonathan Riddell]

how about moving them out of kdereview into calligra? They've been in
kdereview for over 6 months

Jonathan


On 24 April 2017 at 14:47, Jaroslaw Staniek  wrote:
>
>
> On 24 April 2017 at 15:26, Jonathan Riddell  wrote:
>>
>> There's no stable translations for kexi or calligra in the stable branches
>>
>>
>> https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/calligra/
>>
>>
>> Is this deliberate or an oversight?  It messes up building packages in
>> neon
>
>
> For Kexi, its dependencies
>
> (kdb, kreport, kproperty) have no stable translations (within the KDE
> infra). The libs were still kept in playground during the 3.0 series;
> kdereview is in progress. Once it's done stable release 3.1 would make the
> fix.
>
> --
> 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

kexi stable translations

[Jonathan Riddell]

kexi has no stable translations.  I think it should be set to use the
3.0 branch?  Is that right?

Jonathan

Re: kexi stable translations

[Jonathan Riddell]

Then leave it blank indeed and wait for 3.1 branch to happen.  Nearly there :)

Jonathan


On 31 August 2017 at 14:20, Jaroslaw Staniek  wrote:
> On 31 August 2017 at 14:58, Jonathan Riddell  wrote:
>> kexi has no stable translations.  I think it should be set to use the
>> 3.0 branch?  Is that right?
>
> Jonathan,
> Today yes, it could. Or: if we could we'd have this done already. But
> dependencies we develop (kdb, kproperty, kreport) are not marked (in
> KDE terms) as stable they are in the kdereview process (1% left or
> so). So KDE policy blocked us if I remember correctly from having
> translation infra working for us.
> Other than that, the 3.0.x line is done, 3.0.2 was the last release.
> Next stable is the 3.1 planned for Sep/Oct.
> So I don't know if it's worth the effort to enable translations for
> 3.0 without releasing them.
> Feel free to provide your advice and thanks for this contact.
>
> --
> 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

kproperty translations

[Jonathan Riddell]

There's some fancy stuff in the translations extraction script for kproperty

https://cgit.kde.org/kproperty.git/tree/src/Messages.sh

This breaks the Neon builds which try to parse those Messages.sh files
to download translations
https://build.neon.kde.org/job/xenial_unstable_calligra_kproperty_src/89/console

And I'm not sure scripty is happy with it either, there's no
kpropertycore_qt.pot or kpropertywidgets_qt.pot

https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/extragear-libs/

Is there not an easier way?

Jonathan

Re: kproperty translations

[Jonathan Riddell]

On 31 October 2017 at 16:51, Jaroslaw Staniek  wrote:
> On 31 October 2017 at 17:27, Jonathan Riddell  wrote:
>> There's some fancy stuff in the translations extraction script for kproperty
>>
>> https://cgit.kde.org/kproperty.git/tree/src/Messages.sh
>>
>> This breaks the Neon builds which try to parse those Messages.sh files
>> to download translations
>> https://build.neon.kde.org/job/xenial_unstable_calligra_kproperty_src/89/console
>>
>
> Hi Jonathan,
> I've found it less intrusive than removing git history by moving cpp
> files around. The review is here: https://phabricator.kde.org/D8230.
>
> I wonder how the shell scripts are parsed, what are the assumptions.
> In the neon link releaseme only shows me internal backtrace.
> Maybe we can add metadata that you can support instead of parsing scripts.

releaseme needs the name of the .pot files spelled out, can I change
it to make it explicitly call them?

http://embra.edinburghlinux.co.uk/~jr/tmp/DIFF


>> And I'm not sure scripty is happy with it either, there's no
>> kpropertycore_qt.pot or kpropertywidgets_qt.pot
>>
>> https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/extragear-libs/
>
> IIRC there are no translations because the lib has not been approved
> via kdereview yet.

I'm talking nonsense the files are there.

Jonathan

Re: kproperty translations

[Jonathan Riddell]

That's the stable branch, which is on branch 3.0 which has the old Messages.sh

https://websvn.kde.org/trunk/l10n-kf5/templates/messages/extragear-libs/
has kpropertywidgets_qt.pot and kpropertycore_qt.pot

Can I update Messages.sh to list the .pot file explicitly?
http://embra.edinburghlinux.co.uk/~jr/tmp/DIFF

Jonathan


On 17 November 2017 at 14:39, Jaroslaw Staniek  wrote:
> Hmm I see kproperty_qt.pot, which is old. No kpropertycore_qt.pot or
> kpropertywidgets_qt.pot...
>
> On 17 November 2017 at 14:59, Jonathan Riddell  wrote:
>> On 31 October 2017 at 16:51, Jaroslaw Staniek  wrote:
>>> On 31 October 2017 at 17:27, Jonathan Riddell  wrote:
>>>> There's some fancy stuff in the translations extraction script for 
>>>> kproperty
>>>>
>>>> https://cgit.kde.org/kproperty.git/tree/src/Messages.sh
>>>>
>>>> This breaks the Neon builds which try to parse those Messages.sh files
>>>> to download translations
>>>> https://build.neon.kde.org/job/xenial_unstable_calligra_kproperty_src/89/console
>>>>
>>>
>>> Hi Jonathan,
>>> I've found it less intrusive than removing git history by moving cpp
>>> files around. The review is here: https://phabricator.kde.org/D8230.
>>>
>>> I wonder how the shell scripts are parsed, what are the assumptions.
>>> In the neon link releaseme only shows me internal backtrace.
>>> Maybe we can add metadata that you can support instead of parsing scripts.
>>
>> releaseme needs the name of the .pot files spelled out, can I change
>> it to make it explicitly call them?
>>
>> http://embra.edinburghlinux.co.uk/~jr/tmp/DIFF
>>
>>
>>>> And I'm not sure scripty is happy with it either, there's no
>>>> kpropertycore_qt.pot or kpropertywidgets_qt.pot
>>>>
>>>> https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/extragear-libs/
>>>
>>> IIRC there are no translations because the lib has not been approved
>>> via kdereview yet.
>>
>> I'm talking nonsense the files are there.
>>
>> Jonathan
>
>
>
> --
> 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

calligra/3.0 not building with stable branch of Applications

[Jonathan Riddell]

Calligra's calligras/3.0 branch current doesn't build (with
Applications/17.12 builds)

https://build.neon.kde.org/job/xenial_stable_calligra_calligra_bin_amd64/105/console

14:10:54 
/workspace/build/plan/plugins/filters/icalendar/export/icalendarexport.cpp:
In member function ‘void
ICalendarExport::createTodos(KCalCore::Calendar::Ptr, const
KPlato::Node*, long int, KCalCore::Todo::Ptr)’:
14:10:54 
/workspace/build/plan/plugins/filters/icalendar/export/icalendarexport.cpp:144:41:
error: ‘KDateTime’ was not declared in this scope
14:10:54  todo->setDtStart( KDateTime( st ) );
14:10:54  ^

Calligra 3.1 status

[Jonathan Riddell]

It's not clear what the status of Calligra 3.1 is.  There's an announce up but
https://community.kde.org/Calligra
still says 3.0.1 is stable, repo-metadata says calligra/3.0 is the
stable branch.

There's a separate calligraplan tar which isn't announed why that
seems to be separate.

Jonathan

Re: Calligra 3.1 status

[Jonathan Riddell]

But not here
https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects/calligra/calligra/i18n.json
which is used for translations and we also use it in KDE neon

Jonathan


On 6 February 2018 at 13:28, Rik Mills  wrote:
> https://cgit.kde.org/kde-build-metadata.git/tree/logical-module-structure
>
> also says:
>
> "kf5-qt5": "master",
> "stable-kf5-qt5": "calligra/3.1"
>
> On 06/02/18 13:21, Jonathan Riddell wrote:
>> It's not clear what the status of Calligra 3.1 is.  There's an announce up 
>> but
>> https://community.kde.org/Calligra
>> still says 3.0.1 is stable, repo-metadata says calligra/3.0 is the
>> stable branch.
>

Re: Calligra 3.1 status

[Jonathan Riddell]

The calligraplan tar contains translations which conflict with those
in the calligra tar

calligraplanlibs.mo  calligraplan.mo  calligraplan_scheduler_rcps.mo
calligraplan_scheduler_tj.mo  calligraplanwork.mo  krossmoduleplan.mo

Jonathan


On 6 February 2018 at 13:21, Jonathan Riddell  wrote:
> It's not clear what the status of Calligra 3.1 is.  There's an announce up but
> https://community.kde.org/Calligra
> still says 3.0.1 is stable, repo-metadata says calligra/3.0 is the
> stable branch.
>
> There's a separate calligraplan tar which isn't announed why that
> seems to be separate.
>
> Jonathan

Re: Calligra 3.1 status

[Jonathan Riddell]

On 6 February 2018 at 14:25, Dag  wrote:
> Jonathan Riddell skrev den 2018-02-06 14:52:
>>
>> The calligraplan tar contains translations which conflict with those
>> in the calligra tar
>>
>> calligraplanlibs.mo  calligraplan.mo  calligraplan_scheduler_rcps.mo
>> calligraplan_scheduler_tj.mo  calligraplanwork.mo  krossmoduleplan.mo
>
> Hmmm, cannot find any calligraplan* files in the calligra-3.1.0.tar.xz.
> Can you give me any pointers?

Oh I see I'm using Neon dev edition which builds calligra from Git
which still has Plan there.

>>> There's a separate calligraplan tar which isn't announed why that
>>> seems to be separate.
>
> It was mentioned at release-t...@kde.org:
> https://mail.kde.org/pipermail/release-team/2018-January/010806.html

Oh aye, thanks

Jonathan

Re: KEXI, KDb, KProperty, KReport 3.2.0 ready to translate

[Jonathan Riddell]

The stable branch is still set to 3.1 in repo-metadata

Jonathan

On Tue, 8 Jan 2019 at 09:59, Jaroslaw Staniek  wrote:
>
>
> Dear All,
> I'd like to declare string freeze for 4 projects: KEXI, KDb,
> KProperty, KReport version 3.2.0.
>
> Beta would be announced on Jan 21st.
> Stable is planned for February so there is one month for
> testing messages and translating. There are not too many new strings.
> Translating of docs is not recommended, they need major update.
>
> All the code is in branch 3.2 of repo kexi/kdb/kproperty/kreport.
>
> Technical details:
> 3.2.0 KDb, KProperty, KReport may have new APIs but are backward compatible 
> with 3.1.0.
> KEXI 3.2.0 requires update of KDb, KProperty, KReport to 3.2.0.
>
> --
> regards, Jaroslaw Staniek
>
> KDE:
> : A world-wide network of software engineers, artists, writers, translators
> : and facilitators committed to Free Software development - kde.org
> KEXI:
> : A visual database apps builder - kexi-project.org calligra.org/kexi
>   twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project
> Qt Certified Specialist:
> : linkedin.com/in/jstaniek

Re: KEXI, KDb, KProperty, KReport 3.2.0 ready to translate

[Jonathan Riddell]

It blocks any translations to 3.2 branch as there's nowhere the
translations end up.

In KDE neon we also set our dev-stable builds using the repo-metadata
branches so I'd need to override those to build this forthcoming
release as we do for other beta and pre-beta software.

Jonathan

On Tue, 8 Jan 2019 at 12:03, Jaroslaw Staniek  wrote:
>
>
> Does it block anything on your end? If so we can update. CI already has 
> stable set to 3.2 for example.
> 3.1 branch is for the current stable because nothing from 3.2 is released.
> We have 3.2 earlier because we had to bump minor version due to new APIs.
>
> On Tue, 8 Jan 2019 at 12:44, Jonathan Riddell  wrote:
>>
>> The stable branch is still set to 3.1 in repo-metadata
>>
>> Jonathan
>>
>> On Tue, 8 Jan 2019 at 09:59, Jaroslaw Staniek  wrote:
>> >
>> >
>> > Dear All,
>> > I'd like to declare string freeze for 4 projects: KEXI, KDb,
>> > KProperty, KReport version 3.2.0.
>> >
>> > Beta would be announced on Jan 21st.
>> > Stable is planned for February so there is one month for
>> > testing messages and translating. There are not too many new strings.
>> > Translating of docs is not recommended, they need major update.
>> >
>> > All the code is in branch 3.2 of repo kexi/kdb/kproperty/kreport.
>> >
>> > Technical details:
>> > 3.2.0 KDb, KProperty, KReport may have new APIs but are backward 
>> > compatible with 3.1.0.
>> > KEXI 3.2.0 requires update of KDb, KProperty, KReport to 3.2.0.
>> >
>> > --
>> > regards, Jaroslaw Staniek
>> >
>> > KDE:
>> > : A world-wide network of software engineers, artists, writers, translators
>> > : and facilitators committed to Free Software development - kde.org
>> > KEXI:
>> > : A visual database apps builder - kexi-project.org calligra.org/kexi
>> >   twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project
>> > Qt Certified Specialist:
>> > : 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 - kde.org
> KEXI:
> : A visual database apps builder - kexi-project.org calligra.org/kexi
>   twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project
> Qt Certified Specialist:
> : linkedin.com/in/jstaniek

Re: KEXI, KDb, KProperty, KReport 3.2.0 ready to translate

[Jonathan Riddell]

Yes, that's how Plasma and Applications do it. Not all projects to it
this way, but once a new stable branch is made repo-metadata's stable
branch should be updated to allow translations.

Jonathan

On Tue, 8 Jan 2019 at 12:28, Jaroslaw Staniek  wrote:
>
>
>
> On Tue, 8 Jan 2019 at 13:22, Jonathan Riddell  wrote:
>>
>> It blocks any translations to 3.2 branch as there's nowhere the
>> translations end up.
>>
>> In KDE neon we also set our dev-stable builds using the repo-metadata
>> branches so I'd need to override those to build this forthcoming
>> release as we do for other beta and pre-beta software.
>
>
> Thanks. So is it normal practice to bump repo-metadata version weeks before 
> the .0 release?
>
>>
>> Jonathan
>>
>> On Tue, 8 Jan 2019 at 12:03, Jaroslaw Staniek  wrote:
>> >
>> >
>> > Does it block anything on your end? If so we can update. CI already has 
>> > stable set to 3.2 for example.
>> > 3.1 branch is for the current stable because nothing from 3.2 is released.
>> > We have 3.2 earlier because we had to bump minor version due to new APIs.
>> >
>> > On Tue, 8 Jan 2019 at 12:44, Jonathan Riddell  wrote:
>> >>
>> >> The stable branch is still set to 3.1 in repo-metadata
>> >>
>> >> Jonathan
>> >>
>> >> On Tue, 8 Jan 2019 at 09:59, Jaroslaw Staniek  wrote:
>> >> >
>> >> >
>> >> > Dear All,
>> >> > I'd like to declare string freeze for 4 projects: KEXI, KDb,
>> >> > KProperty, KReport version 3.2.0.
>> >> >
>> >> > Beta would be announced on Jan 21st.
>> >> > Stable is planned for February so there is one month for
>> >> > testing messages and translating. There are not too many new strings.
>> >> > Translating of docs is not recommended, they need major update.
>> >> >
>> >> > All the code is in branch 3.2 of repo kexi/kdb/kproperty/kreport.
>> >> >
>> >> > Technical details:
>> >> > 3.2.0 KDb, KProperty, KReport may have new APIs but are backward 
>> >> > compatible with 3.1.0.
>> >> > KEXI 3.2.0 requires update of KDb, KProperty, KReport to 3.2.0.
>> >> >
>> >> > --
>> >> > regards, Jaroslaw Staniek
>> >> >
>> >> > KDE:
>> >> > : A world-wide network of software engineers, artists, writers, 
>> >> > translators
>> >> > : and facilitators committed to Free Software development - kde.org
>> >> > KEXI:
>> >> > : A visual database apps builder - kexi-project.org calligra.org/kexi
>> >> >   twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project
>> >> > Qt Certified Specialist:
>> >> > : 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 - kde.org
>> > KEXI:
>> > : A visual database apps builder - kexi-project.org calligra.org/kexi
>> >   twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project
>> > Qt Certified Specialist:
>> > : 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 - kde.org
> KEXI:
> : A visual database apps builder - kexi-project.org calligra.org/kexi
>   twitter.com/kexi_project facebook.com/kexi.project t.me/kexi_project
> Qt Certified Specialist:
> : linkedin.com/in/jstaniek

Re: calligraplan release

[Jonathan Riddell]

Will you be making a stable branch and at what point will you do that?

Jonathan


On Tue, 29 Oct 2019 at 07:51,  wrote:

> Hi,
> release planned of calligraplan 3.2.0: Thursday, 2019-11-07.
>
> String- and featurefreeze in effect from: Thursday, 2019-10-31.
>
> Beta release (3.1.90) on friday, 2019-11-01.
>
> ---
> Cheers,
> Dag
>

stable branch

[Jonathan Riddell]

The stable branch for calligra is still set to calligra/3.1 but the current
release series is 3.2 from master.  Can this be fixed?

Jonathan

karbon pdf filter

[Jonathan Riddell]

I'm getting a build failure on Karbon's PDF filter since I upgraded KDE
neon to the latest poppler.  Would anyone know if there's a fix for this?

https://build.neon.kde.org/job/focal_unstable_extras_calligra_bin_amd64/172/console

*08:14:42* [ 70%] Building CXX object
filters/libmsooxml/CMakeFiles/komsooxml.dir/MsooXmlThemesReader.cpp.o*08:14:42*
/workspace/build/filters/karbon/pdf/PdfImport.cpp: In member function
‘virtual KoFilter::ConversionStatus PdfImport::convert(const
QByteArray&, const QByteArray&)’:*08:14:42*
/workspace/build/filters/karbon/pdf/PdfImport.cpp:58:48: error: no
matching function for call to ‘PDFDoc::PDFDoc(GooString*&, int, int,
int)’



*Jonathan*

KDB release needed

[Jonathan Riddell]

*KDB no longer compiles with current Qt.  The master branch does
compile.  Can we get a release of KDB?  I can make one if that works
OK.*


*15:47:47* /workspace/build/src/KDb.cpp: In function ‘QString
KDb::escapeBLOB(const QByteArray&, KDb::BLOBEscapingType)’:*15:47:47*
/workspace/build/src/KDb.cpp:1638:37: error: use of deleted function
‘QCharRef& QCharRef::operator=(char)’*15:47:47*  1638 |
 str[new_length++] = '\\';



*Jonathan*

Re: KDB release needed

[Jonathan Riddell]

Similarly kreport doesn't compile with current libmarble for the maps
plugins which makes Kexi unhappy to compile.  Can we get (or can I make) a
new release of this?

Jonathan


On Thu, 25 Aug 2022 at 14:01, Jonathan Riddell  wrote:

>
> *KDB no longer compiles with current Qt.  The master branch does compile.  
> Can we get a release of KDB?  I can make one if that works OK.*
>
>
> *15:47:47* /workspace/build/src/KDb.cpp: In function ‘QString 
> KDb::escapeBLOB(const QByteArray&, KDb::BLOBEscapingType)’:*15:47:47* 
> /workspace/build/src/KDb.cpp:1638:37: error: use of deleted function 
> ‘QCharRef& QCharRef::operator=(char)’*15:47:47*  1638 | 
> str[new_length++] = '\\';
>
>
>
> *Jonathan*
>
>
>

Re: libetonyek, odfgen etc packages for ubuntu?

[Jonathan Riddell]

On Sun, Jun 29, 2014 at 02:14:40PM +0200, René J.V. Bertin wrote:
> Hello,
> 
> It's been a while, so I thought I'd do a git pull and rebuild my Calligra 
> packages. I've migrated to Kubuntu 14.04 since the last time, but I have the 
> impression that Calligra itself now requires newer versions of the odfgen, 
> etonyek (etc) packages than those I built when I first started evaluation 2.9 
> .
> So my question is: is there a ppa where I can find the most importance of 
> those dependencies, or another source of prebuilt packages?

Calligra 2.8 is in the ubuntu archive, no PPA needed, including all the latest 
dependencies.  Updates in the kubuntu-ppa/ppa updates PPA

Let me know if you have any problems.

Jonathan

___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel

Re: libetonyek, odfgen etc packages for ubuntu?

[Jonathan Riddell]

On Sun, Jun 29, 2014 at 03:36:25PM +0200, René J.V. Bertin wrote:
> On Sunday June 29 2014 14:14:25 Jonathan Riddell wrote:
> 
> 
> >Calligra 2.8 is in the ubuntu archive, no PPA needed, including all the 
> >latest dependencies.  Updates in the kubuntu-ppa/ppa updates PPA
> 
> Last time I checked 2.8 wasn't yet in the official repos, and since I had to 
> start building my own version anyway I went with 2.9. And that's what I was 
> talking about, packages require by the Calligra development branch ...

Let me know what's missing and I'll get it updated.

Jonathan
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel

Kubuntu patches

[Jonathan Riddell]

Congratulations on the latest 2.8 release.  Krita especially is looking very 
shiny.

We have some patches in the Kubuntu packaging I'd like reviewed and preferably 
upstreamed

A fix for arm builds
 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/calligra/view/head:/debian/patches/fix_implicit_coercion.diff

We turn on Calligra Active and package it, presumably you don't want that 
upstream but do shout if you don't want it packaged downstream
 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/calligra/view/head:/debian/patches/kubuntu_build_calligraactive.diff

This is needed to install kritasketch plugins in a directory where it will be 
found, but isn't suitable as-is upstream
 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/calligra/view/head:/debian/patches/kubuntu_krita_plugin_directory.diff

We set the kritasketch library to be versioned in line with all the other 
libraries
 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/calligra/view/head:/debian/patches/kubuntu_version_kritasketchlib.diff

Don't open text files in Calligra Words, as Kate is more suited to the job
This might need a separate .desktop file for calligra words text mimetype with 
a lower priority
 http://launchpad.net/bugs/998324
 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/calligra/view/head:/debian/patches/kubuntu_words_mimetype.diff

Jonathan
___
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel