Ilari Korhonen

Hi, 1) Looks like it. 2) The names in the vault(s) seem to be consistent but the troubling thing is the sharing of the `DATA_ID` identifier. 3) Thought so, hence...

Hello, Thanks for your report. I haven't actually tested the 1.0.7 release of the irodsclient on OS X 10.11 at all, so it's good to know that it doesn't work...

Ok, now that's interesting. Good to know! It might be that the 1.1.0b1 might fix his issues as well, since it builds against the newer openssl-1.1.0 libraries from the homebrew...

This is curious. I'm currently using the same build here with SSL support fully functional. Are you sure that in the certificate chain there isn't any signers that would require...

Hi, Sorry I forgot to comment on this earlier. Will start again working on a release, and will fix all these that have been hanging. Thanks for the report!

Hi, Thanks for the report. I don't think you missed anything, I haven't compiled it on Ubuntu 16.04 yet myself, will do so soon. I'll let you know as soon...

Thanks for the reminder! It’s been (too) busy, will get on this right now. Stay tuned. > On 20 Nov 2018, at 10:40, Vojtech Moravec wrote: > > Any update?...

The code from the `master` branch seems to build fine on Ubuntu 16.04 using the same recipe as with 14.04. The `develop` branch is another story, I'll have to get...

Hi, We currently use the iRODS built-in (synchronous) replication triggered by the `replication` resource plugin. In the previous test I believe the `rodsresc2Resource` was the destination resource to which the...

I have now tried to make a more rigorous test which should be fully reproducible from the steps below. 1. Create test cluster ``` $ git clone https://github.com/KTH-PDC/irods-provisioner.git -b 4-1-stable...