I found that "opkg update" doesn't mind when given a Debian package feed (by mistake in my case): root@qemux86-64:~# opkg update Downloading http://192.168.1.20:8000/all/Packages.gz. Updated source 'uri-all-0'. Downloading http://192.168.1.20:8000/core2-64/Packages.gz. Updated source 'uri-core2-64-0'. Downloading http://192.168.1.20:8000/qemux86_64/Packages.gz. Updated source 'uri-qemux86_64-0'. I know that opkg is meant to be largely compatible with dpkg, but couldn't it warn when it doesn't find any ipk package in the various Packages.gz files? Because of that "opkg list-upgradable" returns nothing and no package can be used from the feed. I also though about having "opkg list-upgradable", "opkg install" and "opkg upgrade" complain when they don't see any matching package, but this can perfectly happen when using an ipk feed.
This seems like a developer tooling gap, rather than a situation were we would want to error to the user. As you said, providing opkg with a debian package list (or even a mixed package list) is a totally valid state. I think opkg will happily process: dpkg, ipk, opk, and raw .ar archives; so long as they comply with the internal layout that opkg expects. And I think the assumption in opkg deployments is that the package feed is being prepared by the distro builder. So if the user is getting a well-formed package index from their distro, but then gets an error/warning from opkg about it containing no IPKs, what is the *user* supposed to do about that?
Hi Alex Thanks for your quick response and clarifications. Let's close this bug then. Thanks again