03-12-2020 02:38 PM
Thinking I might be invoking opkg install incorrectly using the entire filename I tried just
opkg install hellopkg and got the following:
03-12-2020 03:09 PM
Thanks for sending that information and your ipk. This behavior is very strange and I can't even get it to reproduce.
FYI, the second error is reasonably expected. opkg is trying to use the "hellopkg" directory instead of the ipk when you run the command (as there's no hellopkg ipk since the system isn't accessing our repos) and fails accordingly.
I've tried installing the xinetd-dev ipk after downloading it, and I get the expected errors on an offline system (missing dependencies). After that, I have no issue installing your ipk. At least there's the good news that your ipk works on my system without issue!
03-12-2020 03:24 PM - edited 03-12-2020 03:28 PM
This is an offline system and I can not run opkg update with it - it is not allowed to be connected to the internet for govt security issues.
I will check and see if there is anything /var/cache/opkg
I'm glad to hear that my little helloworld ipk installs properly, that's good to know.
So when I run the opkg install its proper form to use the whole filename with .ipk, such that opkg install hellopkg_1.0.0_x64.ipk is valid?
03-12-2020 03:43 PM
There is nothing in /var/cache/opkg
03-13-2020 12:30 PM - edited 03-13-2020 12:31 PM
Looking at the information from v4 verbosity, I think installing the ipk wants to download from the online repo? This is of course going to fail, since the system is offline.
I copied the last line into the file as that wasn't added in when I piped the install outputs to the text file.
03-13-2020 12:41 PM
Can you try running the install for your hellopkg with the same logging? We know the xinet should fail since it's missing dependencies, but your package shouldn't have that issue.
03-13-2020 01:35 PM
here are three levels of verbosity for the install of the hellopgk_1.0.0.0_x64.ipk
Still getting the odd response from asking to install hellopgk that is referring back to xinetd - something is "stuck" somewhere it seems in the opkg side
Collected errors:
* Solver encountered 2 problem(s):
* Problem 1/2:
* - nothing provides xinetd = 2.3.15-r2.154 needed by xinetd-dev-2.3.15-r2.154.core2-64
*
* Solution 1:
* - do not ask to install xinetd-dev-2.3.15-r2.154.core2-64
* Problem 2/2:
* - nothing provides libc needed by xinetd-2.3.15-5.x86_64
*
* Solution 1:
* - do not ask to install a package providing xinetd
03-13-2020 01:50 PM
That's weird. It recognizes that you're installing the hellopkg but xinetd-dev is still marked for install. I'm actually not entirely sure how that happens.
Let's see if we can trick opkg into installing xinetd-dev and then remove it. Specifically use the following flag when installing the package to tell it to proceed without dependencies:
--force-depends
Afterwards, try removing xinetd-dev with the same flag, then install your package.
03-13-2020 02:14 PM
It didn't like that either - still failed saying it could not download xinetd
Collected Errors
* opkg_download_file: ///etc/opt/repo/19.07/x86_64/packages/xinetd_2.3.15-5_x86_64.ipk: No such file.
* opkg_install_pkg: Failed to download xinetd. Perhaps you need to run 'opkg update'?
Maybe I should download xinetd_2.3.15-5_x86_64.ipk from the feed manually and install put it in the expected location and try that again...
03-13-2020 02:47 PM - edited 03-13-2020 02:56 PM
ok I downloaded xinetd_2.3.15-5_86_64.ipk
tried install
requested /etc/opt/ni/2091.1/initscripts-dev_1.0-r155.44_core2-64.ipk
I downloaded that and then installed xinetd_2.3.15-5_x86_64.ipk
opkg info xinetd seems to show xinetd_2.3.15-5 installed
Went back and tried opkg install hellopkg_1.0.0_x64.ipk and this time got a different error:
Collected Errors:
Solver encountered 1 problem(s):
* Nothing provides requested initscripts-dev
performed opkg info initscripts-dev
and it is indeed not installed - says the file I need
Filename: initscripts-dev_1.0-r155.44_core2-64.ipk
I will try to download that...