Comment 0 for bug 818138

Revision history for this message
Scott Moser (smoser) wrote : absurd upload size on second push

I did the following:
$ lp:~ubuntu-on-ec2/ubuntu-on-ec2/live-build live-build.dist
$ bzr branch live-build.dist -r 1811 cloud-images
$ cd cloud-images
$ # manually apply revision 1813, 1814 , the point of this was to ditch my accidental merge in 1812.

$ bzr push lp:~ubuntu-on-ec2/live-build/cloud-images
This transport does not update the working tree of: bzr+ssh:// See 'bzr help working-trees' for more information.
Created new branch.

The above too a while (minutes). I wondered why the message , which I suppose is due to repository formats or something, and then tried again:

$ bzr push lp:~ubuntu-on-ec2/live-build/cloud-images
#### 20 minutes or more later:
254912kB 244kB/s | Fetching revisions:Inserting stream
259070kB 237kB/s | Fetching revisions:Inserting stream

Eventually that reported:
No new revisions to push.

If I do a clean
 $ bzr branch lp:~ubuntu-on-ec2/live-build/cloud-images
 $ du -hs cloud-images

So I guess i have 2 issues:
 a.) why the "This transport does not update the working tree" message
 b.) why the 250M+ upload for "no revisions to push"

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: bzr 2.4.0~beta5-2ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Fri Jul 29 11:54:05 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
PackageArchitecture: all
 PATH=(custom, user)
SourcePackage: bzr
UpgradeStatus: Upgraded to oneiric on 2010-11-15 (255 days ago)