+1 to create a kdepim specific PPA for the use case 2
--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
Also posted to: https://phabricator.kde.org/T5840#90170
I would like to suggest a slight change in plan for shipping these
updates based on 2 usage cases:
* Case 1 - A user or organisation who wants to update to PIM 16.12.3,
who is happy to add the backports ppa, and is happy to receive further
u
Good. Yes, those packages *should* be removed.
As you can see, they are being replaced by new packages of the same name
but with 'abi1'. Technical reason for that is that KDE removed some
function from those libraries, so they are now renamed so things build
and depend on the new version, and don
I tried dist-upgrade when I saw the "broken" state in aptitude but
can't exactly remember the initial solution, but remember being
daunted by the REMOVED list (before inquiring this list).
This is what I get now:
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading
Thank you for the feedback.
As per the instructions on the website, could you please try with:
sudo apt-get dist-upgrade
or
sudo apt full-upgrade
The output I would expect, including intended package removals, is shown
in the paste below.
http://paste.ubuntu.com/24425524/
However, on your ap
Hi,
I've tried the upgrade but fail to understand the dependancy circle
I'm encountering.
Disclaimer:I'm not a packaging expert!
aptitude suggests to remove 7 packages, of which knotes is one. This
is because knotes has both version 16.04.3 and 16.12.3 of kdepim-doc
in the breaks and replaces dep
