arv-mount 2.0.1 reported not backwards compatible with 1.4
Some of our automated build machines pull in the latest version of python-arvados-fuse and python-arvados-python-client when they build themselves, which means they're now getting 2.0.1-1 versions of these packages. When we use this version of arv-mount with our cluster the mount appears to work as expected, but any attempt to actually list a collection just leads to an empty directory.
This was intended to work so I'm not sure if this was a oversight in testing or a mistake in cherry-picking into the release branch.
#3 Updated by Tom Clegg over 1 year ago
- Status changed from New to In Progress
16221-arv-mount-api-1.x @ 28014072de9e26a07e943595a6c278148c0bb88d -- https://ci.arvados.org/view/Developer/job/developer-run-tests/1770/