Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: transition
KDE Pim 17.12 has updated ist API and ABI, that makes it nessasary to bump some ABIs. To track those ABI breakages, we updated the package names to 5abi1. So far most of the packages, that needs to be rebuild are inside KDE Pim itself so only following "external" packages are affected: blogilo digikam kjots libkolab zanshin (calligra, calligraplan) I build all rdepends and came to the conclusion: * kjots and zanshin build nicely with the new KDE Pim * blogilo has fallen out of KDE Pim can't be build anymore -> RM request * libkolab do not build anymore with KDE Pim 17.12 it is dead upstream and not needed anymore for KDE Pim -> RM request [1] * digikam is not ready for KDE Pim 17.12 (see #893515) the mantainer told me in private: " My suggestion is: go ahead with the upload to unstable. I should be able to get digikam uploaded very shortly thereafter." * calligra and calligraplan depdend on the build pacakges, but the featueres that use KDE Pim are disabled, so no need to build them within the transition. This transistion includes/replaces following auto detected transitions: auto-akonadi-calendar auto-akonadi auto-kcalcore auto-kdav auto-kmime auto-kpimtextedit auto-libkf5calendarsupport auto-libkf5gravatar auto-libkf5incidenceeditor auto-libkf5mailcommon auto-libkf5pimcommon These 11 transistions share nearly all rdepdens, that's why I think it is easier to track it in only one transistion and not within 11. But if you belive it is easier to have saperate ones, please tell me. I look at all, and all look correcty so far, but IMO it is not easy keep an overview. After KDE Frameworks 5.44 entered testing successfully, there is no blocker anymore for starting this transition. Please tell me additionally, if I need to request the RMs in advanced or while the transition is going on. hefee [1] https://lists.alioth.debian.org/pipermail/pkg-kolab-devel/2018-March/003733.html Ben file: title = "kdepim"; is_affected = .build-depends ~ /\b(libkf5calendarcore\-dev|libkpimkdav\-dev|libkf5pimtextedit\-dev|libkf5mime\-dev|libkf5calendarsupport\-dev|libkf5gravatar\-dev|libkf5incidenceeditor\-dev|libkf5mailcommon\-dev|libkf5pimcommon\-dev|libkf5akonadi\-dev|libkf5akonadiserver\-dev|libkf5akonadicalendar\-dev)\b/; is_good = .depends ~ /\b(libkf5calendarcore5abi1|libkpimkdav5abi1|libkf5pimtextedit5abi1|libkf5mime5abi1|libkf5calendarsupport5abi1|libkf5gravatar5abi1|libkf5incidenceeditor5abi1|libkf5mailcommon5abi1|libkf5pimcommon5abi1|libkf5akonadicore5abi1|libkf5akonadiprivate5abi1|libkf5akonadiwidgets5abi1|libkf5akonadicalendar5abi1)\b/; is_bad = .depends ~ /\b(libkf5calendarcore5|libkpimkdav5|libkf5pimtextedit5|libkf5mime5|libkf5calendarsupport5|libkf5gravatar5|libkf5incidenceeditor5|libkf5mailcommon5|libkf5pimcommon5|libkf5akonadicore5|libkf5akonadiprivate5|libkf5akonadiwidgets5|libkf5akonadicalendar5)\b/; -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
