[Twisted-Python] How to set up Twisted buildbot VM?
![](https://secure.gravatar.com/avatar/469df05f5dfd5b75fb3cb3a0868d36bf.jpg?s=120&d=mm&r=g)
Hi, I tried to set up a VM to test changes to Twisted's buildbot. I did this: git clone https://github.com/twisted-infra/braid cd braid vagrant up fab config.vagrant fab config.vagrant base.bootstrap fab config.vagrant buildbot.install I got some errors at this point (see attached log). Any ideas how to get this working? Thanks. -- Craig
![](https://secure.gravatar.com/avatar/c194a4d2f2f8269aa052942e87985198.jpg?s=120&d=mm&r=g)
On 22 June 2017 at 09:44, Craig Rodrigues <rodrigc@crodrigues.org> wrote:
I am not a python packages expert, but it looks like the `pbr` lib has some errors. And pbr was installed due to `mock`. I think that you can try pinning an older version of the `pbr` or of `mock`. For production usage, I think that we should pin everything, so that we don't end up with things which might break in the future. Cheers, Adi
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
Very much agreed. As per https://caremad.io/posts/2013/07/setup-vs-requirement/ <https://caremad.io/posts/2013/07/setup-vs-requirement/>, any actual deployments need to have "exact version specifiers" (i.e.: pins) on everything. -g
![](https://secure.gravatar.com/avatar/469df05f5dfd5b75fb3cb3a0868d36bf.jpg?s=120&d=mm&r=g)
I found this particular problem was due to the fact that if I followed the instructions in the braid README, pip version 1.0 is installed on the system. This is a really ancient version of pip, and installing the latest versions of mock and pbr fail with it. -- Craig On Thu, Jun 22, 2017 at 1:44 AM, Craig Rodrigues <rodrigc@crodrigues.org> wrote:
![](https://secure.gravatar.com/avatar/c194a4d2f2f8269aa052942e87985198.jpg?s=120&d=mm&r=g)
On 22 June 2017 at 09:44, Craig Rodrigues <rodrigc@crodrigues.org> wrote:
I am not a python packages expert, but it looks like the `pbr` lib has some errors. And pbr was installed due to `mock`. I think that you can try pinning an older version of the `pbr` or of `mock`. For production usage, I think that we should pin everything, so that we don't end up with things which might break in the future. Cheers, Adi
![](https://secure.gravatar.com/avatar/e1554622707bedd9202884900430b838.jpg?s=120&d=mm&r=g)
Very much agreed. As per https://caremad.io/posts/2013/07/setup-vs-requirement/ <https://caremad.io/posts/2013/07/setup-vs-requirement/>, any actual deployments need to have "exact version specifiers" (i.e.: pins) on everything. -g
![](https://secure.gravatar.com/avatar/469df05f5dfd5b75fb3cb3a0868d36bf.jpg?s=120&d=mm&r=g)
I found this particular problem was due to the fact that if I followed the instructions in the braid README, pip version 1.0 is installed on the system. This is a really ancient version of pip, and installing the latest versions of mock and pbr fail with it. -- Craig On Thu, Jun 22, 2017 at 1:44 AM, Craig Rodrigues <rodrigc@crodrigues.org> wrote:
participants (3)
-
Adi Roiban
-
Craig Rodrigues
-
Glyph