← Back to team overview

bzr-windows team mailing list archive

Re: Problems with bzr-windows-installers

 

Just to not let this thread die, as I've already explained to Ian this
is not a problem with buildout per se but with the recipe that we are
using and the fact we configured it to be pedantic when changes are
detected. Bear with me as we approach Lucid's release, and I promise
to put some effort in removing all the pain.

On Mon, Apr 12, 2010 at 10:06 AM, Alexander Belchenko <bialix@xxxxxxx> wrote:
> Alexander Belchenko пишет:
>>
>> Ian Clatworthy пишет:
>>>
>>> On 11/04/10 00:51, Alexander Belchenko wrote:
>>>>
>>>> ad\__init__.py", line 65, in calculate_base
>>>> log.error('Unable to strip top level directory because there are more '
>>>> NameError: global name 'log' is not defined
>>>>
>>
>>> I have absolutely *no* idea about this one. I've raised bug #561240.
>>
>> So the problem definitely in hexagonit. It should be updated to latest
>> version. I cannot continue working with bzr-windows-installers stuff while
>> there is such problems.
>>
>> Maybe replacing buildout with something more lightweight and less buggy
>> makes sense?
>
> I have forced to download all svn-related libs manually and put them into
> the place where buildout can find them. After that I've stopped because of
> the absence of sphinx. The buildout don't stop the build even though there
> was no sphinx tool to run. I've installed sphinx with easy_install. And then
> I've hit the wall with following:
>
> C:\work\Bazaar\bzr-windows-installers>py26 build.py --standalone-only
> installers
> Initialising C:\work\Bazaar\bzr-windows-installers\build-win32 directory
> Running c:\Python26\python.exe bootstrap.py ...
> Generating buildout configuration for bzr-2.2 ...
> Generating buildout-bzr-2.2.cfg in .
> Running bin\buildout -c buildout-bzr-2.2.cfg ...
> c:\work\bazaar\bzr-windows-installers\build-win32\eggs\hexagonit.recipe.download-1.2.2-py2.6.egg\hexagonit\recipe\download\__ini
> t__.py:5: DeprecationWarning: the md5 module is deprecated; use hashlib
> instead
>  import md5
> Uninstalling qbzr.
> Running uninstall recipe.
> Uninstalling bzr-xmloutput.
> Running uninstall recipe.
> bzr-xmloutput: Abort uninstalling "bzr-2.2" (push or adjust push location?),
> detailed output follows:
> """
> Branches are up to date.
>
> Connected (version 2.0, client Twisted)
> Authentication (publickey) successful!
> Secsh channel 1 opened.
> """
> While:
>  Installing.
>  Uninstalling bzr-xmloutput.
> Error: Abort uninstalling, because of pending local changes.
>
> I've got the same error first with qbzr, but there was no local changes.
> I've deleted qbzr directory and then got the same with xmloutput.
>
> There is enough hassles for me for today.
>
> I'd like to vote to title buildout the worst ever tool to build bzr windows
> installers. Yes, of course, when I've maintained bzr windows installers
> there was no bzr-svn stuff, not TortoiseBrz. But what I see today is
> constant pain in the ass for me. I don't have so much free time to debug and
> fix every possible problem in buildout itself. If I can do the installer
> build manually -- then I'd better to do it manually. It will be much faster
> for me.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~bzr-windows
> Post to     : bzr-windows@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~bzr-windows
> More help   : https://help.launchpad.net/ListHelp
>



Follow ups

References