On Sunday 24 of August 2014 02:41:32 ant wrote:
> I didn't get any answers to this (see below)...
> Is that because:
> 1 I didn't make myself clear?
> 2 Nobody knows?
> 3 I'm trying to do something so stupid it should be obvious to me?
>
> cheers
>
> ant
>
> ------------------------------- previous message  ---------------
> I need to reinstall gcc, but when I try, I get this:
> (Trinity 3.5.13.2   /etc/debian_version is jessie/sid)
>
> -------------------------
> />aptitude install gcc
> The following NEW packages will be installed:
>   gcc-4.9{a} libasan1{a} libatomic1{a} libcilkrts5{a} libgcc-4.9-dev{a}
> liblsan0{a} libtsan0{a} libubsan0{a}
> The following packages will be upgraded:
>   binutils gcc
> 2 packages upgraded, 8 newly installed, 0 to remove and 4 not upgraded.
> Need to get 11.3 MB of archives. After unpacking 35.4 MB will be used.
> The following packages have unmet dependencies:
>  kdesktop-trinity : Depends: binutils (< 2.23) but 2.24.51.20140727-1 is to
> be installed.
> The following actions will resolve these dependencies:
>
>      Remove the following packages:
> 1)     kdebase-kio-plugins-trinity
> 2)     kdebase-runtime-data-common-trinity
> 3)     kdebase-trinity
> 4)     kdesktop-trinity
> 5)     kmail-trinity
> 6)     konqueror-nsplugins-trinity
> 7)     konqueror-trinity
> 8)     ksmserver-trinity
>
> ------------------------
>
> I guess if I do this, Trinity will stop working. Is there a fix?
>
> cheers
>
> ant

It is obvious that you have not updated for a long time because from 
separation jessie from wheezy binutils were updated about 6 times.

The package kdesktop-trinity from 3.5.13.2 has a strict dependency on a 
particular version of binutils. You'd have to either rebuild kdebase-trinity 
with each update binutils or rebuild kdebase-trinity with build option 
WITH_KDESKTOP_LOCK_BACKTRACE="OFF" or use a development version R14.

-- 
Slavek