On 07/05/2011 07:48 AM, Radu-Cristian FOTESCU wrote:
Sorry for messing with an issue I am not familiar with, but AFAICT python-coherence was last built on Mon 21 Feb 2011, so I see no reason why this should only manifest now!
Yes, I noticed the package date, and the behavior is probably unrelated to the coherence packages themselves, but I don't know enough about Coherence to guess at what else may be in play here.
