[users at bb.net] Buildbot on Mac OS X

[Pierre Tardy]

Le mer. 27 janv. 2016 01:18, Craig Treleaven <ctreleaven at cogeco.ca> a
écrit :

> Thanks, I’ll keep an eye out for the release.
>
> BTW, will 0.9 ‘workers’ be compatible with 0.8.x masters?
>

Unfortunately this is not a goal. The package name will be different so you
can install 0.8 and 0.9 version in the same environment


Craig
>
> On Jan 26, 2016, at 5:42 PM, Pierre Tardy <tardyp at gmail.com> wrote:
>
> I just tried to upgrade and look at the tests, and created a report in the
> following trac:
>
> http://trac.buildbot.net/ticket/3425#ticket
>
> I dont think it should be so hard to fix
>
> Le mar. 26 janv. 2016 à 23:28, Pierre Tardy <tardyp at gmail.com> a écrit :
>
>> Le mar. 26 janv. 2016 à 21:49, Craig Treleaven <ctreleaven at cogeco.ca> a
>> écrit :
>>
>>> Just to be clear, two of us from the MacPorts project have said that we
>>> want to fix our port.  It appears that a fork of sqlalchemy-migrate has
>>> emerged that (presumably) works with current versions of sqlalchemy.  (With
>>> Python 3 support, I believe.)
>>>
>>
>> I Craig, I did not realize you were part of the macport team, and didn't
>> want to be rude.
>>
>>
>>> Surely the Buildbot project would want to move forward with a module
>>> that is being supported rather than stick with an old version?  If that
>>> fork is incompatible with Buildbot, perhaps there is another, better
>>> version?
>>>
>> It is very hard for us to keep up with the evolution of all our
>> dependencies, we get more or less 1 regression every other month because a
>> dependency incompatible change.
>> We try to change our code in order to be compatible, but sometimes it
>> looks like too much work so we just lazily add a rule in our setup.py to
>> enforce that this or that dependency is fixed to a particular version.
>>
>> Looking at setup.py only the following package have restrictions:
>>         'sqlalchemy >= 0.6, <= 0.7.10',
>>         'sqlalchemy-migrate==0.7.2',
>>         'pylint==1.1.0',
>>
>> We know that this is not very cool for our distro package maintainers,
>> but as virtualenv is so easy to use, and resolves the python dependency
>> hell so well for us, its hard for us to find the motivation to resolve
>> those bugs.
>>
>>
>> I’m not a Python guy—I’ve essentially gone down the rabbit hole trying to
>>> set up an OS X builder for MythTV.
>>>
>>
>> If this is only that, you can safely install a buildbot "slave" (will
>> soon be renamed as "worker") package only, which has much less dependencies.
>>
>>
>>> ‘virtualenv’ is just another layer between me and the problem that I’d
>>> rather be solving.  It looks like I’m going to go that way for the sake of
>>> testing my build-slave but I do want to fix our buildbot port.
>>>
>>
>> I am not exactly sure how hard it will be to fix buildbot to release the
>> restriction on sqlalchemy, as this is the db part, everybody is a little
>> bit scary touching that.
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.buildbot.net/pipermail/users/attachments/20160127/f75153de/attachment.html>