Create Task
Maniphest T5175

Package K3B KF5 for KCI and zesty archive
Closed, ResolvedPublic
Actions

Description

k3b master on kde git: https://cgit.kde.org/k3b.git/log/

  • Move packaging to LP git
  • Add to KCI as a job - http://kci.pangea.pub/job/merger_k3b/
  • Review remaining patches from KDE4 version, and fix or drop
  • Resolve issues with KDE4 applications depending on the old libcddc4 libraries. K3B Kf5 needs the KF5 versions which replace these,
  • Upload to zesty archive
clivej updated the task description. (Show Details)Feb 4 2017, 10:18 PM
clivej triaged this task as Normal priority.Feb 4 2017, 10:20 PM
clivej moved this task from Inbox to Packaging / Devel on the Kubuntu board.
rikmills assigned this task to clivej.Feb 4 2017, 10:27 PM

Still todo - Finish reviewing remaining patches to see if they are relevant and portable to new KF5 version.

At the moment K3B's libkf5cddb dependency is stuck in proposed as it would replace the KDE4 version on which soundkonverter and Audex depend. So an upload of KF5 would need this issue to be resolved. Simplest would be to retire those outdated and unsupported KDE4 apps from the archive.

rikmills updated the task description. (Show Details)Feb 4 2017, 10:29 PM
rikmills updated the task description. (Show Details)Mar 1 2017, 4:00 PM
rikmills updated the task description. (Show Details)
rikmills added a comment.Mar 1 2017, 4:03 PM

Blocking legacy KDE4 apps now taken out of zesty, so k3b and it;s supporting KDE apps libraries will now migrate.

Some of the old patches may still be reviewable, thought the most important such as setting the correct binary name for 'normalize' and unity/KDE quicklists have been re-enabled.

clivej added a comment.Mar 9 2017, 1:23 AM

Can this be marked as resolved?

rikmills added a comment.Mar 11 2017, 8:18 PM
In T5175#83843, @clivej wrote:

Can this be marked as resolved?

It mostly is, but want to try a new snapshot for zesty after a round bugfixs upstream.

rikmills closed this task as Resolved.Mar 22 2017, 7:09 PM

May add another bugfix snapshot from the new stable branch if it seems worth it, but otherwise resolved I think