Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot tag / add attribute to permanode #1390

Open
basilboli opened this issue Mar 29, 2021 · 1 comment
Open

Cannot tag / add attribute to permanode #1390

basilboli opened this issue Mar 29, 2021 · 1 comment

Comments

@basilboli
Copy link

While creating new permanode I cannot add tag or attribute:

How to reproduce

➜  Documents X=$(pk-put permanode)
2021/03/29 17:04:34 Warning: client (B8C50EAF) and server (AF5FD483) keys differ.
➜  Documents echo $X
sha224-c8a67d43b29d899facf85a38b115c24fa33ebaa5322ac6696a93fb9f
➜  Documents pk-put attr $X title "Some title"
2021/03/29 17:04:58 Warning: client (B8C50EAF) and server (AF5FD483) keys differ.
sha224-b7e6de57cf280a9a2fcb70937fe75aa7de2a14084e972f8f6f4a00d5
➜  Documents pk-put attr $X title "Better title"
2021/03/29 17:05:09 Warning: client (B8C50EAF) and server (AF5FD483) keys differ.
sha224-83c31680b3696d5785394957346f89ddc04c4070356483b817efa9b1
➜  Documents pk describe sha224-c8a67d43b29d899facf85a38b115c24fa33ebaa5322ac6696a93fb9f
{
  "meta": {
    "sha224-c8a67d43b29d899facf85a38b115c24fa33ebaa5322ac6696a93fb9f": {
      "blobRef": "sha224-c8a67d43b29d899facf85a38b115c24fa33ebaa5322ac6696a93fb9f",
      "camliType": "permanode",
      "size": 626,
      "permanode": {
        "attr": {},
        "modtime": "0001-01-01T00:00:00Z"
      }
    }
  }
}
➜  Documents pk claims sha224-c8a67d43b29d899facf85a38b115c24fa33ebaa5322ac6696a93fb9f
{
  "claims": null
}
➜  Documents 

I expect attribute and claims fields not to be empty.

Version

perkeep server version
https://perkeep.org/doc/release/0.11
perkeep client version
https://perkeep.org/doc/release/0.11

Have anyone had the similar problem?
Thanks in advance.

P.S. Kudos and thanks for doing this amazing project.

@basilboli
Copy link
Author

Ok, I have actually solved the problem by myself by:

1/ copying identity-secring.gpg from the machine running perkeep server to the machine running the client
2/ pk-put init -gpgkey XXXX using the same key id XXXX as the server

I don't know whether this is the right thing to do but it was not quite obvious from the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant