After running update dialog the working tree does not get refreshed.

Bug #529891 reported by Craig Hewetson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Explorer
Confirmed
High
Unassigned

Bug Description

NOTE this happens when the update causes a conflict. The process results in an "error" and therefore the refreshing mechanism doesn't kick in.

I would expect it to refresh so that the user can see the working tree with the newly created conflicts.

Revision history for this message
Ian Clatworthy (ian-clatworthy) wrote :

Agreed. I'm also seeing the same problem when Merge has conflicts.

Changed in bzr-explorer:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Alexander Belchenko (bialix) wrote :

That's reasonable.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.