- User Since
- Apr 12 2015, 12:50 PM (200 w, 6 d)
Thu, Feb 14
Sun, Feb 10
To create a dump by hand this isn't that easy. see sysadmins/ci-tooling/helpers/create-abi-dump.py.
Mon, Feb 4
I'm not a expert in abi-complience-checker, so we need to find out together...
Jan 8 2019
@ltoscana: thx, done E533
created a workboard for the Privacy Sprint: KDE Privacy Sprint
Jan 7 2019
YEAH so far the abi-compatibility-results.yaml for pim and Frameworks, as far as they got update the last days.
So we are surly hitting the end of this and catching up the loosen tails of all of this. I'll focus currently on other stuff, will look at it and fix stuff in a week or so.
Jan 6 2019
Is there any KDE wide calender where this can be added?
Okay finally we have a date and venue:
Jan 4 2019
@kkofler so blogilo is removed from kdepim team, that means like other expressed, that we would not put effort in keeping it running. As we are already exhausted by the amount of application under our umbrella and also blogilo is not really in the center of a pim suite...
On the other side you got blogilo built with a small patch, great. So if you care about blogilo feel welcome to take over mantainership for blogilo!
Than we surely find also solutions how we handle this patch. We simple want to make sure, that software we ship is in a good shape. And exporting symbols for an unmaintained application does not make sense, otherwise kdepim is getting a dumping ground for rotten applications.
If you have any questions regarding, what it means to take over mantainership or anything else feel free to ask. Maybe the best place is our mailinglist: email@example.com
Make the "prepare enviornemt" solution more bullet proof taking comments into account.
Jan 2 2019
About mentioned pim icon (Kontact, KOrganizer Calendar):
- The oxygen icon for Kontact looks like what I have in mind of kontact. It gives me a bundle of pim applications. The breeze one it overlaying each other, so you can only see the email one. that is not clear what it mention here.
- Please give more information where "KOrganizer Calendar" icon is used and is there a difference between the KOrganizer icon and the KOrganzier Calendar Icon? For me the Oxygen lcon looks like an icon, that should be used for "KOrganizer Reminder Daemon", the breeze one looks like the icon for KOrganzier.
Dec 30 2018
Dec 28 2018
the issue is solved sofar diffently by:
R857:dbb3d8d9f37a: Make sure we wait and block until the publishing process is completed.
update patch for new environment.
reapply to new environment.
Dec 25 2018
Create and store abi-compatibility-results.yaml to artifacts.
fix a fex issues with within the patch.
Dec 24 2018
output for one library. For better unterstanding how output looks like:
use better variable names.
Dec 23 2018
I have made sure that kde/pim is now cleanup in terms of the issue of "not runnig ABI", by triggering a rebuilt. So it is a good test if the patch is working.
With more tests I have detected, that builds still use the oldest commit instead of tags commits (fix D17745) .
Dec 20 2018
In the last for l in libraries: loop, we get output for every item in that list, etiher because there are candidates or there are not.
That means the only way to produce no output at all is that libraries list must be empty. We do not remove any entry from that list, so the initial search do not find any matching entry.
And the only way the list can be empty is that the for key, entry in ourArchive.serverManifest.items() don't find any matching entry.
Rework complete ToolingSettings with a Loader class.
Dec 19 2018
Dec 18 2018
get rid of need to use copy.
Dec 14 2018
Dec 13 2018
@bcooksley for akonadi-search we need some special settings for the abi-create step. Where we should store such settings?
okay with merging D17534 CI now successfully builds the abis for the mentioned packages. (I modified the last comment)
Dec 12 2018
I use the ci-docker images to test the create-abi, but I can't reproduce why those are failing:
I now looked at every repository that failed to build successfully a ABI dump
for Pim. Most of them build successful, but a few of them have issues:
I now looked at every repository that failed to build successfully a ABI dump for Frameworks.
As I'm not really deep into the Framworks code, so I'm unsure, if those are real issues or if those Frameworks need special handling.
Please give me any response you have to those issues. (@aacid , @dfaure, @kde-frameworks-devel)
Dec 10 2018
Dec 9 2018
Dec 8 2018
Nov 28 2018
YEAH - the artifacts are now generated. Thaks a lot!
mail to find a date is sent now.