Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2025-07-07T17:59:35+00:00 2025-07-07T17:59:35+00:00 Jakob Unterwurzacher 2025-07-07T17:54:48+00:00 urn:sha1:8f5df19b353e02ffba842fd1b15ccf93da7ee3b4 Tool-assisted. 2021-08-23T13:05:15+00:00 Jakob Unterwurzacher 2021-08-23T13:05:15+00:00 urn:sha1:69d88505fd7f4cb0d9e4f1918de296342fe05858 Our git version is v2+ for some time now, but go.mod still declared v1. Hopefully making both match makes https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2 work. All the import paths have been fixed like this: find . -name \*.go | xargs sed -i s%github.com/rfjakob/gocryptfs/%github.com/rfjakob/gocryptfs/v2/% 2019-12-23T23:38:40+00:00 Jakob Unterwurzacher 2019-12-23T23:38:40+00:00 urn:sha1:7dda2363e1f8d30d5ebce5b6279452a2cf1bb77a Move the statusTxtContent to fix this confusing error when running `go get github.com/rfjakob/gocryptfs/...`: $ go get github.com/rfjakob/gocryptfs/... # github.com/rfjakob/gocryptfs/tests/example_filesystems tests/example_filesystems/example_test_helpers.go:22:16: undefined: statusTxtContent tests/example_filesystems/example_test_helpers.go:75:16: undefined: statusTxtContent 2017-03-05T12:39:25+00:00 Jakob Unterwurzacher 2017-03-05T12:39:25+00:00 urn:sha1:b2f154a9a908e6ec097de90c04ce45118adc76de Calling t.Fatal immeadiately aborts the test, which means the filesystem will not get unmounted, which means test.bash will hang. 2016-11-26T14:20:54+00:00 Jakob Unterwurzacher 2016-11-26T14:17:15+00:00 urn:sha1:3f5c48e0585f6fe0782aded541e42879eb570e69 Calling t.Fatal means that the parent test has no chance to clean up. 2016-10-08T19:45:11+00:00 Jakob Unterwurzacher 2016-10-08T19:45:11+00:00 urn:sha1:eb51a1ed20696460a9cdab2caa8f5d6e1e8dee04 2016-06-26T16:34:30+00:00 Jakob Unterwurzacher 2016-06-26T16:34:30+00:00 urn:sha1:1de5ceed586335361baae02160d61400fbf71e15 This file was forgotten in commit "tests: make tests for unsupported FSs more compact".