David James replied to the topic 'Ubuntu indi-full dependency hell' in the forum. 1 month ago

How can I use a 64bit OS on a computer that only supports 32bit OSes? I've got an old Dell Mini9 Netbook that I can strap to the mount it's so small, thus much reducing cable clutter and tangling. With it on the mount I can connect to it from other computers.

The "issue" is not that I'm using a 32bit OS but rather that the control file for the i386 package has a dependency it shouldn't have and which that for amd64 doesn't have. I got installed with a --force-depends flag to get all the other stuff then I let apt "fix" the situation by removing indi-toupcam (and with it the meta-package indi-full) since I don't actually need it. If I actually needed it I'd have had to edit the control file and repackage the .deb.

Read More...

David James replied to the topic 'Ubuntu indi-full dependency hell' in the forum. 1 month ago

Uh, no, the issue with indi-toupcam (and therefore indi-full) having conflicting dependencies remains. After purging everything and re-adding the PPA, it still happens:

sudo apt-get install libindi1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
indi-bin libindi-data
The following NEW packages will be installed:
indi-bin libindi-data libindi1
0 upgraded, 3 newly installed, 0 to remove and 370 not upgraded.
Need to get 1298 kB of archives.
After this operation, 6453 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 ppa.launchpad.net/mutlaqja/ppa/ubuntu cosmic/main i386 libindi-data all 1.7.9~201907021820~ubuntu18.10.1 [9532 B]
Get:2 ppa.launchpad.net/mutlaqja/ppa/ubuntu cosmic/main i386 libindi1 i386 1.7.6~201812191813~ubuntu18.10.1 [327 kB]
Get:3 ppa.launchpad.net/mutlaqja/ppa/ubuntu cosmic/main i386 indi-bin i386 1.7.6~201812191813~ubuntu18.10.1 [961 kB]
Fetched 1298 kB in 2s (566 kB/s)
Selecting previously unselected package libindi-data.
(Reading database ... 281498 files and directories currently installed.)
Preparing to unpack .../libindi-data_1.7.9~201907021820~ubuntu18.10.1_all.deb ...
Unpacking libindi-data (1.7.9~201907021820~ubuntu18.10.1) ...
Selecting previously unselected package libindi1:i386.
Preparing to unpack .../libindi1_1.7.6~201812191813~ubuntu18.10.1_i386.deb ...
Unpacking libindi1:i386 (1.7.6~201812191813~ubuntu18.10.1) ...
Selecting previously unselected package indi-bin.
Preparing to unpack .../indi-bin_1.7.6~201812191813~ubuntu18.10.1_i386.deb ...
Unpacking indi-bin (1.7.6~201812191813~ubuntu18.10.1) ...
Setting up libindi-data (1.7.9~201907021820~ubuntu18.10.1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...
Setting up indi-bin (1.7.6~201812191813~ubuntu18.10.1) ...
Setting up libindi1:i386 (1.7.6~201812191813~ubuntu18.10.1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...


As you can see, the libindi1 has come from the PPA repo. Continuing on:

sudo apt-get install indi-toupcam
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-toupcam : Depends: libindidriver1 (>= 1.7.4+dfsg) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.



Here are screengrabs from the Muon package manager: <strong>it's unequivocal and without any possibility of doubt</strong>: indi-toupcam has dependencies on libindi1 and libindidriver1 but the libindi1 package has a conflicts flag against libindidriver1.

Lifting indi-toupcam's dependency on libindidriver1 should fix it.

Read More...

David James created a new topic ' Ubuntu indi-full dependency hell' in the forum. 2 months ago

Using an Ubuntu-based OS, following the instructions on the Ubuntu page for installing the Stable version we get this:

sudo apt-get install indi-full
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-full : Depends: indi-asi but it is not going to be installed
Depends: indi-toupcam but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


So let's see what the issues are, starting with indi-asi (which I actually need as I have an ASI camera):

sudo apt-get install indi-asi
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-asi : Depends: asi-common but it is not installable
E: Unable to correct problems, you have held broken packages.


And that leads to:

sudo apt-get install asi-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package asi-common is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'asi-common' has no installation candidate


Well, that's not going to be installed, then. How about indi-toupcam?

sudo apt-get install indi-toupcam
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-toupcam : Depends: libindidriver1 (>= 1.7.4+dfsg) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


Leading to:

sudo apt-get install libindidriver1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
libindidriver1
0 upgraded, 1 newly installed, 0 to remove and 370 not upgraded.
Need to get 0 B/287 kB of archives.
After this operation, 1042 kB of additional disk space will be used.
Selecting previously unselected package libindidriver1:i386.
(Reading database ... 281507 files and directories currently installed.)
Preparing to unpack .../libindidriver1_1.7.4+dfsg-1_i386.deb ...
Unpacking libindidriver1:i386 (1.7.4+dfsg-1) ...
Setting up libindidriver1:i386 (1.7.4+dfsg-1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...


So... that installed despite the earlier warning that it wouldn't. Let's try indi-toupcam again:

sudo apt-get install indi-toupcam
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-toupcam : Depends: libindi1 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


Ok, now let's try libindi1:

sudo apt-get install libindi1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
indi-bin
The following packages will be REMOVED:
libindidriver1
The following NEW packages will be installed:
indi-bin libindi1
0 upgraded, 2 newly installed, 1 to remove and 370 not upgraded.
Need to get 0 B/1288 kB of archives.
After this operation, 5367 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 281511 files and directories currently installed.)
Removing libindidriver1:i386 (1.7.4+dfsg-1) ...
Selecting previously unselected package libindi1:i386.
(Reading database ... 281507 files and directories currently installed.)
Preparing to unpack .../libindi1_1.7.6~201812191813~ubuntu18.10.1_i386.deb ...
Unpacking libindi1:i386 (1.7.6~201812191813~ubuntu18.10.1) ...
Selecting previously unselected package indi-bin.
Preparing to unpack .../indi-bin_1.7.6~201812191813~ubuntu18.10.1_i386.deb ...
Unpacking indi-bin (1.7.6~201812191813~ubuntu18.10.1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...
Setting up indi-bin (1.7.6~201812191813~ubuntu18.10.1) ...
Setting up libindi1:i386 (1.7.6~201812191813~ubuntu18.10.1) ...
Processing triggers for libc-bin (2.28-0ubuntu1) ...


So it just finished removing something it installed just before. Back to indi-toupcam again:

sudo apt-get install indi-toupcam
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
indi-toupcam : Depends: libindidriver1 (>= 1.7.4+dfsg) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.


And libindidriver1 again:

sudo apt-get install libindidriver1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
indi-bin libindi1
The following NEW packages will be installed:
libindidriver1
0 upgraded, 1 newly installed, 2 to remove and 370 not upgraded.
Need to get 0 B/287 kB of archives.
After this operation, 5367 kB disk space will be freed.
Do you want to continue? [Y/n]


So basically there's a conflict between libindi1 and libindidriver1.

If I go to the Nightly Builds, I can deal with the indi-asi/asi-common issue as asi-common exists there, but the indi-toupcam dependency on conflicting packages libindi1 and libindidriver1 still exists.

Read More...

David James created a new topic ' OpenWRT and INDI' in the forum. 3 months ago

Would it be possible to use a router equipped with a USB port running on OpenWRT to run an instance of INDI server from which the mount can be controlled remotely over either ethernet or wifi?

I happen to have bought such a router (still on its way) for another purpose but won't be needing it for that anymore, so it occurred to me I might be able to take advantage of it to reduce cable clutter a bit and control my mount from a bit further away.

Someone has definitely tried this in the past as they posted a page on their website about it, but the link has gone dead:
sites.google.com/site/picgoto/indi-openwrt
The archived version - from 2010 - suggests they had packaged indi-server 0.5 as an .ipk
web.archive.org/web/20101030080708/https...picgoto/indi-openwrt

Has anyone else tried this? I imagine an OpenWRT build environment would be needed to compile the INDI packages for installation, which is what I'm going to be looking into next.

Read More...