error about uncommitted changes, but continues nonetheless
Bug #221369 reported by
Andreas Hasenack
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| AutoPPA |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
I did a merge from trunk to staging, but forgot to commit the changes in staging. I then ran autoppa.
A few moments later, it gave me this error:
bzr: ERROR: Working tree "/home/
But it didn't stop. In fact, when it did its own merging, the trunk->staging merge was included. So it seemed fine. But somehow it wasn't, because the uploaded package didn't contain the fixes I pulled in from trunk.
This cost me a release number, because I had to bump it and send again.
| Changed in autoppa: | |
| status: | New → Confirmed |
| Changed in autoppa: | |
| importance: | Undecided → Medium |
| milestone: | none → 0.0.6 |
Revision history for this message
| Jelmer Vernooij (jelmer) wrote | #1 |
| Changed in autoppa: | |
| milestone: | 0.0.6 → 0.1.0 |
To post a comment you must log in.
I just hit this as well.