Sune Vuorela wrote:

If you can track down what exactly causes kdevelop non-installable on
kde desktop, it would be great.
It is meant to be possible to run kde3 apps in kde4.


/Sune


Hi,

this seems to be the essential part of aptitude's output:

#########################################

sudo aptitude install kdevelop
[...]
The following packages are BROKEN:
kdebase-runtime-data-common
The following NEW packages will be installed:
kdebase-bin{a} kdevelop kdevelop-data{a}
0 packages upgraded, 3 newly installed, 0 to remove and 25 not upgraded.
Need to get 0B/12.6MB of archives. After unpacking 37.1MB will be used.
The following packages have unmet dependencies:
kdebase-runtime-data-common: Conflicts: kdebase-bin (< 4:4.0.0-1) but
4:3.5.9.dfsg.1-2+b1 is to be installed.

Resolving dependencies...
The following actions will resolve these dependencies:

Remove the following packages:
kdebase-runtime-data-common
libkonq5-templates

Install the following packages:
kcontrol [4:3.5.9.dfsg.1-2+b1 (unstable, testing, now)]
kdesktop [4:3.5.9.dfsg.1-2+b1 (unstable, testing, now)]
kicker [4:3.5.9.dfsg.1-2+b1 (unstable, testing, now)]

Downgrade the following packages:
kdebase-data [4:4.0.72-1 (experimental, now) -> 4:3.5.9.dfsg.1-2
(unstable, testing)]
kfind [4:4.0.68+svn794641-1 (experimental, now) -> 4:3.5.9.dfsg.1-2+b1
(unstable, testing)]
konqueror [4:4.0.68+svn794641-1 (experimental, now) ->
4:3.5.9.dfsg.1-2+b1 (unstable, testing)]

[...]
#########################################


Hope it helps.

Kind regards,

Felix


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi,

2008 m. May 16 d., Friday, Felix Homann rašė:
> kdebase-runtime-data-common: Conflicts: kdebase-bin (< 4:4.0.0-1) but
> 4:3.5.9.dfsg.1-2+b1 is to be installed.
Force kdebase-bin to the version in experimental (other another aptitude
solution or like below), then processed with kdevelop install.

# aptitude -t experimental install kdebase-bin
# aptitude install kdevelop

--
Modestas Vainius <modestas@vainius.eu>

Modestas Vainius wrote:

Hi,

2008 m. May 16 d., Friday, Felix Homann rašė:

kdebase-runtime-data-common: Conflicts: kdebase-bin (< 4:4.0.0-1) but
4:3.5.9.dfsg.1-2+b1 is to be installed.
Force kdebase-bin to the version in experimental (other another aptitude
solution or like below), then processed with kdevelop install.


OK, then this is the real problem:

The following packages have unmet dependencies:
kdebase-bin: Depends: kdebase-data (= 4:4.0.68+svn794641-1) but
4:4.0.72-1 is installed.


Should be solved when packages are in sync.

Kind regards,

Felix


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

It lets me install both.

The only package I lose is kdeartwork-theme-icon


On 2008-05-16, Felix Homann <fexpop@onlinehome.de> wrote: > 1.1
KDevelop (Show stopper for me!) > > What's really keeping me from using
KDE4 is a result of the package > maintainer's decision not to let KDE3
and KDE4 be installed completely > in parallel. One of the side effects is
that you can't install KDevelop > together with KDE4! For me this means I
can't use KDE4 at the moment! > Other packages will surely suffer from
the very same decision. If you can track down what exactly causes
kdevelop non-installable on kde desktop, it would be great. It is meant to
be possible to run kde3 apps in kde4. /Sune


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

You can use both IF you compile one of them. I had to compile kde3 (using
konstruct) when kde3 was too big of a problem on Sid for an extended period.
I put it on /opt. Kde4 installed on /usr. (Yes, a pity that stuff did not go
into separate subdirectories--I think they do it that way for Ubuntu,
i.e /usr/bin/kde4, /usr/lib/kde4, etc., at least until it is really ready for
SId.)

With one of them off /usr, I can have desktop files in sessions to run the
appropriate startkde. Paths need be set there AND an environment variable
should be set identifying the session (it used to do just that but I now must
add it myself, say in my older kde3 startkde which is not getting overwritten
in upgrades). I then have my bash profile test that and set up appropriate
paths.

Rusty-trusty kde3 apps usually run just fine in kde4 so kdevelop can still be
used. Visa-versa, I can run the new dolphin in kde3, no sweat.

One big reason why it can be problematic keeping both around is that kde3 uses
dcop and kde4 is using dbus services for intertask operations and never the
twain to meet. So ... I have both going. It would be nice (hint-hint) for
kde4 to have a dcop that tests the session env variable and uses dbus. This
bit of compatibility would go a long way.


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org