| Summary: | Size verification failed during update of a debian-repository | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] opkg | Reporter: | Max <opkg-bug> | ||||
| Component: | opkg | Assignee: | Alejandro del Castillo <alejandro.delcastillo> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Undecided | ||||||
| Version: | 0.3.6 | ||||||
| Target Milestone: | 0.4.1 | ||||||
| Hardware: | All | ||||||
| OS: | arm | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Max
2019-02-15 22:19:10 UTC
I have a very similar configuration as reported above and get the same error message. Which size is opkg trying to verify in the 'release_verify_file' function? As a workaround, is it possible to disable the size verification on the command line? Fixed on commits: cb6ad4a dist_hash_add_from_file: add debian repository information as extra_data b7838a0 pkg_parse_line: allow Description fields that start with an empty line 78ba8fb release_parse_line: improve parsing of Release files Debian-based repo support on opkg is a not very well supported feature. At the time I tried it, it was totally busted. I fixed 3 issues and now it works with raspbian, but I fear there are likely other bugs lingering. |