error about uncommitted changes, but continues nonetheless

Bug #221369 reported by Andreas Hasenack on 2008-04-24
Affects Status Importance Assigned to Milestone

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/andreas/canonical/landscape-client/bound/staging/" has uncommitted changes.

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.

Jamu Kakar (jkakar) on 2008-04-25
Changed in autoppa:
status: New → Confirmed
Jamu Kakar (jkakar) on 2008-06-02
Changed in autoppa:
importance: Undecided → Medium
milestone: none → 0.0.6
Jelmer Vernooij (jelmer) wrote :

I just hit this as well.

Jamu Kakar (jkakar) on 2009-09-20
Changed in autoppa:
milestone: 0.0.6 → 0.1.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers