Re: [Kicad-developers] testing has been renamed to product

2014-01-23 Thread Travis Ayres
I tried using "bzr branch lp:kicad-winbuilder"
but I run into problems - however the 3.2 archive on the kicad-winbuilder
site gets me closer, but still no joy currently.

Hmm.



On Tue, Jan 21, 2014 at 1:32 AM, Brian Sidebotham <
brian.sidebot...@gmail.com> wrote:

> 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  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 
> 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 
> >> $ bzr bind
> >> http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/
> >>
> >>
> >> Fixing the kicad source tree:
> >>
> >> $ cd 
> >> $ 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@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] testing has been renamed to product

2014-01-21 Thread Brian Sidebotham
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  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  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 
>> $ bzr bind
>> http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/
>>
>>
>> Fixing the kicad source tree:
>>
>> $ cd 
>> $ 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@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] testing has been renamed to product

2014-01-20 Thread Travis Ayres
>>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  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 
> $ bzr bind
> http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/
>
>
> Fixing the kicad source tree:
>
> $ cd 
> $ 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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] testing has been renamed to product

2014-01-20 Thread Dick Hollenbeck
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 
$ bzr bind http://bazaar.launchpad.net/~brian-sidebotham/kicad-winbuilder/trunk/


Fixing the kicad source tree:

$ cd 
$ 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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] testing has been renamed to product

2014-01-20 Thread Travis Ayres
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



On Mon, Jan 20, 2014 at 11:01 AM, Dick Hollenbeck  wrote:

> On 01/20/2014 12:42 PM, Travis Ayres wrote:
> > I'm getting:
> > ERROR Updating source code!
> > ERROR Bazaar said: bzr: ERROR: Not a branch: "
> http://bazaar.launchpad.net/~kicad
> > -testing-committers/kicad/testing/".
> >
> > I thought it might be this change, but you're right about lp:kicad being
> treated like a
> > symlink and thus giving some amount of immunity.
> >
> > Unfortunately now I'm not sure where the error is coming from.
>
>
> After following the instruction in my email, which were:
>
>
> $ bzr bind lp:kicad
>
>
> It should work.
>
> If not, then attach your branch.conf file to the developer's mailing list.
>
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] testing has been renamed to product

2014-01-20 Thread Dick Hollenbeck
On 01/20/2014 12:42 PM, Travis Ayres wrote:
> I'm getting:
> ERROR Updating source code!
> ERROR Bazaar said: bzr: ERROR: Not a branch: 
> "http://bazaar.launchpad.net/~kicad
> -testing-committers/kicad/testing/".
> 
> I thought it might be this change, but you're right about lp:kicad being 
> treated like a
> symlink and thus giving some amount of immunity. 
> 
> Unfortunately now I'm not sure where the error is coming from. 


After following the instruction in my email, which were:


$ bzr bind lp:kicad


It should work.

If not, then attach your branch.conf file to the developer's mailing list.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] testing has been renamed to product

2014-01-20 Thread Dick Hollenbeck
On 01/20/2014 12:08 PM, Travis Ayres wrote:
> I think this renaming has broken Brian's Kicad Winbuilder scripts.


That's very possible.  I don't have commit rights to his winbuilder, but he is 
on the
mailing list so he should have received the notification.

It can't be more than a line or two.

Using lp:kicad in references to this branch gives some amount of immunity, as 
that
"lp:kicad" seems to be treated like a symlink at launchpad.  This "sym-linking 
like"
behaviour may be new however within bzr or launchpad.






___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


Re: [Kicad-developers] testing has been renamed to product

2014-01-20 Thread Dick Hollenbeck


> Wayne and Jean-Pierre may identify periods of quiet, or increased reliability 
> within the
> product branch, so that you can take your production snapshots during those 
> periods.


bzr supports revision "tagging", which if hypothetically done at that same 
point in time
where one used to take "stable" snapshots of "testing", leads to an equivalent 
set of
recommended revisions from which one could take snapshots *at any point in 
time* for
production use.



Dick



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp