GitHub user Kami opened a pull request:
https://github.com/apache/libcloud/pull/1112
[WIP] Make sure we don't have any files with names longer than 143
characters
It looks like 2.2.0 broke installation on some systems, because we now ship
files with names longer than 143 characters.
Most modern operating systems and file systems support file names with
lengths up to 255 characters, but it looks like using an encrypted file system
(layering ecryptfs on top of ext3/4) drops this limit to 143 characters.
This pull request fixes that and add a CI check which will catch issues
like that in the future.
Resolves https://issues.apache.org/jira/browse/LIBCLOUD-946.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Kami/libcloud use_shorter_fixture_file_names
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/libcloud/pull/1112.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1112
----
commit 60701af4e610b9eeb4e3c60034300148933d69ba
Author: Tomaz Muraus <[email protected]>
Date: 2017-09-19T16:00:09Z
Add a tox check which verifies we don't have any file which name is
longer than 143 characters.
143 characters seems to be the limit for ecryptfs file system layered on
top of ext4.
Source:
https://askubuntu.com/questions/361976/find-files-with-a-minimum-filename-length
Part of LIBCLOUD-946.
commit 942255a6998c37d73cffba8ad90516b34f520c19
Author: Tomaz Muraus <[email protected]>
Date: 2017-09-19T16:14:44Z
Run checks step on Travis CI.
----
---
