| Summary: | Delete build information | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Toaster | Reporter: | Belen Barros Pena <belen.barros.pena> |
| Component: | toaster | Assignee: | Alexandru Damian <alexandru.damian> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, david.reyna, jessica.zhang |
| Version: | unspecified | ||
| Target Milestone: | 1.6 M5 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Done (doc changes complete) | |
|
Description
Belen Barros Pena
2013-06-07 10:52:55 UTC
The ugly workaround is to erase and recreate the database. Alex has suggested to add a command to Django through manage.py to avoid any security issues (the GUI has no authentication built in). This should be solved with a bldviewer command addition for manage.py: - listbuilds :should get a user-readable tabbed list of build ids and identification information - deletebuild id :should delete the build with the specified id AND ALL related information (traversing the ForeignKey relationships recursively) from the database. This was merged sometime mmm, maybe I spoke too soon. Running ./manage.py buildslist returns an error saying DatabaseError: no such table: orm_build This is on master:ac4ff568f5b2ad4f50a1b7b60797e7b797c314bb Scott has already provided the content relevant to this issue, which will be published in the Yocto Project wiki for 1.6 release. my bad: this is working, but if you are using the standard configuration you need to issue the commands from the /poky/build directory. verified in master:39846ddbce87d26eb68870914bf86a8ce5e86e5c |