On 07/06/2013 04:34 PM, Dimitris Moraitis wrote:
We met with Simone in EuroPython and solved this issue. The pycrypto
version of the standalone buildout was 2.5 instead of 2.4.1 which is
required by collective.transcode.daemon
Yep! Anyway, as long as the daemon works only with that version I think
we should no rely on buildout pinning. Wouldn't be better to pin it from
setup.py?
Then when it will be made compatible with both releases we can drop the
pin.
What do you think?
PS @Dimo: has been pleasure and fun to meet you in Florence! Good luck
w/ mist.io and tnx for all the work on Plumi :)
On 2013-07-01 13:31, Dimitris Moraitis wrote:
On 2013-07-01 13:32, Simone Orsi wrote:
On 07/01/2013 12:14 PM, Dimitris Moraitis wrote:
That's weird. Are you using a standalone transcode.daemon
buildout?
yes, that's what I meant with "I setup a transcoder instance on a
separate machine." :)
I splitted out the transcoder part of the buildout (to be shared
soon ;)).
There is already a standalone collective.transcode.daemon buildout.
Maybe you can try using this one:
https://github.com/plumi/collective.transcode.daemon
--
https://unweb.me
_______________________________________________
Discuss mailing list
[email protected] <mailto:[email protected]>
http://lists.plumi.org/listinfo/discuss
--
https://unweb.me
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
_______________________________________________
Discuss mailing list
[email protected]
http://lists.plumi.org/listinfo/discuss
