Created attachment 439246 [details] kbfs ebuild I created some ebuilds for testing the new Keybase Filesystem functionality that is available for keybase.io. I also had to create a newer version of the keybase client as the current release does not include the necessary RPC calls.
Created attachment 439248 [details] keybase client
Note that these ebuilds use the latest commits in master branch at the time of writing so they might be unstable, no official release tags have been created yet. They are also available in my overlay: https://github.com/MathyV/gentoo-overlay-mathy
These should both be using the git-r3 eclass, please re-submit. I would also recommend re-naming the ebuild to -9999 if its a 'live' (ie. trunk git checkout) or a -pYYYYMMDD for a (dated) snapshot. See the devmanual for naming conventions, if required.
Are you interested in ultimately proxy-maintaining this? (https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers) If so, I'll cc the Proxy Maintainers project and someone can stop by to help review your submissions.
Sure, I don't mind improving the ebuild quality if they indeed end up in portage
(In reply to Mathy Vanvoorden from comment #5) > Sure, I don't mind improving the ebuild quality if they indeed end up in > portage
Any updates to this? Been almost a month. I'd like to see keybase 1.0.17 in the tree.
I installed both ebuilds. I had keybase 1.0.16 running. the keybase seems to work for me, but not the kbfs. gem@kong ~ $ kbfsfuse keybase ▶ INFO KBFS version 1.0.2 ▶ WARNING MDServerRemote is disconnected: 2 [hangs...] ^C gem@kong ~ $ gem@kong ~ $ keybase status Username: gemiller Logged in: yes Device: name: kong ID: 53d4fbfd8f47e6071d8991ab1ff39d18 status: active Session: gemiller [salt only] is valid: yes keys: unlocked Key status: stream: cached secret: not stored dev sig: not cached dev enc: not cached paper sig: not cached paper enc: not cached prompt: show tsec: not cached KBFS: status: not running version: 1.0.2 log: /home/gem/.cache/keybase/keybase.kbfs.log Service: status: running version: 1.0.16 log: /home/gem/.cache/keybase/keybase.service.log Updater: log: /home/gem/.cache/keybase/keybase.updater.log Platform Information: OS: linux Runtime: go1.6.3 Arch: amd64 Client: version: 1.0.16 Desktop app: status: not running version: log: /home/gem/.cache/keybase/Keybase.app.log Config path: /home/gem/.config/keybase/config.json Default user: gemiller Other users: command-line client: keybase status [pid: 2450, version: 1.0.16] gem@kong ~ $ eix kkeybase [?] app-crypt/keybase Available versions: (~)0.8.13 0.8.18 (~)0.8.22 (~)0.8.23 (~)0.8.24 0.8.25 (~)1.0.8.0 (~)1.0.9.0 (~)1.0.12.0 (~)1.0.15 (~)1.0.16 Installed versions: 1.0.17_pre20160630[?](05:34:04 PM 08/13/2016) Homepage: https://keybase.io/ Description: Client for keybase.io
I installed both ebuilds. I had keybase 1.0.16 running. the keybase seems to work for me, but not the kbfs. gem@kong ~ $ kbfsfuse keybase ▶ INFO KBFS version 1.0.2 ▶ WARNING MDServerRemote is disconnected: 2 [hangs...] ^C gem@kong ~ $ gem@kong ~ $ keybase status Username: gemiller Logged in: yes Device: name: kong ID: 53d4fbfd8f47e6071d8991ab1ff39d18 status: active Session: gemiller [salt only] is valid: yes keys: unlocked Key status: stream: cached secret: not stored dev sig: not cached dev enc: not cached paper sig: not cached paper enc: not cached prompt: show tsec: not cached KBFS: status: not running version: 1.0.2 log: /home/gem/.cache/keybase/keybase.kbfs.log Service: status: running version: 1.0.16 log: /home/gem/.cache/keybase/keybase.service.log Updater: log: /home/gem/.cache/keybase/keybase.updater.log Platform Information: OS: linux Runtime: go1.6.3 Arch: amd64 Client: version: 1.0.16 Desktop app: status: not running version: log: /home/gem/.cache/keybase/Keybase.app.log Config path: /home/gem/.config/keybase/config.json Default user: gemiller Other users: command-line client: keybase status [pid: 2450, version: 1.0.16] gem@kong ~ $ eix keybase [?] app-crypt/keybase Available versions: (~)0.8.13 0.8.18 (~)0.8.22 (~)0.8.23 (~)0.8.24 0.8.25 (~)1.0.8.0 (~)1.0.9.0 (~)1.0.12.0 (~)1.0.15 (~)1.0.16 Installed versions: 1.0.17_pre20160630[?](05:34:04 PM 08/13/2016) Homepage: https://keybase.io/ Description: Client for keybase.io
sys-fs/kbfs-1.0.2_pre20160630 is working great for me with app-crypt/keybase-1.0.17 The kbfsfuse command appears to do nothing when you run it -- but it's working. I've verified this between four computers so far, 2 Gentoo, 1 Fedora and 1 Windows.
If anyone wants an invite to test, send me your email address.
(In reply to Alecks Gates from comment #10) > sys-fs/kbfs-1.0.2_pre20160630 is working great for me with > app-crypt/keybase-1.0.17 > > The kbfsfuse command appears to do nothing when you run it -- but it's > working. I've verified this between four computers so far, 2 Gentoo, 1 > Fedora and 1 Windows. Where is the kbfs ebuild? Not is the main paortage tree: dagwood ~ # eix kbfs No matches found
(In reply to Gary E. Miller from comment #12) > (In reply to Alecks Gates from comment #10) > > sys-fs/kbfs-1.0.2_pre20160630 is working great for me with > > app-crypt/keybase-1.0.17 > > > > The kbfsfuse command appears to do nothing when you run it -- but it's > > working. I've verified this between four computers so far, 2 Gentoo, 1 > > Fedora and 1 Windows. > > Where is the kbfs ebuild? Not is the main paortage tree: > > dagwood ~ # eix kbfs > No matches found It's in Mathy's overlay, at https://github.com/MathyV/gentoo-overlay-mathy
I didn't see this bug until now, but I have added app-crypt/keybase-1.0.17 and app-crypt/kbfs-9999 in tree.
Both are present in the tree as of now and have a maintainer. Closing as fixed.
