Bug 381628 - Routine package breakage between kdepim/akonadi packages due to ABI
Summary: Routine package breakage between kdepim/akonadi packages due to ABI
Status: RESOLVED WORKSFORME
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-25 02:42 UTC by Allan Sandfeld
Modified: 2022-12-06 05:20 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Allan Sandfeld 2017-06-25 02:42:31 UTC
Akonadi ABI breaks every single day between packages from different repos. Please keep ABI stable or package everything under the same version number. Having KMail be unlauncable 6 out of 7 days of the week in "stable" KDE Neon is not professional.

Feel free to redirect the bug to a more correct place if it is KDE Neon that are not following the correct procedures.
Comment 1 Christoph Feck 2017-06-26 12:29:33 UTC
All KDEPIM packages must be installed from the same version; there is no ABI compatibility guarantee yet.

For neon, this means all KDEPIM packages need to be recompiled (in correct dependency order) and released together. Current list of KDEPIM packages:

akonadi
akonadi-calendar
akonadi-calendar-tools
akonadi-contacts
akonadi-import-wizard
akonadi-mime
akonadi-notes
akonadi-search
akonadiconsole
akregator
blogilo
calendarsupport
eventviews
grantlee-editor
grantleetheme
incidenceeditor
kaddressbook
kalarm
kalarmcal
kblog
kcalcore
kcalutils
kcontacts
kdav
kdepim-addons
kdepim-apps-libs
kdepim-runtime
kholidays
kidentitymanagement
kimap
kldap
kleopatra
kmail
kmail-account-wizard
kmailtransport
kmbox
kmime
knotes
kontact
kontactinterface
korganizer
kpimtextedit
ktnef
libgravatar
libkdepim
libkleo
libksieve
mailcommon
mailimporter
mbox-importer
messagelib
pim-data-exporter
pim-sieve-editor
pimcommon
syndication
Comment 2 Jonathan Riddell 2017-06-26 16:29:25 UTC
Note that stable Neon is Developer Edition Stable Branches which means branches for bugfix releases, it doesn't necessarily mean it's stable to use as a developer edition is for developers to test from.  It's badly named and I'd like to find another name.
Comment 3 Allan Sandfeld 2017-06-27 07:54:33 UTC
I think all the packages probably are all recompiled on the same date (though maybe not in the right order), what is certainly missing are dependencies on exact versions between all of them so they can only migrate into the repo and be upgraded together. Some packages are specific-version tied, but not all.
Comment 4 Justin Zobel 2022-11-06 09:25:16 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-11-21 05:14:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-12-06 05:20:49 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!