Erwan David ha scritto:
Le 08/27/18 à 22:46, Luigi Toscano a écrit :Erwan David ha scritto:Le 08/27/18 à 21:51, Luigi Toscano a écrit :yaros ha scritto:Dnia poniedziałek, 27 sierpnia 2018 21:25:21 CEST Erwan David pisze:Since latest upgrade, krunner does not find anything outside the latest documents (and cannot execute command lines), sametime system tray cannot start anymore (and this on 2 different machines) Do someone have a hint on what happens ? (or is there a workaround) ?Look at the topic "[Debian/buster] Problems after Upgrade 4:5.13.1-1 to 4:5.13.4-1" And https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907262Namely this email: https://lists.debian.org/debian-kde/2018/08/msg00030.htmlThanks. So what would be the safest way to get only the needed packages from unstable and not keep getting them from unstable in the future ?Discussed in the same thread: https://lists.debian.org/debian-kde/2018/08/msg00032.htmlMy past tries whith this kind of commands lead to always using unstable after such an install. I do not want to run unstable if avoidable.
Then disable the unstable repository immediately after the upgrade.There are no other solutions: you need to install those packages, and unless you want to download each single deb file, the sequence of adding the unstable repositories, upgrading those packaging, removing the unstable repositories, is the only way.
Moreover, even if you keep unstable with a low-priority, one the Frameworks 5.49 packages land in testing, everything will continue from testing as before.
Ciao -- Luigi