John A Meinel wrote:
> Post 'bzr pack' I get:
> 101M .bzr/repository/obsolete_packs
> 1.0K .bzr/repository/pack-names
> 8.8M .bzr/repository/indices
> 30M .bzr/repository/packs
>
> In other words, I was correct about expecting ~30MB of packed content.
> As the size dropped from 101MB => 38.8MB (packs + indices).
>
> Do we just need to ask a LOSA to run 'bzr pack' since the branch is only
> accessible from pqm?
Well the master copy was freshly upgraded yesterday; we should check
with spm how big it is. That same bzr was then used to push the new
bzr.dev branch. Lets get detail, but be sure to find the root cause;
otherwise users will need to manually pack etc too.
summary "newly converted and pushed repository poorly packed."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John A Meinel wrote: /obsolete_ packs /pack-names /indices /packs
> Post 'bzr pack' I get:
> 101M .bzr/repository
> 1.0K .bzr/repository
> 8.8M .bzr/repository
> 30M .bzr/repository
>
> In other words, I was correct about expecting ~30MB of packed content.
> As the size dropped from 101MB => 38.8MB (packs + indices).
>
> Do we just need to ask a LOSA to run 'bzr pack' since the branch is only
> accessible from pqm?
Well the master copy was freshly upgraded yesterday; we should check
with spm how big it is. That same bzr was then used to push the new
bzr.dev branch. Lets get detail, but be sure to find the root cause;
otherwise users will need to manually pack etc too.
summary "newly converted and pushed repository poorly packed." enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq gH1MACgkQ42zgmr PGrq6+dwCfUdDTj 2ViEef5SdLeMmpV pIJS YwOdyDXfSBkJlLU HV
+X0An2hKQwZOMY7
=gXsz
-----END PGP SIGNATURE-----