The GCM configuration check under Linux falsely assumes that password store is not initialized, when the root directory does not contain the .gpg-id marker.
Even if the git subdirectory contains it, which is all that is needed.
It should not make any claims of itself, but go straight to encoding/decoding a test password, then judge by the results of the process, not by some manual checks that may or may not hold true in all possible configurations.
And yes, this configuration of the store is intentional. The default pass storage directory is merely a pivot point, the actual password stores are pulled in as submodules of it.
The GCM configuration check under Linux falsely assumes that password store is not initialized, when the root directory does not contain the
.gpg-idmarker.Even if the git subdirectory contains it, which is all that is needed.
It should not make any claims of itself, but go straight to encoding/decoding a test password, then judge by the results of the process, not by some manual checks that may or may not hold true in all possible configurations.
And yes, this configuration of the store is intentional. The default pass storage directory is merely a pivot point, the actual password stores are pulled in as submodules of it.