With some help from folks in #debian-qt-kde on OFTC, I was encouraged to
add testing to my sources.lists and ask aptitude to run through the install
again without compromising on plasma-desktop. Back on my feet again.
On 29 August 2016 at 20:19, Rubin Abdi <ru...@starset.net> wrote:
> Hello. I haphazardly did a dist-upgrade today on my Debian Sid machine
> without paying attention and have fallen into a pit. Is my only option
> right now to wait till the reverent packages have been upgraded and pushed
> to 5.7.4 or 5.8.1?
>
> 20160829-201153 rubin110@lines:~/temp$ sudo aptitude install
> plasma-desktop
> The following NEW packages will be installed:
> accountsservice{a} bluedevil{a} cracklib-runtime{a} fonts-oxygen{a}
> frameworkintegration{a} ieee-data{a} kde-cli-tools{ab}
> kde-cli-tools-data{a} kde-config-gtk-style{a} kde-config-sddm{a} kded5{a}
> kdoctools5{a} kgamma5{a} khelpcenter{a} khotkeys{a}
> khotkeys-data{a} kinfocenter{a} kinit{a} kmenuedit{a} kscreen{a}
> ksysguard{a} ksysguard-data{a} ksysguardd{a} kwrited{a}
> libaccountsservice0{a} libcln6{a} libcrack2{a} libgps22{a}
> libkf5activitiesexperimentalstats1{a} libkf5bluezqt-data{a}
> libkf5bluezqt6{a} libkf5jsembed-data{a} libkf5jsembed5{a}
> libkf5networkmanagerqt6{a} libkf5people-data{a} libkf5people5{a}
> libkf5peoplebackend5{a} libkf5peoplewidgets5{a} libkf5su-bin{a}
> libkf5su-data{a} libkf5su5{a} libkf5sysguard-bin{a}
> libkf5sysguard-data{a} libkf5xmlrpcclient-data{a} libkf5xmlrpcclient5{a}
> libkfontinst5{a} libkfontinstui5{a} libksgrd7{ab} libksignalplotter7{a}
> libkworkspace5-5{a} libplasma-geolocation-interface5{a}
> libpowerdevilcore2{a} libpowerdevilui5{a}
> libprocesscore7{ab} libprocessui7{ab} libpwquality-common{a}
> libpwquality1{a} libqalculate5-data{a} libqalculate5v5{a} libqt5clucene5{a}
> libqt5designer5{a} libqt5designercomponents5{a} libqt5help5{a}
> libtaskmanager5{a} libweather-ion7{a}
> libxcb-record0{a} muon-discover{a} muon-notifier{a} muon-updater{a}
> oxygen-sounds{ab} plasma-desktop plasma-desktop-data{a} plasma-discover{ab}
> plasma-discover-common{ab} plasma-discover-private{a}
> plasma-discover-updater{a} plasma-integration{ab}
> plasma-pa{a} plasma-workspace{a} polkit-kde-agent-1{ab} powerdevil{a}
> powerdevil-data{a} python3-pycurl{a} python3-pyqt5{a} python3-sip{a}
> python3-software-properties{a} qdbus-qt5{a} qml-module-org-kde-bluezqt{a}
> qml-module-org-kde-extensionplugin{a} qml-module-org-kde-kio{a}
> qml-module-org-kde-kwindowsystem{a} qml-module-qt-labs-folderlistmodel{a}
> qml-module-qt-labs-settings{a} qml-module-qtquick-dialogs{a}
> qml-module-qtquick-privatewidgets{a}
> qttools5-dev-tools{a} sni-qt{a} software-properties-common{a}
> software-properties-kde{a} systemsettings{a} user-manager{a}
> 0 packages upgraded, 101 newly installed, 0 to remove and 2 not upgraded.
> Need to get 40.5 MB of archives. After unpacking 173 MB will be used.
> The following packages have unmet dependencies:
> milou : Breaks: plasma-workspace (< 4:5.7) but 4:5.6.5.1-1 is to be
> installed
> kde-cli-tools : Breaks: plasma-desktop (< 4:5.7) but 4:5.6.5-1 is to be
> installed
> Breaks: plasma-workspace (< 4:5.7) but 4:5.6.5.1-1 is to
> be installed
> libprocesscore7 : Breaks: plasma-workspace (< 4:5.7) but 4:5.6.5.1-1 is
> to be installed
> plasma-discover-common : Breaks: plasma-discover-private (< 5.7.0) but
> 5.6.5-1 is to be installed
> Breaks: plasma-discover-updater (< 5.7.0) but
> 5.6.5-1 is to be installed
> plasma-discover : Breaks: plasma-discover-private (< 5.7.0) but 5.6.5-1
> is to be installed
> Breaks: plasma-discover-updater (< 5.7.0) but 5.6.5-1
> is to be installed
> breeze : Breaks: plasma-desktop (< 4:5.7) but 4:5.6.5-1 is to be installed
> kactivitymanagerd : Breaks: plasma-desktop (< 4:5.7) but 4:5.6.5-1 is to
> be installed
> libksgrd7 : Breaks: plasma-workspace (< 4:5.7) but 4:5.6.5.1-1 is to be
> installed
> oxygen-sounds : Breaks: plasma-desktop (< 4:5.7) but 4:5.6.5-1 is to be
> installed
> libkscreenlocker5 : Breaks: plasma-workspace (< 4:5.7) but 4:5.6.5.1-1 is
> to be installed
> plasma-integration : Breaks: plasma-desktop (< 4:5.7) but 4:5.6.5-1 is to
> be installed
> polkit-kde-agent-1 : Breaks: plasma-desktop (< 4:5.7) but 4:5.6.5-1 is to
> be installed
> libprocessui7 : Breaks: plasma-workspace (< 4:5.7) but 4:5.6.5.1-1 is to
> be installed
> The following actions will resolve these dependencies:
>
> Keep the following packages at their current version:
> 1) kinfocenter [Not Installed]
> 2) muon-discover [Not Installed]
> 3) plasma-desktop [Not Installed]
> 4) plasma-discover [Not Installed]
> 5) plasma-discover-common [Not Installed]
> 6) plasma-workspace [Not Installed]
>
> Leave the following dependencies unresolved:
> 7) plasma-desktop-data recommends plasma-workspace
>
> On 27 August 2016 at 15:10, Luigi Toscano <luigi.tosc...@tiscali.it>
> wrote:
>
>> Luigi Toscano ha scritto:
>> > Martin Steigerwald ha scritto:
>> >> Am Samstag, 27. August 2016, 17:15:30 CEST schrieb Luigi Toscano:
>> >>> Maximiliano Curia ha scritto:
>> >>>> plasma-workspace tests were failling in the 5.7.[0-2] releases and we
>> >>>> decided to wait till this gets fixed, this was finally fixed in
>> 5.7.3 (by
>> >>>> moving the failling tests to a non packageable project). By that
>> time 5.8
>> >>>> was announced to be the first lts, so it makes sense to wait for 5.8,
>> >>>> which should be released "real soon now"(tm).
>> >>>
>> >>> As this is no more true, as most of Plasma 5.7.x landed in unstable
>> breaking
>> >>> the remaining 5.6 bits, would be possible to have the missing bits
>> (from a
>> >>> quick glance, plasma-desktop, plasma-workspace and khotkeys for sure)?
>> >>
>> >> I just saw on debian-qt-kde-ml, plasma-workspace 5.7.4 uploaded again
>> after an
>> >> initial reject due to source only upload, so if ftpmasters accept it
>> this
>> >> time, at least this one is coming.
>> >>
>> >
>> > The reject afaik does not depend on the package being source-only; it
>> > introduces new binaries.
>>
>> I stand corrected sorry. The reject was, as you wrote, because it was a
>> source
>> only-upload for a package with new binaries and that should have gone
>> through NEW.
>>
>> >
>> > Maybe a way to solve this is a push to experimental, so that a block of
>> new
>> > packages can "decant" in experimental without breaking the rest of the
>> world.
>> >
>>
>> This is still a valid suggestion.
>>
>> --
>> Luigi
>>
>>
>
>
> --
> Rubin
> ru...@starset.net
>
--
Rubin
ru...@starset.net
