| Summary: | opkg doesn't complain when updating from a Debian package feed | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] opkg | Reporter: | Michael Opdenacker <michael.opdenacker> |
| Component: | opkg | Assignee: | Alex Stewart <alex.stewart> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Undecided | CC: | bruce.ashfield, michael.opdenacker |
| Version: | 0.6.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Michael Opdenacker
2024-02-07 15:15:18 UTC
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 |