search

signet-org / signet-python

A decentralized code signing network
MIT License
23 stars 1 forks source link

After rm -rf ~/.signet/remotes/myRemoteName, reference still exists #7

Closed dmvaldman closed 8 years ago

dmvaldman commented 8 years ago

After rm -rf ~/.signet/remotes/keybase and adding a new remote with the same name, I get the warning

warning A remote named "keybase" already exists. Skipping.

chromakode commented 8 years ago

Thanks, I'll look into this and add some tests.

chromakode commented 8 years ago

Ah, I think I may know what is going on here. If you run sig list you'll see that there is still a remote entry for "keybase". Remotes are stored in the main configuration file, ~/.signet/config. Removing the remote directory doesn't remove the configured remote -- you have to sig remote remove keybase as well.

I recommended to remove the directory in my tweet because there was another issue that would cause sig to crash on startup if remote repo files weren't valid JSON.

Does this clarify what you're experiencing? Does the behavior of managing remotes with sig remote add/sig remote remove make sense?

dmvaldman commented 8 years ago

Ah yes, makes total sense and fixed my issue. Thanks!