Support lightweight checkouts

Also, this recipe is currently failing with the output:

Building the source package
bzr: ERROR: [Errno 2] No such file or directory

...which is very opaque :( Adding --verbose to the command-line doesn't actually produce more output.

On Wed, 30 Dec 2009 20:02:57 -0000, Paul Kishimoto <email address hidden> wrote:
> Also, this recipe is currently failing with the output:
>
> Building the source package
> bzr: ERROR: [Errno 2] No such file or directory
>
> ...which is very opaque :( Adding --verbose to the command-line doesn't
> actually produce more output.

Could you run with -Derror to get a full backtrace?

Thanks,

James

Here you go. I omitted four GPG passphrase prompts.

Building the source package
bzr: ERROR: exceptions.OSError: [Errno 2] No such file or directory

Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 842, in exception_to_return_code
    return the_callable(*args, **kwargs)
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 1037, in run_bzr
    ret = run(*run_argv)
  File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 654, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/builder/__init__.py", line 292, in run
    self._build_source_package(package_dir)
  File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/builder/__init__.py", line 350, in _build_source_package
    stdin=subprocess.PIPE)
  File "/usr/lib/python2.6/subprocess.py", line 621, in __init__
    errread, errwrite)
  File "/usr/lib/python2.6/subprocess.py", line 1126, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory

On Tue, 05 Jan 2010 17:59:36 -0000, Paul Kishimoto <email address hidden> wrote:
> Here you go. I omitted four GPG passphrase prompts.
>
> Building the source package
> bzr: ERROR: exceptions.OSError: [Errno 2] No such file or directory
>
> Traceback (most recent call last):
> File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 842, in exception_to_return_code
> return the_callable(*args, **kwargs)
> File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 1037, in run_bzr
> ret = run(*run_argv)
> File "/usr/lib/python2.6/dist-packages/bzrlib/commands.py", line 654, in run_argv_aliases
> return self.run(**all_cmd_args)
> File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/builder/__init__.py", line 292, in run
> self._build_source_package(package_dir)
> File "/usr/lib/python2.6/dist-packages/bzrlib/plugins/builder/__init__.py", line 350, in _build_source_package
> stdin=subprocess.PIPE)
> File "/usr/lib/python2.6/subprocess.py", line 621, in __init__
> errread, errwrite)
> File "/usr/lib/python2.6/subprocess.py", line 1126, in _execute_child
> raise child_exception
> OSError: [Errno 2] No such file or directory

This is the obscure message you get from python when you run something
with subprocess that isn't installed.

There's a bug that we don't depend on everything we should as well.

I think if you install "devscripts" this will probably go away.

Thanks,

James

As it wound up, I had to install dpatch as well, but after that things went swimmingly. Thanks for the tip! It appears that I was bit before by https://bugs.launchpad.net/bzr-builder/+bug/428722, since I was the one who marked it confirmed—two months ago. Long term memory failure :/

The recipe I am running is now:

$ cat gnucash.recipe
# bzr-builder format 0.2 deb-version 2.3.8+{revno}~ppa{revno:packaging}
lp:gnucash
nest packaging lp:~khaeru/+junk/gnucash-2.3-packaging debian
run ./autogen.sh

...and it's still pulling way too much data. As I said earlier, this should have 'Wishlist' importance.

Hi,

I don't see a problem with adding this. It may be that it turns out not to be much
faster, depending on the operations it ends up doing remotely, as merging will require
pulling down extra data as well.

The best way to find out is to do it though.

To add this you would need to add:

  * An Option to the commands to specify "checkout".
  * checkout=None added to both run() methods in __init__.py.
  * This variable passed down to build_tree()
  * The changes in build_tree() to make checkouts not branches (see cmd_checkout
     in bzrlib/builtins.py in the bzr source for inspriration).
  * Tests, and I would be happy to help work out how to write those.

Thanks,

James

I would say the first step would be to create/use a local copy of the branch referenced by the recipe. On subsequent runs this copy can be updated and then copied (hard linked?) to the build dir for the actual build process.

The lightweight option makes a lot of sense but only for non-merge recipes. (This would actually be really helpful for me too! )

Opinions?

Have you tried running the recipe in a shared repository? That should prevent most of the traffic.

In other words, specify a build location that is under a shared repository:

bzr init-repo /tmp/gnucash
bzr dailydeb gnucash.recipe /tmp/gnucash