circular build dependency between kdebase-workspace and kde4bindings, broken on lpia and hppa

Bug #289402 reported by Matthias Klose
4
Affects Status Importance Assigned to Milestone
kde4bindings (Ubuntu)
Fix Released
High
Unassigned
Intrepid
Fix Released
High
Roderick B. Greening
kdebase-workspace (Ubuntu)
Fix Released
High
Unassigned
Intrepid
Fix Released
High
Roderick B. Greening

Bug Description

Binary package hint: kdebase-workspace

circular build dependency between kdebase-workspace and kde4bindings, broken on lpia and hppa

see the build logs on lpia; package cannot be built without manual intervention

Matthias Klose (doko)
Changed in kdebase-workspace:
importance: Undecided → High
Changed in kde4bindings:
importance: Undecided → High
Revision history for this message
Harald Sitter (apachelogger) wrote :

Needs to be discussed with upstream.
Right now it appears KDE itself has the circular dependency.

Changed in kdebase-workspace:
assignee: nobody → roderick-greening
milestone: none → intrepid-updates
status: New → Triaged
Changed in kde4bindings:
assignee: nobody → roderick-greening
milestone: none → intrepid-updates
status: New → Triaged
Revision history for this message
Roderick B. Greening (roderick-greening) wrote :

Spoke with Simon Edwards. He feels that the issue is in kde4bindings and possibly with the libplasma-dev dep. This dep was probably added for the plasma ruby bits. It's likely that this should not exist in this package.

This is being discussed with the kde4bindings devs.

If it moves, this resolves the circular dep issue. If it does not, then we need to discuss other ways to address.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Using the current information we came up with following options:
1) dump the patches
2) don't build ruby/smoke with plasma bindings (that is assuming there are no other workspace dependencies, which I am not sure about)
3) add the necessary patches to get all the kdebase-workspace deps moved from bindings to workspace (according to upstream changes in KDE trunk)
4) debundle the python stuff from kdebase-workspace into a sepearte source package
5) leave it alone

With the following disadvantages:
1) the seperate examples package would end up empty + user confusing because of disappearing features
2) disappearing features again
3) difficult to do + not very regression-save
4) the python bindings would need a new package and apt-get update doesn't install new packages automagically, so we would have to communicate the need for dist-upgrade, which is kind of difficult considering libplasma is one of the most essential parts of the KDE 4 desktop, not making libplasma depend on teh python bindings would again be disappearing features
5) no LPIA and HPPA builds (although mobile stuff is only getting upstream attention in 4.2 and we still didn't hear of any HPPA KDE users)

Revision history for this message
Jonathan Riddell (jr) wrote :

Fixed upstream in 4.2, libplasms is in kdelibs now.

Revision history for this message
Peter Antoniac (pan1nx) wrote :

What about the intrepid? Are we going to get something soon? Last time when I checked:
https://edge.launchpad.net/ubuntu/+source/kdebase-workspace/4:4.1.2-0ubuntu12/+build/748812
it was still not building for LPIA and HPPA.

Thanks...

Revision history for this message
Peter Antoniac (pan1nx) wrote :

Ok, sorry. My interest was intrepid lpia.

Changed in kde4bindings:
assignee: roderick-greening → nobody
milestone: intrepid-updates → none
status: Triaged → Fix Released
assignee: nobody → roderick-greening
importance: Undecided → High
milestone: none → intrepid-updates
status: New → Triaged
Changed in kdebase-workspace:
assignee: roderick-greening → nobody
milestone: intrepid-updates → none
status: Triaged → Fix Released
assignee: nobody → roderick-greening
importance: Undecided → High
milestone: none → intrepid-updates
status: New → Triaged
Changed in kdebase-workspace (Ubuntu Intrepid):
status: Triaged → Fix Released
Changed in kde4bindings (Ubuntu Intrepid):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.