You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Master and 21.02 I found that running opkg install package.ipk will raise an errormessage about incompatible architecture when there is an unmet dependency.
I've choosen to open against 21.02, as it might more easy to spot before release.
root@Ahof-Frieden05:~# opkg install -V2 /tmp/jupp-data_3.1.40-1_all.ipk
opkg_conf_parse_file: Loading conf file /etc/opkg.conf.
opkg_conf_parse_file: Loading conf file /etc/opkg/customfeeds.conf.
opkg_conf_parse_file: Loading conf file /etc/opkg/distfeeds.conf.
pkg_hash_load_feeds:
pkg_hash_load_feeds:
pkg_hash_load_status_files:
pkg_info_preinstall_check: Updating file owner list.
Installing jupp-data (3.1.40-1) to root...
satisfy_dependencies_for: This could mean that your package list is out of date or that the packages mentioned above do not yet exist (try 'opkg update'). To proceed in spite of this problem try again with the '-force-depends' option.
opkg_configure_packages: Configuring unpacked packages.
opkg_configure_packages: Reordering packages before configuring them...
Collected errors:
satisfy_dependencies_for: Cannot satisfy the following dependencies for
jupp-data:
Previous version of opkg returned a "unresolved dependency" in such case, with is correct and also points into the direction how to solve the installation. Console-output is
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for
jupp-data:
* jupp
* opkg_install_cmd: Cannot install package jupp-data.
This happens already on a virgin system, when the package, e.g. jupp-data, is transferred via scp to get installed offline. I found this when trying to add a package on a system without direct network-connection, so there is no opkg-cache.
My finding is based on a "blank" unit without package-cache
rebooting the board
scp-ing the package to /tmp
then login
calling opkg install
The workflow is based on the situation, where the board has no internet-access and I can only login via IPv6-link-local, to install a missing package.
This was seen with following code: "OpenWrt SNAPSHOT, r16599-43dad22025", "OpenWrt 21.02.0-rc1, r16046-59980f7aaf",
I had some investigation done with on the ML, here some pointers:
SAm0815:
For Master and 21.02 I found that running
opkg install package.ipk
will raise an errormessage about incompatible architecture when there is an unmet dependency.I've choosen to open against 21.02, as it might more easy to spot before release.
root@Ahof-Frieden05:~# opkg install -V2 /tmp/jupp-data_3.1.40-1_all.ipk
opkg_conf_parse_file: Loading conf file /etc/opkg.conf.
opkg_conf_parse_file: Loading conf file /etc/opkg/customfeeds.conf.
opkg_conf_parse_file: Loading conf file /etc/opkg/distfeeds.conf.
pkg_hash_load_feeds:
pkg_hash_load_feeds:
pkg_hash_load_status_files:
pkg_info_preinstall_check: Updating file owner list.
Installing jupp-data (3.1.40-1) to root...
satisfy_dependencies_for: This could mean that your package list is out of date or that the packages mentioned above do not yet exist (try 'opkg update'). To proceed in spite of this problem try again with the '-force-depends' option.
opkg_configure_packages: Configuring unpacked packages.
opkg_configure_packages: Reordering packages before configuring them...
Collected errors:
jupp-data:
root@Ahof-Frieden05:~#
Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for jupp-data: * jupp * opkg_install_cmd: Cannot install package jupp-data.
This happens already on a virgin system, when the package, e.g. jupp-data, is transferred via scp to get installed offline. I found this when trying to add a package on a system without direct network-connection, so there is no opkg-cache.
My finding is based on a "blank" unit without package-cache
The workflow is based on the situation, where the board has no internet-access and I can only login via IPv6-link-local, to install a missing package.
This was seen with following code: "OpenWrt SNAPSHOT, r16599-43dad22025", "OpenWrt 21.02.0-rc1, r16046-59980f7aaf",
I had some investigation done with on the ML, here some pointers:
A bit of digging points to a commit after "opkg 2020-08-31.cf44c2feb606" causing this (see also http://lists.openwrt.org/pipermail/openwrt-devel/2021-May/034924.html)
The text was updated successfully, but these errors were encountered: