openerp-community team mailing list archive

[Georges Racinet <gracinet@xxxxxxxxx>]

Hi Sandy,

sorry for the delay

On 03/24/2014 10:08 PM, Sandy Carter wrote:
> Hi,
> 
> I have a feature request of sorts for anybox.recipe.openerp:
> 
> Often times, when developping, we will change branches of certain repos
> as our projects progress. This happens, for example after a merge.
> 
> What happens in cases like that is that the buildout will either not
> take in all the commits from the new branch or will fail with the
> following error:
> 
> UpdateError: Command '['bzr', 'pull', '-d', 'bzr/addons']' returned
> non-zero exit status
> 
> I beleive this can avoided entirely if the --overwrite flag is used.
> The pull call happens in vcs/bzr.py L293:
>             update_check_call(['bzr', 'pull', '-d', self.target_dir],
>                               env=SUBPROCESS_ENV)
> 
> It would be helpful to either have the option to set the --overwrite
> flag, or to have it one by default.
> 
> What do you think?

I believe what you suggest could be expressed as an option on the addon
definition (bzr-init=... or bzr-update=...).

On the other hand, there is already some handling of the change of
parent branch, see the will-never-be-finished
https://bugs.launchpad.net/anybox.recipe.openerp/+bug/1008931 : the
examples are written for hg, but I believe the case is really close.
This is delicate stuff, because we don't want developers to lose their work.

Maybe the branch.conf handling methods BzrBranch.read_conf() and
write_conf() can take care of this automatically.

In any case, would you be so kind to create an issue on the launchpad
bugtracker ?

Thanks,


-- 
Georges Racinet
Anybox SAS, http://anybox.fr
Bureau: 09 72 39 50 97 / 09 72 39 13 06
Portable: 06 51 32 07 27
GPG: 0x33AB0A35, sur serveurs publics

Attachment: signature.asc
Description: OpenPGP digital signature