[Bug 818138] Re: absurd upload size on second push

[Martin Pool]

The other bug I was thinking of was bug 465517, but is supposed to be
fixed ahead of 2.4b5, and it that wouldn't explain you seeing different
results running apparently the same command on lucid and oneiric.  So
more investigation seems to be needed.

** Also affects: bzr
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bzr in Ubuntu.
https://bugs.launchpad.net/bugs/818138

Title:
  absurd upload size on second push

Status in Bazaar Version Control System:
  New
Status in “bzr” package in Ubuntu:
  New

Bug description:
  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.

  Then
  $ bzr push lp:~ubuntu-on-ec2/live-build/cloud-images
  This transport does not update the working tree of: bzr+ssh://bazaar.launchpad.net/~ubuntu-on-ec2/live-build/cloud-images/. 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 the following on oneiric, i'll see something like:
   $ bzr branch lp:~ubuntu-on-ec2/live-build/cloud-images
   273670kB  1957kB/s \ Fetching revisions:Inserting stream:Estimate 104073/106426             
   324886kB   848kB/s / Fetching revisions:Inserting stream:Estimate 113712/116014                   
   327077kB    34kB/s - Build phase:Building tree 42/710                                             
   Branched 1813 revision(s).  
   $ du -hs cloud-images/
   314M	cloud-images/

  However, if I do the same thing on a lucid system 
   $ bzr --version | head -n 1
   Bazaar (bzr) 2.1.4
   $ bzr branch lp:~ubuntu-on-ec2/live-build/cloud-images
   $ du -hs cloud-images
   $ du -hs cloud-images/
   52M     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"
   c.) why am I do I waste 6X the space on oneiric that I would for the same thing on lucid.

  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
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bzr
  UpgradeStatus: Upgraded to oneiric on 2010-11-15 (255 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/bzr/+bug/818138/+subscriptions