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
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 a
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
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 6
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.
>
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 c
> 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
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 happe
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
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
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?
>
> P
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 re
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/
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
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
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
>
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 84091746c37a80dc907c412d0903
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 kp
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
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
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
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/
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
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 has no stable translations. I think it should be set to use the
3.0 branch? Is that right?
Jonathan
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 b
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_sr
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
>>
>> Th
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,
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
ICalendarExpor
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
ule-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
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
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.m
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
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:
>> >
>&
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
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, 201
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
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
*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.c
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 ma
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
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
>
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/patche
45 matches
Mail list logo
