keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
899 stars 37 forks source link

Ubuntu/Debian packaging #191

Open ezyang opened 10 years ago

ezyang commented 10 years ago

Hey folks,

I don't like it when my software doesn't use my system's package manager:

ezyang@sabre:~$ npm install -g keybase-installer 
npm http GET https://registry.npmjs.org/keybase-installer
npm http 200 https://registry.npmjs.org/keybase-installer
npm http GET https://registry.npmjs.org/keybase-installer/-/keybase-installer-0.1.8.tgz
npm http 200 https://registry.npmjs.org/keybase-installer/-/keybase-installer-0.1.8.tgz
npm ERR! Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR!  { [Error: EACCES, mkdir '/usr/local/lib/node_modules']
npm ERR!   errno: 3,
npm ERR!   code: 'EACCES',
npm ERR!   path: '/usr/local/lib/node_modules',
npm ERR!   fstream_type: 'Directory',
npm ERR!   fstream_path: '/usr/local/lib/node_modules/keybase-installer',
npm ERR!   fstream_class: 'DirWriter',
npm ERR!   fstream_stack: 
npm ERR!    [ '/usr/lib/nodejs/fstream/lib/writer.js:171:23',
npm ERR!      '/usr/lib/nodejs/mkdirp/index.js:51:17',
npm ERR!      'Object.oncomplete (fs.js:107:15)' ] }
npm ERR! 
npm ERR! Please try running this command again as root/Administrator.

npm ERR! System Linux 3.11.0-17-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "keybase-installer"
npm ERR! cwd /home/ezyang
npm ERR! node -v v0.10.15
npm ERR! npm -v 1.2.18
npm ERR! path /usr/local/lib/node_modules
npm ERR! fstream_path /usr/local/lib/node_modules/keybase-installer
npm ERR! fstream_type Directory
npm ERR! fstream_class DirWriter
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, mkdir '/usr/local/lib/node_modules'
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:171:23
npm ERR! fstream_stack /usr/lib/nodejs/mkdirp/index.js:51:17
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ezyang/npm-debug.log
npm ERR! not ok code 0

Would you guys be interested in a contributed Debian/Ubuntu package for the keybase command line client?

makyo commented 10 years ago

:+1:, though we're too late for 14.04.

tildelowengrimm commented 10 years ago

I think that a good step before trying to be accepted into either Ubuntu or Debian mainline would be to have a dedicated apt repo or PPA for the package, and watch carefully to see what starts breaking, if anything.

patcon commented 10 years ago

Would love to see a response from core devs about starting a ppa on launchpad. I'm interested in using this approach to get keybase cli working on Tails OS.

Anyone know anyone with debian maintainer status who might be able to help us through the process?

frank-borkin commented 9 years ago

Hi all, I've created a PPA: sudo add-apt-repository ppa:borkinfr/keybase sudo apt-get update sudo apt-get install keybase

It's a bit fugly right now, but it works (at least on trusty). I'll get some improvements in over the next few weeks and cover the other versions (utopic, etc).

Frank

maxtaco commented 9 years ago

This is awesome, thanks for doing this.

zQueal commented 9 years ago

Confirmed working on trusty! Doesn't actually look too terribly bad. Thanks for the time, frank!

frank-borkin commented 9 years ago

Ok, Precise, Trusty, Utopic, Vivid are there; there are problems with Lucid (though it's so old it might not be worth supporting - it's EOL in April). Trusty and Utopic seem to work fine, I need to test Precise and Vivid.

@maxtaco - Do you do release anouncements and have a versioned changelog?

maxtaco commented 9 years ago

We haven't been doing release announcements since we're in bugfix mode, but we have a versioned changelog in node-client as CHANGELOG.md.

BTW, we're working on replacing the node-based client with one in Go. It will have a lot of new features and fewer dependencies. It's a work in progress, but we're getting there. That repo is now closed because we don't want people running the software, as it will make changes to sigchains that will break current clients. But if you want read access, I'm happy to add you, let me know....

frank-borkin commented 9 years ago

Hi @maxtaco ,

I'd like access to the Go repo so I know what's coming up, and I think it woulg be useful for myself and @danielquinn to get release announcements so we know when 0.7.7 turns into 0.7.8 or 0.8.0. I think it looks better if the packages are released about the same time as the node updater sees a new version.

Is the Go client slated for 0.8.0?

ghost commented 9 years ago

If you need only a notification that a new version has been released then you can use githubs atom feed for releases: https://github.com/keybase/node-client/tags.atom Since I want those release notifications on my smartphone I wrote a little IFTTT recipe which sends these as a notification to it.

maxtaco commented 9 years ago

Hi @frank-borkin and @dtiersch, I invited you guys into the Go client repo if you're curious.

I think the Go client is slated for 1.0.0 at current.

frank-borkin commented 9 years ago

Hi Max,

Thanks. Poking around, it's interesting but it looks like it'll be a while before it's done.

David,

I was hoping for more of a heads-up than a notification after the fact :)

Frank

On 11 March 2015 at 01:20, Maxwell Krohn notifications@github.com wrote:

Hi @frank-borkin https://github.com/frank-borkin and @dtiersch https://github.com/dtiersch, I invited you guys into the Go client repo if you're curious.

I think the Go client is slated for 1.0.0 at current.

— Reply to this email directly or view it on GitHub https://github.com/keybase/keybase-issues/issues/191#issuecomment-78169918 .

ptman commented 8 years ago

There is now https://github.com/keybase/client/tree/master/packaging