"bzr send" goes through too much history

Bug #416249 reported by Johan Walles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Fix Released
Wishlist
Jelmer Vernooij

Bug Description

With bzr 1.17 and bzr-svn 0.6.4:

1. To work around bug 407283, add the following lines to your ~/.bazaar/subversion.conf:
"
[13f79535-47bb-0310-9956-ffa450edef68]
use-cache = False
"

2. Then do bzr branch http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.2 to get yourself a branch. About 1100 revisions will be downloaded..

3. Change a file in your branch and commit your change.

4. bzr send -o /dev/null

To perform the send, Bazaar says that it wants to do "discovering revprop revisions" for over 800k revisions.

Considering my branch only has 1100 revisions, I didn't expect it to have to go through more than that.

I don't really understand why it has to go through anything not in my local branch (which should be quick since it's on disk) or in new revisions in the upstream repository that haven't been merged yet. But that might be because I don't understand what send really has to do, so I don't know if that's fixable.

Tags: usability
Johan Walles (walles)
tags: added: usability
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

This is caused by the fact that you have disabled the cache.

Changed in bzr-svn:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I can't reproduce this (anymore?)

Changed in bzr-svn:
status: Triaged → Incomplete
Revision history for this message
Johan Walles (walles) wrote :

I still see this just as before (but with 950000 revisions rather than 800000).

You probably already thought of this, but have you verified that you don't already have a cache for Apache's SVN repo when you try this?

I'm using:
Bazaar (bzr) 2.1.2
  Python interpreter: /usr/bin/python 2.5.5
  Python standard library: /usr/lib/python2.5
  Platform: Linux-2.6.32-3-686-i686-with-debian-squeeze-sid
  bzrlib: /usr/lib/python2.5/site-packages/bzrlib
  Bazaar configuration: /home/johan/.bazaar
  Bazaar log file: /home/johan/.bzr.log

johan@johansdator:/tmp/hej/maven-scm-1.2$ bzr plugins |grep -A1 svn
svn 1.0.2
    Support for Subversion branches

Changed in bzr-svn:
status: Incomplete → New
Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 416249] Re: "bzr send" goes through too much history

On Wed, 2010-06-09 at 17:27 +0000, Johan Walles wrote:
> I still see this just as before (but with 950000 revisions rather than
> 800000).
>
> You probably already thought of this, but have you verified that you
> don't already have a cache for Apache's SVN repo when you try this?
>
> I'm using:
> Bazaar (bzr) 2.1.2
> Python interpreter: /usr/bin/python 2.5.5
> Python standard library: /usr/lib/python2.5
> Platform: Linux-2.6.32-3-686-i686-with-debian-squeeze-sid
> bzrlib: /usr/lib/python2.5/site-packages/bzrlib
> Bazaar configuration: /home/johan/.bazaar
> Bazaar log file: /home/johan/.bzr.log
>
> johan@johansdator:/tmp/hej/maven-scm-1.2$ bzr plugins |grep -A1 svn
> svn 1.0.2
> Support for Subversion branches
>
Please try this with trunk rather than 1.0.2

 status incomplete

Cheers,

Jelmer

Changed in bzr-svn:
status: New → Incomplete
Revision history for this message
Johan Walles (walles) wrote :

I just tried this again with bzr-svn 1.0.3dev and the problem is gone.

Thanks Jelmer!

  Regards /J

Changed in bzr-svn:
status: Incomplete → Fix Committed
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
status: Fix Committed → Fix Released
assignee: nobody → Jelmer Vernooij (jelmer)
milestone: none → 1.0.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.