Even if that bug is not a priority, there should be at least a warning in the commit dialog if a file is too large for Bazaar.
This bug affects me even if I did not wanted to add a large file...
* I did a commit of a large file by mistake.
* I did an uncommit.
* From that point, I was unable to do new commit (out of memory)
* pack seems to be the problem
* After that Bazaar refused all my attemps to recover (pack always return out of memory)
** I updated from 2.1.1 to 2.2.0 -> no difference
** I did a new branch (not binded) at the previous revision, pack, push -> out of memory
** Even worse, another developper on another branch (same parent) got this error when attempting to do a commit (share repository)
** I took the backup version of yesterday (the main shared repo) and I did a new binded branch in my locally shared repos I got again the same error...
It looks like I will have to:
* takes the backup for the server
* reinit a new share repos on my local computer
* redo manually all the commit of the day.
Setup:
* share repo available from a networked windows share
* binded branch on local developpers computer. (with a share repo also locally)
Even if that bug is not a priority, there should be at least a warning in the commit dialog if a file is too large for Bazaar.
This bug affects me even if I did not wanted to add a large file...
* I did a commit of a large file by mistake.
* I did an uncommit.
* From that point, I was unable to do new commit (out of memory)
* pack seems to be the problem
* After that Bazaar refused all my attemps to recover (pack always return out of memory)
** I updated from 2.1.1 to 2.2.0 -> no difference
** I did a new branch (not binded) at the previous revision, pack, push -> out of memory
** Even worse, another developper on another branch (same parent) got this error when attempting to do a commit (share repository)
** I took the backup version of yesterday (the main shared repo) and I did a new binded branch in my locally shared repos I got again the same error...
It looks like I will have to:
* takes the backup for the server
* reinit a new share repos on my local computer
* redo manually all the commit of the day.
Setup:
* share repo available from a networked windows share
* binded branch on local developpers computer. (with a share repo also locally)