kstars does not support indi

same problem in kubuntu jaunty 4:4.2.2-0ubuntu1 (64bit arch)
The devices menu does not appear in kstars. It worked in previous version.

Problem also confirmed for me. No devices menu available within kstars.

Does kstars perhaps need to depend libindi0 rather than indi? The problem is that libindi0 conflicts with indi:
Unpacking libindi0 (from .../libindi0_0.6-0ubuntu1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libindi0_0.6-0ubuntu1_i386.deb (--unpack):
 trying to overwrite `/usr/bin/indiserver', which is also in package indi
Errors were encountered while processing:
 /var/cache/apt/archives/libindi0_0.6-0ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Here is a debdiff that corrects the problem

Changes:
Adds build depend for libindi-dev
Replaces kstars depend on indi to libindi0

Have confirmed that this results in the Devices menu reappearing in kstars

Does this work in kubuntu also?

How do I implement this correction, I am not familiar with debdiff archives.

Yes, works fine in kubuntu.

If you add the following line to your apt sources the update should come through:
deb http://ppa.launchpad.net/josh-noisymime/ppa/ubuntu jaunty main

Note that you will have to uninstall indi if you've got it installed as it conflicts with libindi0. See bug #364918

noisymime: I tried your package and it seems it's working fine. I hope this may slip into distro, even if libindi0 is in universe...

Uninstalled indi

added in adept:
deb http://ppa.launchpad.net/josh-noisymime/ppa/ubuntu jaunty main

installed kstars and now it has the devices tag correctly

thank you.

I'm a little surprised that this has been targeted for 9.10. The update to fix it in 9.04 is a trivial change to the package and does not require any code patches etc.

Is there a particular reason this can't be added to jaunty updates?

The targeting for 9.10 means that it *should* be done before Karmic is released. It doesn't really mean anything for Jaunty. The problem is, we can't promote libindi0 or indi-dev to Main in Jaunty and we can't make kstars dep on them either. So it looks like we need to figure out a way to make kstars work with indi (0.5) in order to fix this bug in Jaunty.

One possible option would be to put noisymime's package in a ~edubuntu-dev PPA and advertise it on edubuntu.org and the mailing lists. Frankly, I'm not sure how long it would take to make kstars work with indi (0.5) and neither Kubuntu nor Edubuntu really has resources for it. Putting noisymime's know-to-work package in a PPA would be pretty trivial.

Fix committed to Karmic. This fix will get into a Jaunty experimental PPA, but it will not get placed or backported in Jaunty due to not being able to promote the libindi package to main. We have already done this for Karmic. Thanks for the debdiff, as it was utilized in the updated and merged package from Debian.

This bug was fixed in the package kdeedu - 4:4.2.2-1ubuntu1

---------------
kdeedu (4:4.2.2-1ubuntu1) karmic; urgency=low

  * Merge from Debian Unstable

  +++ Changes by Richard A. Johnson

  * Merge debian/changelog

  +++ Changes by Jonathan Thomas

  * Merge everything else, remaining changes:
    - Conflict/Replace on -kde4 packages
    - Build-Depends: cdbs (>= 0.4.52ubuntu7), libgmm-dev,
      libqalculate-dev, libsbigudrv-dev
    - kdeedu not depend on kiten, blinken (in universe), indi (kstars conflict).
    - kturtle description - change to be more reflective of pseudo-logo language
    - remove indi from kdeedu (external package)
    - Drop openbabel, libgsl0-dev and libgps-dev build-deps (they are in universe)
    - Keep python marble bindings
  * Update KUBUNTU-DEBIAN-DIFFERENCES

  +++ Changes by Josh Stewart

  * debian/control:
    - Add libindi-dev to build-depends
    - Update kstars depends, replaced indi with libindi0 (LP: #359517)

kdeedu (4:4.2.2-1) unstable; urgency=low

  * New upstream release:
    - fix kmplot when calculating integrals of functions. (Closes: #442281)
    - kstars, improved usability of the Observing List Wizard. (Closes: #404583)

 -- Jonathan Thomas <email address hidden> Thu, 07 May 2009 22:04:43 -0400

Got a question about the Karmic fix. Why is libsbigudrv-dev a build-dep? If I am not completely mistaken it is created by the old indi 0.5 source package (which should be dropped, btw) and thus unnecessary to compile with indi 0.6 support.

Anyway about jaunty:
The only reasonable option I can think of is getting indi 0.6 into indi 0.5.
0.6 can be, just like 0.5 a monolithic source package, so if we create such a package for 0.6 and do a SRU to supersed 0.5 we could do another SRU to get kstars rebuilt and then kstars from jaunty-updates should have indi support again.
That has two catches:
a) getting 0.6 in a monolithic source is not all too easy (though I think Debian got exactly that)
b) this would be so incredibly against the SRU rules that we probably won't get permission, however since (to my knowledge) kstars is the only user of indi 0.5 in Jaunty, we could argue that there is no regression potential because the only app that uses the lib is actually not compiled it to begin with.

Deploying the fix via an Edubuntu PPA is nice, but certainly not the best solution for this kind of problem IMHO.

I added the ppa as suggested and it breaks the dependencies on the gnome flavored ubuntu 9.04 with this error:

E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
dpkg: dependency problems prevent configuration of kstars:
 kstars depends on libindi0 (>= 0.6); however:
  Package libindi0 is not installed.

Ideas?? I'm quite keen on scope control via kstars! :)

Mike

Hi Mike,

Do you still have package 'indi' installed? Its installed as part of the non-ppa version of kstars however libindi0 conflicts with it, so you'll need to remove it before installing the ppa version.

If you're having problems after that, I suggest removing indi, libindi0 and kstars, refreshing your apt cache and installing kstars again. That should fix everything.

Josh, you totally solved that one I hope I didn't read something wrong. I still cannot get my USB/Serial adapter to connect to a synced/aligned scope in kstars via the wizard.

Perhaps, this is something to document if in fact I didn't misread/skip?

I'll try my other scope/mount (This one's a CGE)

TIA,

Mike

Hi noisymime

I have the problem with
deb http://ppa.launchpad.net/josh-noisymime/ppa/ubuntu jaunty main

When i inserted the line, and i make apt-get update. i get this key error:

GPG error: http://ppa.launchpad.net jaunty Release: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY E5DC24558986EB1A

Sorry i am new with Kubuntu.
I have used in the last years gentoo.

Thanks in advance
Thomas

Hi Thomas

That error is simply stating that the package isn't 'signed' with a known key. It shouldn't cause a problem though and the update/install should still work without a problem.

If you're getting dependency errors, try removing package 'indi' and see if that helps.

-Josh

Hello Josh

Thanks for the answer, but it do not understand. :(

I uninstall indi and kstars.
I do "deb http://ppa.launchpad.net/josh-noisymime/ppa/ubuntu jaunty main" in /etc/apt/sources.list
Now i install kstars ??
When i do this, i have the same problem. No menue "geräte" in kstars.

I think i need the kdeedu_4.2.2-0ubuntu1.debdiff .
How do i use this one ??
"patch kdeedu_4.2.2-0ubuntu1.debdiff "
Does not work !!

My kde is the 4.2.4 version, can i use this file to??

Sorry for my stupid questions, but i'm a little bit confused.

Ubuntu/Kubuntu is different to gentoo than I thought.

Thanks
Thomas

I'm still on 9.04 with Gnome:

sudo aptitude purge indi kstars libindi0

then

sudo aptitude install kstars

Seems to install properly and run kstars. Hopefully indi will talk to my mount now! :)

Its cold out and I'd like to use it to drive the setup remotely from inside the warm house! ;)

I spoke too soon, the devices menu is empty / won't open.

I'm on karmic, and the kstars package still causes this error. So is it really fixed?

OK, it looks like I had indi on my system. Getting rid of it was pretty ugly. apt-get remove wouldn't work because the kstars package and others were broken, fix didn't work because libindi0 gave the error "trying to overwrite '/usr/bin/indiserver'" as above. In the end I was able to do dpkg -r indi and get rid of indi, then these things installed properly. I would say the fact we still have packages stomping on each other (because I am pretty sure I checked indi along with the others in synaptic and that is what brought this on) is kind of a problem.