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

Fri Aug 5 14:22:54 UTC 2011

Looking at the directories directly:
http://bazaar.launchpad.net/~ubuntu-on-ec2/ubuntu-on-ec2/live-build/.bzr/repository/packs/
vs
http://bazaar.launchpad.net/~ubuntu-on-ec2/live-build/cloud-images/.bzr/repository/packs/

There are a few things:

1) It certainly appears to have uploaded all of the history of the repository.
2) Bug #465517 is that it was pushing the whole repository, not the whole ancestry of a given branch. Eg, I have bzr-rewrite in the same repository as bzr. bug #465517 was that 'bzr push' && ^C && 'bzr push' would try to push up all of *bzr* into the *bzr-rewrite* target.
3) Because of the ^C and re-push, the branch did not end up stacked on the development focus:
http://bazaar.launchpad.net/~ubuntu-on-ec2/live-build/cloud-images/.bzr/branch/branch.conf
(there should be a 'stacked_on_location' there.)
4) The bug is that the second 'bzr push' doesn't see that it should be stacked by-default. I believe the cause is:

 a) The config stating that it should be stacked is a virtual file in ~/ubuntu-on-ec2/ (AIUI). We fake a .bzr/control.conf file.
 b) After the first push, we have created the .bzr/ directory and .bzr/repository but *not* the .bzr/branch. So the first process does see that the branch should be stacked, but it won't create that branch until the repository fetch has finished.

We create the branch last because we didn't want a psuedo-branch to
confuse things. The branch can't say that it is at the target tip
revision, because that content has not been pushed to the repository
yet. However, I think we've had enough experience to show that we can
probably just set the branch tip to 'null:', finish the fetch, and then
update the branch tip to the target revision.

I don't think this needs to be critical, because it isn't any sort of
regression. We've been doing since stacked branches were first created.

** Changed in: bzr
   Importance: Critical => High

** Changed in: bzr
     Assignee: (unassigned) => canonical-bazaar (canonical-bazaar)

** Summary changed:

- absurd upload size on second push
+ branch not stacked if first push is interrupted

-- 
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:
  branch not stacked if first push is interrupted

Status in Bazaar Version Control System:
  Confirmed
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