Removing .OTHER file removes main file

Bug #674019 reported by Michael J. Vinca on 2010-11-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QBzr
High
Unassigned

Bug Description

Somehow one of my users "Added" filename.OTHER into pending commits for the branch. No big deal, since she hadn't committed yet, so I select the file in Bazaar Explorer, choose Remove from the context menu, and to my horror, not only was filename.OTHER removed, so was filename! This is completely unintuitive that when selecting one file, related files are also removed.

Michael J. Vinca (michaelj) wrote :

Further information: After some testing, it wasn't my user that added filename.OTHER, it was a merge process that created a context conflict. Even more so, performing the remove command on the .OTHER file should not delete both files.

affects: bzr-explorer → qbzr
Changed in qbzr:
importance: Undecided → High
status: New → Confirmed
tags: added: treewidget
Craig Hewetson (craighewetson) wrote :

Was the "conflict" resolved (bzr resolve filename.OTHER) before explicitly deleting it?
I'm thinking that it might consider both files the "same" before its resolved, and therefore the deletion might have two different outcomes.
Regardless, I agree that it shouldn't delete both files.

Michael J. Vinca (michaelj) wrote :

The conflict was not resolved. We were surprised that the (.OTHER) was a pending addition and were trying to remove it because we didn't want it to be added. Later we realized that "resolve" essentially does the delete in this case. It was just different from a text conflict, where .BASE, .THIS and .OTHER files aren't "pending additions", so we thought something was wrong and were trying to fix it.

Now that we know that the "addition" is just misleading and we can ignore it, we are acting accordingly. However, in learning this process, I was quite surprised that both files were deleting, which, in essence, deleted our good file where we had just finished the manual resolving of the conflicts (without having said "resolve" yet). So loosing that work was quite frustrating, and I figured I would file the bug about the two file deletion surprise.

BTW, we did bzr resolve filename in the end, as opposed to filename.OTHER, if that makes any difference. After doing so, filename.OTHER is listed in the bazaar explorer dialog as added, missing.

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

Other bug subscribers