| Summary: | 'devtool upgrade' tracebacks when a recipe includes another recipe with PV in the name | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Alexander Kanavin <alex.kanavin> |
| Component: | Scripts and Tools | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | ross.burton |
| Version: | unspecified | ||
| Target Milestone: | 2.8 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Alexander Kanavin
2019-06-18 11:07:35 UTC
A related improvement would be to have a 'devtool reset --force-all' command, which would basically re-initialize the workspace to a completely blank state. This wouls allow recovery from similar tracebacks - even if this specific one is fixed, there may be more. I've sent a patch to fix this so it doesn't leave files around after the error by default (as well as generally fixing error handling). I think automatically handling this scenario completely (i.e. upgrading the other recipe) would be overkill, since this is rather unusual. With regard to changing devtool reset, I'd prefer instead that we fix these kinds of situations as they come up rather than providing a tool to work around them. Fix merged to master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b52d58b8bb81f5053b9fa8b79a137c37d6ef6fb3 (Note that the recipe originally triggering this was already changed to avoid the issue under http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0d8357f9f38f529cc03ce2602d5209c9f8dfe878 ). |