kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

A new version of KiCad-Winbuilder will be released in the next few
days. I haven't tried it since the change to product from testing, but
there will only be a few references to testing, if any.

The new version includes the library from github, and has wxPython 3 +
a few patches.

Best Regards,

Brian.

On 20 January 2014 21:33, Travis Ayres <trayres@xxxxxxxxx> wrote:
>>>You can probably still use the same computer though :)
>
> Haha thanks Dick :) I appreciate it.
>
>
> On Mon, Jan 20, 2014 at 11:51 AM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
>>
>> On 01/20/2014 01:32 PM, Travis Ayres wrote:
>> > My branch.conf file:
>> >
>> > parent_location =
>> > http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/
>> > bound_location =
>> > http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/
>> > bound = True
>> >
>>
>>
>> When I said run
>>
>> $ bzr bind lp:kicad
>>
>> I meant in the kicad source working tree, not in the winbuilder working
>> tree.
>>
>> You evidently have two working trees with a winbuilder setup, and now the
>> winbuilder tree
>> is broken, so you are doubly broke.
>>
>> Fixing the winbuilder tree:
>>
>> $ cd <winbuilder tree>
>> $ bzr bind
>> http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/
>>
>>
>> Fixing the kicad source tree:
>>
>> $ cd <kicad src tree>
>> $ bzr bind lp:kicad
>>
>> After both are fixed, you have a prayer.  If this does not work, I am out
>> of ideas.  Start
>> over is what I would say.  You can probably still use the same computer
>> though :)
>>
>>
>>
>>
>>
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>