commit incorrectly reports missing files as modified

Bug #553955 reported by Alexander Belchenko
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar
Fix Released
Medium
Unassigned

Bug Description

C:\Temp\6>bzr init .
Created a standalone tree (format: 1.9)

C:\Temp\6>echo > foo.txt

C:\Temp\6>bzr add
adding foo.txt

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

C:\Temp\6>del foo.txt

C:\Temp\6>bzr st
removed:
  foo.txt

C:\Temp\6>bzr ci -m2
Committing to: C:/Temp/6/
missing foo.txt
modified foo.txt
Committed revision 2.

I don't think removed foo.txt is "modified" as commit says. I think it's actually "removed" as status says. Or maybe I misunderstood something?

Related branches

description: updated
Revision history for this message
Vincent Ladeuil (vila) wrote :

Looks like a pretty shallow bug in commit, bzr seems to record the deletion anyway:

$ bzr st -r1..2
removed:
  foo.txt

Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 553955] Re: bzr 2.1: commit incorrectly reports missing files as modified

Vincent Ladeuil пишет:
> Looks like a pretty shallow bug in commit, bzr seems to record the
> deletion anyway:
>
> $ bzr st -r1..2
> removed:
> foo.txt

Yes, I think it's mostly UI thing.

tags: added: ui
Vincent Ladeuil (vila)
tags: added: commit
Martin Pool (mbp)
tags: added: regression
Vincent Ladeuil (vila)
summary: - bzr 2.1: commit incorrectly reports missing files as modified
+ commit incorrectly reports missing files as modified
Changed in bzr:
status: Confirmed → Fix Released
milestone: none → 2.5b1
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.