One golang standalone module can exists inside another module, when we replace such module to local directory, we'll try to create symbolic link inside the source directory and ln complains permission denied.
For example, both cosmossdk.io/x/accounts and cosmossdk.io/x/accounts/defaults/lockup are standalone modules, if we do replace cosmossdk.io/x/accounts => ./x/accounts, we'll try to create two symbolic links like this:
And the second one is inside source directory and fails.
The temporary solution here is to simply ignore the symbolic link error, not ideal, but fix the issue at hand, and should have no side effect on existing projects.
One golang standalone module can exists inside another module, when we replace such module to local directory, we'll try to create symbolic link inside the source directory and
lncomplains permission denied.For example, both
cosmossdk.io/x/accountsandcosmossdk.io/x/accounts/defaults/lockupare standalone modules, if we doreplace cosmossdk.io/x/accounts => ./x/accounts, we'll try to create two symbolic links like this:And the second one is inside source directory and fails.
The temporary solution here is to simply ignore the symbolic link error, not ideal, but fix the issue at hand, and should have no side effect on existing projects.