On Fri, Jan 19, 2024 at 12:00 PM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
On Thu, Jan 18, 2024 at 6:26 PM Rainer Klier <r.klier@namirial.com> wrote:
hi,
Am 18.01.24 um 16:46 schrieb Roger Oberholtzer:
error: Failed dependencies: mono(System.Collections) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.ComponentModel.Primitives) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Console) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Diagnostics.Process) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Linq) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Runtime) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Text.RegularExpressions) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Threading) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Threading.Thread) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Xml.ReaderWriter) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64 mono(System.Xml.XmlSerializer) = 6.0.0.0 is needed by navsolve-cmd-1.2.1-2.x86_64
could it be, that the used software really has an explicite dependency on mono/.net 6.0?
there has to be some file in the ditribution of the used software, where thedependency is configured.
if you find that, maybe you can change it to also accept 6.12.0
I will check that. The package is provided as a .deb. I use alien to make an .rpm, which is what I am installing. If I just have alien create the directory that it will use to make the .rpm, I see that the .spec files is:
Buildroot: /home/roger/source.18.00/Tools_OxTS/NAVsolve_CMD/navsolve-cmd-1.2.1 Name: navsolve-cmd Version: 1.2.1 Release: 2 Summary: NAVsolve Command Line Utility License: see /usr/share/doc/navsolve-cmd/copyright Distribution: Debian Group: Converted/base
%define _rpmdir ../ %define _rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm %define _unpackaged_files_terminate_build 0
%description Used to convert RT and xNAV raw data files into NCOM and CSV files.
(Converted from a deb package by alien version 8.95.6.)
%files "/usr/local/bin/NcomToCsv.exe" "/usr/local/bin/navsolve-cmd" %dir "/usr/local/share/navsolve-cmd_1.2.1_amd64/" "/usr/local/share/navsolve-cmd_1.2.1_amd64/NAVsolveNetCore" "/usr/local/share/navsolve-cmd_1.2.1_amd64/NAVsolveNetCore.deps.json" "/usr/local/share/navsolve-cmd_1.2.1_amd64/NAVsolveNetCore.dll" "/usr/local/share/navsolve-cmd_1.2.1_amd64/NAVsolveNetCore.pdb" "/usr/local/share/navsolve-cmd_1.2.1_amd64/NAVsolveNetCore.runtimeconfig.json" "/usr/local/share/navsolve-cmd_1.2.1_amd64/OxTS.NetCore.Utilities.dll" "/usr/local/share/navsolve-cmd_1.2.1_amd64/OxTS.NetCore.Utilities.pdb" %dir "/usr/local/share/navsolve-cmd_1.2.1_amd64/ref/" "/usr/local/share/navsolve-cmd_1.2.1_amd64/ref/NAVsolveNetCore.dll" %dir "/usr/share/doc/navsolve-cmd_1.2.1_amd64/" %dir "/usr/share/doc/navsolve-cmd_1.2.1_amd64/copyright/" "/usr/share/doc/navsolve-cmd_1.2.1_amd64/copyright/LICENSE.txt"
I don't see where the .spec file specifies a dependency for this. Is the rpm program looking inside the .rpm and coming up with dependencies?
Yes, rpmbuild calls plugins to generate a list of dependencies. For Mono there is such plugin (I do not know how you create your RPM so I do not know if it is actually used): https://build.opensuse.org/package/view_file/openSUSE:Factory/mono-core/mono...
I did not think it did that. So where are they coming from?
Hard to tell without verbose RPM build log, but you may check the above script.