| Summary: | opkg don't resume big upgrades (old issue #17) | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] opkg | Reporter: | Alejandro del Castillo <alejandro.delcastillo> |
| Component: | opkg | Assignee: | Alex Stewart <alex.stewart> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | Medium | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Alejandro del Castillo
2015-08-14 17:00:54 UTC
Based on the discussion, it seems like opkg correctly handles resuming the upgrade, with interrupted via SIGINT. I don't think it's reasonably within the scope of the opkg project to optimize resuming upgrades through sudden power-loss. It seems like that opinion is well-founded, given that no one has stepped up to move that feature along in the years since this bug was filed. Closing as won't fix. |