git ssb

16+

cel / patchfoo



Commit e8c2eb2a9f3c9a25df5ee189740641ff96fc6ba7 renders the project further unable to be built, as the referenced pa...

%Q8uSiDrcJNhZKdjQQy3k5hhhsyg9mlU5ssPxniGYUt0=.sha256
Closedkode54 opened this issue on 6/15/2018, 5:48:47 AM

Commit e8c2eb2a9f3c9a25df5ee189740641ff96fc6ba7 renders the project further unable to be built, as the referenced packages don't appear to exist in those versions in any of the repositories yet. Maybe I should wait a few more hours and try again?

%p0z6uv1S/MI5sryfsgPeVrG4R2C1ROnQnqvMicUd7NY=.sha256 kode54 · 6/15/2018, 5:49:56 AM

Upstream npm is missing ssb-contact@^1.2.0, ssb-npm is missing ssb-mentions@^0.5.0.

%BgTWMLOJm5NI4sFuEzPym3XcfWAH+fMVmcI7Xrapeyg=.sha256 cel · 6/15/2018, 1:58:51 PM

@kode54 sorry about that. migrated ssb-mentions 0.5.0 to ssb-npm now: %xGyt8/z...

%Qdxo8EmEB05QaZsgY1LOKqPnjCPBjX6BzlBTYQx4msY=.sha256 kode54 · 6/16/2018, 5:32:22 AM

Maybe next, you can tell me who I need to follow or which blobs I need to blobs.want to get sodium-native to install via ssb-npm, since that's my last hangup to getting Patchfoo working.

%O11j9f+89RfCBWhgbHyQliE97GIlWcC6DxJLCAG7lMs=.sha256 kode54 · 6/16/2018, 6:22:14 AM

Disregard that, it was due to a stale package-lock.json... Should I submit a pull request with the one I generated?

%4i9Cv9J0xi3sHIBcrioL/77lM8ZCDmlJZLnl9/0UVOE=.sha256 cel · 6/16/2018, 3:54:44 PM

@kode54 sure

%c0pu62/yVxRBZGUzPINJN+0SqY21R0fmZnEdp20Lxh4=.sha256 cel closed this issue · 8/23/2019, 1:37:43 AM

Built with git-ssb-web