Rev 5601: NEWS about fixing bug #659978 in http://bazaar.launchpad.net/~jameinel/bzr/2.3-break-lock-corrupt-win32

[John Arbash Meinel]

At http://bazaar.launchpad.net/~jameinel/bzr/2.3-break-lock-corrupt-win32

------------------------------------------------------------
revno: 5601
revision-id: john at arbash-meinel.com-20110112204137-x9bhoxzyb5l6dh82
parent: john at arbash-meinel.com-20110112203115-w55rhrojc21qs8tk
fixes bug(s): https://launchpad.net/bugs/659978
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: 2.3-break-lock-corrupt-win32
timestamp: Wed 2011-01-12 14:41:37 -0600
message:
  NEWS about fixing bug #659978
-------------- next part --------------
=== modified file 'doc/en/release-notes/bzr-2.3.txt'
--- a/doc/en/release-notes/bzr-2.3.txt	2011-01-12 15:50:12 +0000
+++ b/doc/en/release-notes/bzr-2.3.txt	2011-01-12 20:41:37 +0000
@@ -65,6 +65,10 @@
 * Avoid leaking SSH subprocess communication socket into unrelated child
   processes, which could cause bzr to hang on exit. (Max Bowsher, #696285)
 
+* ``bzr break-lock`` on a corrupted lock file works correctly, rather than
+  raising a PermissionDenied error. We were accidentally holding open the
+  file we were trying to delete. (John Arbash Meinel, #659978)
+
 * ``bzr update`` in a checkout of a readonly branch works again, without
   trying to set the tags in the master branch. This had been broken by the
   bug fix for bug #603395.  (John Arbash Meinel, #701212)