bzr-packagers team mailing list archive

[Sidnei da Silva <sidnei.da.silva@xxxxxxxxxxxxx>]

On Thu, Mar 25, 2010 at 5:55 AM, Ian Clatworthy
<ian.clatworthy@xxxxxxxxxxxxx> wrote:
> Sidnei,
>
> When I try to build 2.2 after building 2.1 on desolution, I get a weird
> buildout error something like ...
>
> Uninstalling qbzr.
> Runing unistall recipe.
> qbzr: Abort uninstalling "bzr-2.1" (...) ...
> """
> modified:
>  po/qbzr-en.po
> """
> While
>  Installing.
>  Uninstalling qbzr.
> Error: Abort uninstalling, because of pending local changes.
>
>
> This only happen if I try building 2.2 using Python 2.5 (because 2.1 was
> built using 2.5 I assume).
>
> How do I fix this? How do I prevent it from happening in the future?
> (I'm hoping there's some magic buildout setting that makes this issue go
> away?)

The problem is that there's a file being tracked by bzr that has been
modified (ignored files are fine). The buildout recipe is configured
to bail out when trying to delete modified files to avoid losing work,
which is a nice safeguard. If you don't care about that we could
disable this check. Alternatively we could 'bzr revert' as the first
step?

-- Sidnei