Closed jhautefeuille closed 1 year ago
Hi, Why don't you comment a little more in this issue? For anybody to be able to help, more info is needed.
Kind regards
I have no idea what is going on here. Can you show the output of
go version
?
julien@pop7550:~/Téléchargements/gocryptfs$ ./build-without-openssl.bash
# github.com/rfjakob/gocryptfs/v2
./help.go:15:2: undefined: printVersion
./help.go:50:2: undefined: printVersion
./init_dir.go:98:39: undefined: GitVersion
./main.go:158:3: undefined: printVersion
./main.go:168:3: undefined: printVersion
julien@pop7550:~/Téléchargements/gocryptfs$ go version
go version go1.20.4 linux/amd64
So looks like https://github.com/rfjakob/gocryptfs/issues/735 and this issue is really the same issue, which is the 143-byte limit for filenames on ecryptfs.
0 jakob@brikett:/mnt/ecryptfs/b$ git clone git@github.com:rfjakob/gocryptfs.git
Cloning into 'gocryptfs'...
remote: Enumerating objects: 12528, done.
remote: Counting objects: 100% (2471/2471), done.
remote: Compressing objects: 100% (810/810), done.
remote: Total 12528 (delta 1677), reused 2278 (delta 1611), pack-reused 10057
Receiving objects: 100% (12528/12528), 5.67 MiB | 6.27 MiB/s, done.
Resolving deltas: 100% (8689/8689), done.
error: unable to create file tests/example_filesystems/content/longname_255_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: File name too long
error: unable to create file tests/example_filesystems/v1.1-reverse-plaintextnames/longname_255_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: File name too long
error: unable to create file tests/example_filesystems/v1.1-reverse/longname_255_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: File name too long
error: unable to create file tests/example_filesystems/v1.3-reverse/longname_255_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: File name too long
error: unable to create file tests/reverse/ctlsock_reverse_test_fs/dir/longfile.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx: File name too long
fatal: cannot create directory at 'tests/reverse/ctlsock_reverse_test_fs/longdir.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx': File name too long
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
128 jakob@brikett:/mnt/ecryptfs/b$ cd gocryptfs/
0 jakob@brikett:/mnt/ecryptfs/b/gocryptfs$ ./build.bash
# github.com/rfjakob/gocryptfs/v2
./help.go:15:2: undefined: printVersion
./help.go:50:2: undefined: printVersion
./init_dir.go:98:39: undefined: GitVersion
./main.go:158:3: undefined: printVersion
./main.go:168:3: undefined: printVersion
And "git status" tells us that everything is messed up badly:
Long story short, when using ecryptfs for your home dir, and you want to "git clone" gocryptfs, please do it on /tmp
or something.
Alternatively, download the tar.gz source code release ( https://github.com/rfjakob/gocryptfs/releases/download/v2.3.2/gocryptfs_v2.3.2_src.tar.gz ), ignore the errors on extraction, and it will compile successfully. The "file name too long" thing only affects the test suite, but not gocryptfs itself.