Chris Pahl

Hello @hulkabob, thanks for taking a try and taking time to write a good bug report. Also that's a fun error message. Sadly, neither me or @evgmik are investing time...

Hi @hulkabob > I can file in another bug report for the daemon start, but in a nutshell - it acts like the BRIG_PASSWORD is already set to some random...

Hello @tennox, thanks for your report. Your difficulties seem to arise due to some out dated documentation, since a lot things changed in the ``develop`` branch. Some things are not...

Will check next. > [...] the repo database could be left in a broken state. It should not, [there is some defence](https://github.com/sahib/brig/blob/4ac4c3ce4a16465365696fed7648a76bc82883e9/catfs/core/linker.go#L1744) against crashes in the linker. If the state...

> Looks like Walk get into recursion of some type or maybe adding a child to a parent triggers consequent Walk over itself. IIRC the logic for ``NotifyMove`` was not...

> I would say fs.Copy should preserve the pin status. Yep, it probably should. --- Side note: I'm currently working on re-building ``linker.go`` (...and probably rename it to ``mdag.go``...) to...

> Maybe we should wait until we implement our new 'pin' hints. Agreed.

Cool, thank you @m-a-t! > My first impression was: It's complicated, but seems well thought through. If possible, I would like to find a tool with simpler concepts. But so...

"Now" is still a good point to do it. :smile: Just in case anybody sees this and wants to help by working on a non-coding task.

I welcome that discussion, the whole pinning concept in brig is not perfectly thought throughout and could use a review. > I always thought that explicit stands for keep this...