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
Collected errors:
* check_data_file_clashes: Package rmbim wants to install file /home/dem/R2305/build_dir/target-mipsel_24kc_musl/root-ramips/lib/netifd/proto/mbim.sh
But that file is already provided by package * umbim
* check_data_file_clashes: Package rmbim wants to install file /home/dem/R2305/build_dir/target-mipsel_24kc_musl/root-ramips/sbin/umbim
But that file is already provided by package * umbim
* opkg_install_cmd: Cannot install package rmbim.
* check_data_file_clashes: Package rqmi wants to install file /home/dem/R2305/build_dir/target-mipsel_24kc_musl/root-ramips/lib/netifd/proto/qmi.sh
But that file is already provided by package * uqmi
* check_data_file_clashes: Package rqmi wants to install file /home/dem/R2305/build_dir/target-mipsel_24kc_musl/root-ramips/sbin/uqmi
But that file is already provided by package * uqmi
* opkg_install_cmd: Cannot install package rqmi.
Need help!
The text was updated successfully, but these errors were encountered:
My understanding is rqmi and uqmi conflict. Same with rmbim and umbim.
Both uqmi and umbim should be left unselected. It's possible you're seeing something that depends on them - I don't see any dependencies in opkg on umbim, and uqmi only has luci-proto-qmi depending on it.
The rqmi and rmbim packages are forks of those packages that provide that same functionality plus additional functions needed for ROOter, so you should use the r* packages instead, and leave the original uqmi and umbim packages unselected.
I'm not as aware on this one, but I believe luci-proto-qmi may also do things that break how ROOter works.
Some of these problems would be easier if OpenWRT's configuration system gave us a way to mark packages that conflict, but I've done some digging this morning and don't see one. Instead people find out the hard way with errors like this.
Need help!
The text was updated successfully, but these errors were encountered: