diracos2/libcloud/conda forge

[Daniela Bauer]

Hi All and especially Chris B,

While this is a specific example, the problem might be more general.

Simon and me are working on integrating the Cloud as a 'standard' ComputingElement.

For this to work, we submitted a patch for libcloud (and we may have more patches for libcloud in the future). This patch went into libcloud in November in version 3.4.0

However it looks like the automated pull requests in conda fail due to a linting error <decided eye roll> and it looks like no-one is looking at them:

https://github.com/conda-forge/apache-libcloud-feedstock/pulls

How is this meant to work ?

So, in step 2, we tried updating it with pip install (to 3.5.1). This only worked if we updated the rucio-clients to 1.28.0 at the same time as otherwise 'requests' would have been incompatible (though it looks like rucio is about to be updated in conda-forge).

Simon thinks I should wait a couple of days so at least the rucio request goes through on conda-forge, but I'm a bit concerned that code we wrote in August last year still hasn't appeared in the dependencies.

In  a tangentially related question:

Could someone retrigger the test on this pull request:

https://github.com/DIRACGrid/DIRAC/pull/5988

as conda forge seemed to have issues on the day we submitted it.

Regards,

Daniela