libindi0 conflicts with indi

[noisymime]

TEST CASE:
1. use jaunty
2. install kstars
3. upgrade to karmic using "sed -i s/jaunty/karmic/ /etc/apt/sources.list ; apt-get update ;apt-get dist-upgrade"
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.

[MaxNegro (maxnegro)]

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>

[sirald66 (sirald66)]

CONFIRM

My install of Vuze/Azureus 4 from PPA onto Jaunty mentioned links to kstars, which is now broken; unable to fix broken package.

At 90 days now.

[ersntiersntien (iresntiresnt-deactivatedaccount)]

Confirm. Can someone *please* fix this?

[Aaron Turrall (aaron-turrall-deactivatedaccount)]

There is a workaround, which is to stop the indi server, then dpkg -r indi, then sudo apt-get install libindi0

this worked for me

but why there are two packages that have the same program but as a different name is beyond me

[medic-ben (benekortuem)]

worked for me, too!

Thanks!

[Michael Vogt (mvo)]

kstars switched its dependency from indi to libindo between jaunty to karmic. This is why its now a more common error.

[noisymime (josh-noisymime)]

libindi0 needs to be set to conflict and replace indi otherwise these upgrade problems are going to keep occurring. Any fresh install of kstars will go through OK, but anyone moving from 9.04 -> 9.10 with kstars installed will have a problem.

[Martin Pitt (pitti)]

I'm not quite sure about the effect of adding a Conflicts:. Wouldn't that mean that on dist-upgrade, the "indi" package would be automatically removed? That seems a bit undesirable to me?

Also, a file like "/usr/bin/indi-server" does _not_ belong into a library package like libindi0. This breaks parallel installability of different SONAME packages.

IMHO a better fix would be to drop indi-server from libindi0?

[noisymime (josh-noisymime)]

I think removing indi completely is exactly what is needed. My understanding is that its functionality is all provided by libindi now.

As for the fact that it provides binaries to /usr/bin, that is a worry. There's been an open bug on it for a while: https://bugs.launchpad.net/ubuntu/+source/libindi/+bug/333301
From what I can see though, this is something that will have to be taken upstream as the files in /usr/bin are part of the original libindi source.

It *might* be possible to retain 2 packages, libindi0 for the libraries and indi for the executables, but looking at the current source layout, this would be quite a change.

[Martin Pitt (pitti)]

noisymime [2009-11-06 1:16 -0000]:
> It *might* be possible to retain 2 packages, libindi0 for the libraries
> and indi for the executables, but looking at the current source layout,
> this would be quite a change.

Nevertheless, it sounds necessary (at least for lucid). Right now it
is utterly broken.

[Martin Pitt (pitti)]

I rejected the upload for now, since it doesn't seem clear at all how this should be handled on updates.

[sirald66 (sirald66)]

UPDATE ?

[Jasem Mutlaq (mutlaqja)]

I splitted libindi into three packages (libindi0 , libindi0-dev, and indi0). indi0 installs the executables such as the server and the drivers while libindi0 is kept for libraries only. I also updated it to the latest upstream version which fixes the drivers loading with KStars.

This is my first package upgrade contribution, is that all, or do I need to do something else?

[Jasem Mutlaq (mutlaqja)]

Actually, I found more issues and uploaded a new package to my PPA here: https://launchpad.net/~mutlaqja/+archive/ppa

[Jonathan Riddell (jr)]

Thanks for looking at this Jasem, it's been neglected for too long.

Your update seems to start with the current lucid package. For maverick please start with the current maverick package.

You split out the binaries into indi0 and make that depend on libindi0. Actually I think the dependency is the other way around, the binaries are drivers and libindi0 uses them, so libindi0 should depend on indi0 (and I'd rename indi0 to just indi, it's not versioned).

We still have the source package indi for some reason, that should be removed.

[Jonathan Riddell (jr)]

Also your change needs to add the appropriate replaces/conflicts for the moved files

[Jasem Mutlaq (mutlaqja)]

Thanks Jonathan for the heads up! I made all the changes and uploaded a new package to my PPA. Can you please include that in Maverick now? Also, please remove the old obsolete indi package (0.5) as it conflicts with the new package.

[Jasem Mutlaq (mutlaqja)]

This is a link to the offending package that needs to be completely removed from Maverick: https://launchpad.net/ubuntu/maverick/+package/indi

[Jonathan Riddell (jr)]

Something strange going on with the packaging in your PPA there.

If I
dget https://edge.launchpad.net/~mutlaqja/+archive/ppa/+files/libindi_0.6.2-0ubuntu2.dsc
dpkg-source -x libindi_0.6.2-0ubuntu2.dsc

I get dpkg-source: error: File ./libindi_0.6.2.orig.tar.gz has size 405738 instead of expected 404382

If I uncompress libindi_0.6.2.orig.tar.gz manually and apply the diff the files in debian/ seem to have their contents duplicated

Other than that libindi0-dev should be libindi-dev, I don't see any point in adding a version number in there

Package: indi should conflict/replace old libindi0

[Jonathan Riddell (jr)]

The old indi source package is still needed to make libsbigudrv. It would be nice if upstream could release a source package for libsbigudrv, currently there is only a binary package released by upstream.

[Jasem Mutlaq (mutlaqja)]

I will prepare a new upstream release in about 10 days when I get back home as I'm currently on vacation and can't do that now. I'll also update the PPA package and insure no conflicts come up.

[Jasem Mutlaq (mutlaqja)]

Ok, I updated my PPA, please check it out. Regarding libsbigudrv, there is no source package, only the binaries as released by SBIG. At any rate, libsbigudrv never depended on INDI.

[Jasem Mutlaq (mutlaqja)]

Any updates? Will this be incorporated into Maverick release?