On Fri, May 25, 2018 at 2:54 PM, Matthias Teege <[email protected]> wrote:
> On Fri, May 25, 2018 at 06:06:46PM +0200, Mathieu Lonjaret wrote: > > Hi, > > > > No, I did not copy the GPG key from the old setup. My goal is to > > > Long story short, if you've lost your old GPG keys you still have your > > contents/files/data, but you'll have to recreate all the permanodes > > for them with the new GPG key. > > Thank you for clarifying. Is it possible to use more then one > identity on a single perkeep instance? > > > > 2018/05/25 15:57:51 Reindexing at sha1-f1721c26cc21b41f41be41ef376b02 > 38fa6a37fe > > > 2018/05/25 15:57:52 Reindexing at sha1-fa8f698d8452a7fc752c5a36e8e7a1 > 9326cc4999 > > > 2018/05/25 15:57:53 Index rebuild complete. > > > > yeah I would guess these are only the blobs your created with the new > > GPG identity. > > Hmm, the new instance was almost empty and IMHO uses sha-224 as > default. I've copied the old identify to the new server. Starting > perkeepd gives me: > > 2018/05/25 23:04:31 Rebuilding index... > > 2018/05/25 23:04:31 Reindexing at > sha1-00010ede8ad52b7058b0f13edda52e9e507aa9a5 > > 2018/05/25 23:04:32 Reindexing at > sha1-0b99792ba9b537fa3622da2346f72d5f9e8dba7f > > 2018/05/25 23:04:33 Reindexing at > sha1-14d61d0fc34249b8eb7b7c74b7c8d348c6c74433 > > 2018/05/25 23:04:34 Reindexing at > sha1-181456b2020e2ce506fd7499f60c705f2574a87b > > 2018/05/25 23:04:35 Reindexing at > sha1-23c4eca8533e2ccb45b9d5847e722c0c246eecd4 > > 2018/05/25 23:04:36 Reindexing at > sha1-2ef4791b2fb5f75d459c6f77293bfdbdab52bf2a > > 2018/05/25 23:04:37 Reindexing at > sha1-37a84014711bfb20d5ddffc3512e1deba2d5eac6 > > 2018/05/25 23:04:38 Reindexing at > sha1-3f798547f2e8390059d7d9ea0794cc6c26544c0b > > 2018/05/25 23:04:39 Reindexing at > sha1-485fd48855dbdaad37136dacd677960804559b6d > > 2018/05/25 23:04:40 Reindexing at > sha1-52cf179d7a859e99bda3c8b60abbd1a7290ec2cf > > 2018/05/25 23:04:41 Reindexing at > sha1-5d151bb17854d334983ab1282a1f557e09ee7574 > > 2018/05/25 23:04:42 Reindexing at > sha1-6777b372275c63f2cb5b065997f975cb146de318 > > 2018/05/25 23:04:43 Reindexing at > sha1-7321695a0a96675daea6b797f88ff09c9fa16cc6 > > 2018/05/25 23:04:44 Reindexing at > sha1-77cabbdf1c8e9b14028a7aa1b8b9b4b3c30de2d1 > > 2018/05/25 23:04:45 Reindexing at > sha1-82365f43b8decb3b8d27ad525e0b16ffed778ee6 > > 2018/05/25 23:04:46 Reindexing at > sha1-8d2be4d6240f9ba09919cf4fa25b195c2edbed2d > > 2018/05/25 23:04:47 Reindexing at > sha1-95d6ae4d75aea7e87fb25e9c459855a2deb88aa1 > > 2018/05/25 23:04:48 Reindexing at > sha1-9f2056294c8ca7e090c773b2c1c1df4832debc44 > > 2018/05/25 23:04:49 Reindexing at > sha1-a7c8ed7152ae01550a6d2514e2a890cf3eaf1896 > > 2018/05/25 23:04:50 Reindexing at > sha1-b07eed218c799119aa90de682d396669bcd4eec5 > > 2018/05/25 23:04:52 Reindexing at > sha1-b9de4448fd0f4b0e2cfa81c1322fd948cc0ce8e9 > > 2018/05/25 23:04:53 Reindexing at > sha1-c3ef5caf71ab2b4c82e144092e205ae9f54efc92 > > 2018/05/25 23:04:54 Reindexing at > sha1-cc4b61649d4975d40fd3c52fb92c1107ca1c4e13 > > 2018/05/25 23:04:55 Reindexing at > sha1-d545959e2c0b349cb3df568190734f15abba0689 > > 2018/05/25 23:04:56 Reindexing at > sha1-decccf7b5df4ed52af02c4b4e49421b41f57ca82 > > 2018/05/25 23:04:57 Reindexing at > sha1-e70c1ffab2668845a68caff5a26a98b3564b63ba > > 2018/05/25 23:04:58 Reindexing at > sha1-efe29d61f9e4de554c9950d7ea661e5cba61646d > > 2018/05/25 23:04:59 Reindexing at > sha1-f8087c1297b1fa2c40ab531214fe8d5a0363e9a3 > > 2018/05/25 23:05:00 Index rebuild complete. > 2018/05/25 23:05:00 index/corpus: loading into memory... > > There are more the 100000 blobs. Shouldn't I see each blob during > a reindexing? > It's just showing where it's "at" periodically. Note that the log lines are each 1 second part. -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
