Update KEXI master to 3.3
ClosedPublic

Authored by staniek on Jan 21 2019, 9:55 AM.

Diff Detail

Repository
R256 Flatpak packaging for KDE Applications
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
staniek requested review of this revision.Jan 21 2019, 9:55 AM
staniek created this revision.
bcooksley edited reviewers, added: apol; removed: Sysadmin.Jan 23 2019, 5:40 AM
bcooksley added a subscriber: bcooksley.

This looks fine to me, but as the original author Aleix should confirm this is correct.

apol accepted this revision.Jan 27 2019, 4:35 AM
This revision is now accepted and ready to land.Jan 27 2019, 4:35 AM
This revision was automatically updated to reflect the committed changes.

Landed, now how to rebuild it? Can I get rights to click Rebuild?
I may want this in other cases, e.g. when kexi.git is unchanges but when dependencies changed and we want to test things while testers are waiting for binaries. For nightly builds it means one test per 24h I'd assume?

Our Flatpak builds monitor the source repository (in this case the Kexi repository) for changes, so once there has been a change there the build should trigger automatically sometime in the next 24 hours.

Thanks Ben, it's hard to argue with this standard behavior. I am wondering though how to trigger the build in projects like KEXI - there can be weeks of development when changes are in kdb.git only and not in kexi.git. More precisely, how to deal with that without adding artificial commits to kexi.git.

At this time your only way will be to ask in #kde-sysadmin for someone to trigger the build for you manually.

Thanks a lot @apol, it looks promising and clean. I have questions based on my limited knowledge of these json files:

  • kreport, kproperty, kdb modules - can their branch be 3.2 too? They're BC but still using stable dependencies for stable builds would be better
  • the top level "branch" attribute is master, not sure what it means
  • what would be the URL at https://binary-factory.kde.org/ for the stable?

PS I am on vacation this week so may respond with delays :)

apol added a comment.Feb 5 2019, 11:38 PM

Thanks a lot @apol, it looks promising and clean. I have questions based on my limited knowledge of these json files:

  • kreport, kproperty, kdb modules - can their branch be 3.2 too? They're BC but still using stable dependencies for stable builds would be better

done

  • the top level "branch" attribute is master, not sure what it means

changed

https://binary-factory.kde.org/view/Flatpak/job/Kexi_stable_flatpak/

Very good, by chance, where are the artifacts for kexi builds?

staniek added a comment.EditedFeb 20 2019, 12:04 AM

Thanks @bcooksley and @apol

I've reported icons issue https://bugs.kde.org/show_bug.cgi?id=404579 (breeze is the only theme having all icons supported for now but it does not work in flatpak case probably because kexi searches them wrong way)