This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/xsnrg/indi-3rdparty-bleeding/
This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/xsnrg/indi-3rdparty-bleeding/
[root@sword ~]# dnf install indi-*
上次元数据过期检查:0:12:27 前,执行于 2020年09月16日 星期三 11时29分56秒。
软件包 indi-qhy-1.8.7.git-20200914235110.fc32.x86_64 已安装。
错误:
问题 1: conflicting requests
- nothing provides libSVBCameraSDK.so(libSVBCameraSDK)(64bit) needed by indi-sv305-1.8.7.git-20200909143303.fc32.x86_64
- nothing provides libSVBCameraSDK.so(libSVBCameraSDK)(64bit) needed by indi-sv305-1.8.7.git-20200910124244.fc32.x86_64
- nothing provides libSVBCameraSDK.so(libSVBCameraSDK)(64bit) needed by indi-sv305-1.8.7.git-20200911212211.fc32.x86_64
- nothing provides libSVBCameraSDK.so(libSVBCameraSDK)(64bit) needed by indi-sv305-1.8.7.git-20200913134926.fc32.x86_64
- nothing provides libSVBCameraSDK.so(libSVBCameraSDK)(64bit) needed by indi-sv305-1.8.7.git-20200914211628.fc32.x86_64
问题 2: conflicting requests
- nothing provides libfirmata.so()(64bit) needed by indi-duino-1.8.7.git-20200909144059.fc32.x86_64
- nothing provides libfirmata.so()(64bit) needed by indi-duino-1.8.7.git-20200910125017.fc32.x86_64
- nothing provides libfirmata.so()(64bit) needed by indi-duino-1.8.7.git-20200911212916.fc32.x86_64
- nothing provides libfirmata.so()(64bit) needed by indi-duino-1.8.7.git-20200913135703.fc32.x86_64
- nothing provides libfirmata.so()(64bit) needed by indi-duino-1.8.7.git-20200914212331.fc32.x86_64
(try to add '--skip-broken' to skip uninstallable packages)
indi-duino and indi-sv305 are fail to install due to unsatisfied dependents.
Thank you, I will look into this.
sv305 is fixed. libfirmata is provided as a .a library though, not a shared .so, so I need to look into this further.
Hi, I found that libqhy
doesn’t install *.rules file. Could you add it to libqhy
?
I found that qhyccd.rules is installed in /lib/udev/rules.d
instead of /etc/udev/rules.d
. Sorry for this noise.
Hi, could you add the indilib driver for playerone?
Thank you!
Hi, is it possible to add aarch64 as a supported architecture?
Hello. I’m trying to use my SV305M Pro with INDI via this repository, but it appears that the build for its driver is failing. From the logs it appears because the COPR is trying to build indi-sv305
, but the directory in the original repo was at some point renamed to indi-svbony
(EDIT: may not be the case as your fork has it as indi-sv305). Would it be possible to fix this?
Thanks!
I was able to get indi-svbony (replaces indi-sv305) to build by changing the spec file to the one in the indi-3rdparty repo (indi-svbony/indi-svbony.spec). The same thing needs to be done for libsvbony (replaces libsv305).
I am unable to connect to an SV305M Pro via kstars. The platform and USB are able to connect via AstroDMX so I believe it is a driver issue. I have just done an upgrade via the repositories, below are installed packages. I could be missing a package or a cofniguration parameter. The system should have no remaining FC kstars packages installed. Thanks in advance for your help.
stellarsolver-2.4.git-20230201164833.fc37.x86_64
indi-libs-2.0.1.git-20230330071043.fc37.x86_64
indi-2.0.1.git-20230330071043.fc37.x86_64
kstars-debugsource-3.6.4.git-20230331180850.fc37.x86_64
libahp-gt-2.0.1.git-20230331182444.fc37.x86_64
indi-eqmod-2.0.1.git-20230331183843.fc37.x86_64
kstars-debuginfo-3.6.4.git-20230331180850.fc37.x86_64
kstars-3.6.4.git-20230331180850.fc37.x86_64
indi-static-2.0.1.git-20230330071043.fc37.x86_64
libsvbony-2.0.1.git-20230331182656.fc37.x86_64
This sounds like it may be a driver issue or a configuration issue, but not a build issue? I would suggest opening a discussion here: https://indilib.org/forum/clients.html – this is the primary place where discussions of this nature take place. The board here is mostly just issues with the install of packages. If you can, attach a log file when you open a thread. It will help us see what is going on.
Thank you.
I saw your name in the copr page and was trying to reach out. Additionally I saw that you reported you were able build the driver by changing / adding a link to the new / updated name.
I do not have a good understanding of the git source, the contributors, the update process, or the build process. If you have time and can provide pointers on how to keep this going it would be helpful.
Thanks again, Dan
There is a reference in the build documentation to an indi-svbony package. There is no such package in the repositories. Is it as simple as there is a build issue with creating this package?
I’m getting this same glitch
sudo dnf install indi-*
Last metadata expiration check: 0:11:30 ago on Tue 25 Apr 2023 10:30:47 +07.
Error:
Problem: conflicting requests
- nothing provides libfirmata.so()(64bit) needed by indi-duino-2.0.2.git-20230412030803.fc37.x86_64
- nothing provides libfirmata.so()(64bit) needed by indi-duino-2.0.2.git-20230413175522.fc37.x86_64
- nothing provides libfirmata.so()(64bit) needed by indi-duino-2.0.2.git-20230414101827.fc37.x86_64
- nothing provides libfirmata.so()(64bit) needed by indi-duino-2.0.2.git-20230419133201.fc37.x86_64
(try to add ‘–skip-broken’ to skip uninstallable packages)