Moving large files

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-06-08 15:41, Muhammad Bashir Al-Noimi wrote:
> New question #230419 on Bazaar:
> https://answers.launchpad.net/bzr/+question/230419
>
> I've to use Bzr with some binaries (GigaBytes) but I noticed that
> moving any file from folder to another one similar to add a new
> one.
>
> Is there any way for making Bzr consider that files as moved files
> instead of new ones?
>
> PS Init. repos. size was 3GB moving 1GB file increased the
> repository to 4GB although I didn't add any new file just move one
> from folder to another one
>

Are you doing 'bzr mv a b' or just 'mv a b; bzr add' ?

If you are doing 'bzr mv' you can probably just issue 'bzr pack' and
it will reclaim the extra space. Commit of a change stores an
uncompressed copy until the repository is repacked. This will happen
automatically eventually, but when you have a big change you can
trigger it manually.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlGzGTIACgkQJdeBCYSNAAOIYQCgt2qiR4y5huD3E039vqNzjFu/
B2sAoLsHg3EPZXkW9jiakspF61h95AHp
=vQAA
-----END PGP SIGNATURE-----

> Are you doing 'bzr mv a b' or just 'mv a b; bzr add' ?
Basically I'm using Bazaar Explorer but in short I'm using 'mv a b; bzr add'

> If you are doing 'bzr mv'
'bzr mv' will save the file spcace of the repository? If yes is there any way to use it visually by Bazaar Explorer insteas of using "All Commands" actions?

I found it... I just need to move the files manually from working tree dialog in Bazaar Explorer instead of moving them from operating system file manager.

Thanks John A Meinel for help.

By the way, I used 'bzr pack' and 'bzr pack --clean-obsolete-packs' nothing changed!

The size still multiplied!

As I mentioned, plain commit doesn't store a text delta. That is delayed
until the repository is repacked. If you have a few more commits, it will
eventually go down. However, you can do 'bzr pack --clean-obsolete' (check
--help, I'm not sure on the spelling) to force bzr to do it sooner.

The default heuristics are good for handling source trees. Gig files
require a bit more manual intervention.

John
=:->
On Jun 8, 2013 4:31 PM, "Muhammad Bashir Al-Noimi" <
<email address hidden>> wrote:

> Question #230419 on Bazaar changed:
> https://answers.launchpad.net/bzr/+question/230419
>
> Status: Solved => Open
>
> Muhammad Bashir Al-Noimi is still having a problem:
> Oops... although I could use 'bzr mv a b' from the GUI but it didn't save
> repository file size!!!
> http://img89.imageshack.us/img89/401/commit001.png
>
> --
> You received this question notification because you are an answer
> contact for Bazaar.
>

> As I mentioned, plain commit doesn't store a text delta. That is delayed until the repository is repacked. If you have a few ore commits, it will eventually go down.
That's mean I don't need to do 'bzr pack --clean-obsolete' manually as long as I still working on that repository, is it?

Thanks John A Meinel, that solved my question.