The following worked for me (from the issue @JoshStrobl found):

Yes, my mistake. Sorry about that.

Fix indenting of description.

Add MAINTAINERS and remove commented check

Add MAINTAINERS file

Add MAINTAINERS and fix package description

Add MAINTAINERS file and remove builddeps

Fix various packaging issues

I'm willing to maintain this. I have to keep an eye on my disk somehow :)

Fixed SPDX license number.

Update licenses to be valid SPDX identifiers

Fix networking, license and builddeps ordering

Update setup/build/install commands

Fix SPDX license identifier

Nice work! One thing though: 1.1.3 has been released last thursday.

Some binaries could really use CAP_NET_RAW, not sure how to set that it in package.yml though (as this is stripped in the package).

@JoshStrobl Out of habit, I'll skip right to the diff next time 🙂

Use install instead of cp

Two things:

• I believe update_sources.sh is missing a closing quote for LINKS (this isn't introduced by this revision).
• Attached you find a rebased version of the the disabled patch.

FYI: v1.0.1 has just been released

Rebase

In D3846#65787, @sunnyflunk wrote:

In D3846#65786, @silke wrote:

Edit: /usr/bin/ssh doesn't require libresolv.so.2 as a shared library when built against ldns, which is why it isn't included automatically. readelf -d output:

Then libresolv.so.2 shouldn't be in abi_used_libs. It's not a file to manually edit, it's to identify differences from the build.

Undo: Add libresolv back to abi_used_libs

@DataDrake, @JoshStrobl: it seems to me that libresolv is removed because ldns is used for resolving instead.

@JoshStrobl I got the same result when building against the updated images. I have added it back manually.

Add libresolv back to abi_used_libs

Update to 2.6.2

@JoshStrobl Unfortunately not: the single note on the release doesn't match the large amount of actual changes. And the changelog they have is woefully out of date.

Increment release by one instead of two

Update after acceptance

I know this is a duplicate of D599, but it seems to have stalled. There's still a lot of interest for Keybase, and I think this should do the trick.

Update to 4.8

Update Riot to 0.15.4

@Siilwyn: no, Electron does not necessarily come bundled with Node.JS (it is a framework after all). Electron does depend on Node.JS, and is a dependency of Riot because Electron is bundled with the application.

KBFS v1.0.47 now mounts KBFS in /run/user/$UID/keybase/kbfs. It also includes keybase-redirector, which ensures that /keybase/{private,public,team} point to the /run/user folder. The permissions for /keybase can be set to 0755, but keybase-redirector requires SUID.

Update Riot to 0.14.2

Now pam-krb5 has been accepted for inclusion: can I update this or should I submit a new revision?

By the way: the link to the source returns a 404 for me.

Rebase on latest master

Rebase on master