`bzr qcommit UNCHANGED_FILE` fails

Bug #406427 reported by Alexander Belchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QBzr
Fix Released
Medium
Gary van der Merwe

Bug Description

C:\Temp\1>bzr init
Created a standalone tree (format: pack-0.92)

C:\Temp\1>echo foo > foo

C:\Temp\1>bzr add
adding foo

C:\Temp\1>bzr ci -m 1
Committing to: C:/Temp/1/
added foo
Committed revision 1.

C:\Temp\1>bzr qci foo
bzr: ERROR: No such file: u'foo'

At this point qcommit window opens and immediately closing with error shown above.
I think qcommit should not fail in this situation. It should either report error in message dialog box or silently ignore wrong files.

In the same situation standard commit just works:

C:\Temp\1>bzr ci foo -m 2
Committing to: C:/Temp/1/
aborting commit write group: PointlessCommit(No changes to commit)
bzr: ERROR: No changes to commit. Use --unchanged to commit anyhow.

Changed in qbzr:
importance: Undecided → Medium
status: New → Confirmed
summary: - `bzr qcommit UNSHANGED_FILE` fails
+ `bzr qcommit UNCHANGED_FILE` fails
Changed in qbzr:
assignee: nobody → Gary van der Merwe (garyvdm)
milestone: none → 0.13
status: Confirmed → Fix Released
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.