libindi0 conflicts with indi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libindi (Ubuntu) |
Fix Released
|
Medium
|
Jasem Mutlaq | ||
Karmic |
Won't Fix
|
Medium
|
Jasem Mutlaq |
Bug Description
TEST CASE:
1. use jaunty
2. install kstars
3. upgrade to karmic using "sed -i s/jaunty/karmic/ /etc/apt/
4. watch it fail with a file conflict
5. repeat 1,2
6. enable jaunty-proposed
7 repeat 3
8 verify it works now
Package libindi0 conflicts with package indi as both try to install file /usr/bin/indiserver
I'm not sure of the history behind the 2 packages, but from what I can see libindi0 should to be set to conflict and replace indi. All the functionality within indi seems to be duplicated within libindi0 (Though not vice versa). I'm happy to create a debdiff if that would be helpful?
Perhaps the bug needs to be logged against package indi however, as it appears as though it is not actually required within Jaunty.
Changed in libindi (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in libindi (Ubuntu): | |
assignee: | nobody → Jasem Mutlaq (mutlaqja) |
Changed in libindi (Ubuntu Karmic): | |
assignee: | Michael Vogt (mvo) → Jasem Mutlaq (mutlaqja) |
Changed in libindi (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in libindi (Ubuntu Karmic): | |
status: | Incomplete → Confirmed |
Changed in libindi (Ubuntu Karmic): | |
status: | Confirmed → Won't Fix |
Actually libindi _should_ be required in jaunty, in order to have telescope control support in kstars. At the moment kstars depends on package indi, but those functionalities are currently broken in kstars package.
Probably best strategy should be replace indi with libindi and have again an indi enabled kstars :)
See <a href="https:/ /bugs.launchpad .net/ubuntu/ +source/ kdeedu/ +bug/359517">#359517</a>