| Summary: | Deploy action cannot be cancelled | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Anjuta Plugin | Reporter: | Joshua Lock - Disabled <josh> |
| Component: | anjuta-plugin | Assignee: | Joshua Lock - Disabled <josh> |
| Status: | VERIFIED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | liping.ke, sgw, yp.ap.watcher, yp.watcher |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M1 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
Joshua Lock - Disabled
2010-02-23 17:37:43 UTC
We should definitely handle cancelling the dialog here in a graceful way but we should also consider populating with the default root password and also disabling password hiding. Hi, Josh I can't reproduce the bug here. When deploy->cancel, on the "Deploy" tab, you'll see "rsync error: received SIGINT, SIGTERM, or SIGHUP (cod20) at rsync.c(544) (sender = 3.0.6). Deleting tempory deployment area. Error During deployment. Deployment finished. And I checked the qemu /usr/local/bin, no binary file deployed. So can you elaborate how to reproduce the bug. How ever, I do find a problem about deploy. Even if you deploy successfully, Still printing: "Error during deployment". I will fire a new bug for this. Thanks& Regards, criping Seems to work |