Error occured after commiting files. No apparent reason why access would not be permitted.

Bug #903218 reported by David Ware
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar Explorer
Confirmed
Medium
Unassigned

Bug Description

After checking in files, this error occured.
There is no apparent reason why the file build.h would be un-accessible. It is located within the same location as the other files.

Tags: filewatcher
Revision history for this message
Martin Packman (gz) wrote :

David, you appear to have forgotten to paste the information bzr-explorer told you to report?

Revision history for this message
David Ware (david-ware) wrote :

Sorry, forgot to paste the data on the last error.

A similar error occured whilst Commiting within the same project (with the following details):-

bzr: ERROR: [Error 32] C:/worksp/IQMK1_Replacement/.bzr/branch/lock/releasing.ht1gz4uu3eqwg1nu08ah.tmp/*

Revision history for this message
Martin Packman (gz) wrote :

David, can you find that error in your .bzr.log (running `bzr version` will tell you where to find it) and attach that section to this bug report please?

Revision history for this message
David Ware (david-ware) wrote :

Attached log for the original reported error.

Revision history for this message
David Ware (david-ware) wrote :

Attached log for the latest error.

Revision history for this message
Martin Packman (gz) wrote :

Thanks!

Changed in bzr-explorer:
importance: Undecided → Medium
status: New → Confirmed
tags: added: filewatcher
Revision history for this message
André Bachmann (andrebachmann-dd) wrote :

A co-worker just had the same error after committing a change with Bazaar 2.4.2-1. Fortunately, the commit itself is done correctly, as qlog shows.
I strongly suspect it is the same problem from my bug #850004.

Revision history for this message
Alexander Belchenko (bialix) wrote :

Please, test new Bazaar Explorer 1.2.2 release, and tell us whether the problem still exists.

Revision history for this message
André Bachmann (andrebachmann-dd) wrote :

The problem seems to be gone with Bazaar Explorer 1.2.2 - at least I don't have encountered them after the update.

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.