Arch Linux User Repository

The LICENSE file has changed again. Now it is 68040689c4342e0018adec3eb0fb1f2ae68aaeef918e7b4493518523381b7129.

@vasily: Fixed. They've apparently changed their licensing policy.

https://www.cockroachlabs.com/blog/oss-relicensing-cockroachdb/

@jktr Please update the checksum for the LICENSE file. It has changed as well in the new version and now the check fails.

I've been adding this package to archlinuxcn repository, thinks again!

Source

Package URL

@axionl: Thanks for your feedback!

• Regarding deps on base: There seems to be no official consesus on the matter [0][1], but I'm leaning toward including it here in order to be explicit about glibc being a specific dependency of the binary from upstream.

• Regarding "executable stack": It seems I'd need to control source/compilation [2] to fix this (assuming cockroachdb internals don't actually require this), which is inapplicable for a *-bin package.

• Regarding moving to /opt: file-hierarchy(7) seems to indicate keeping the binary in /usr/bin is preferable.

• Regarding hardcoding uid/gid: tmpfiles.d(5) seems to be the proper solution, according to some cross-referencing with comparable packages in community. I've updated this package accordingly.

• [0] https://lists.archlinux.org/pipermail/aur-general/2018-February/033977.html

• [1] https://lists.archlinux.org/pipermail/aur-general/2018-February/033979.html
• [2] https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart

Thanks for you package, but here's some problems here:

===> Waring: ELF file ('usr/bin/cockroach') has executable stack.

• For this problem, I think create a sof-tlink for ELF file may be better, and put them to /opt path may be a better way.

===> cockroachdb-bin W: Dependency glibc included but already satisfied

• glibc is a part of base group, so you can remove it from PKGBUILD.

But the more serious problem is that:

==> cockroachdb-bin E: File (etc/cockroach) is owned by root:361

==> cockroachdb-bin E: File (var/lib/cockroach) is owned by 361:361

• Forcing the designation of owners and groups is not a good idea under the system root. If you can find a better way to fix this problem, please update the PKGBUILD.