Package Details: openresty 1.25.3.1-1

Git Clone URL: https://aur.archlinux.org/openresty.git (read-only, click to copy)
Package Base: openresty
Description: A Fast and Scalable Web Platform by Extending NGINX with Lua
Upstream URL: http://openresty.org/
Licenses: BSD
Submitter: tocer
Maintainer: kimbrandt
Last Packager: kimbrandt
Votes: 36
Popularity: 0.26
First Submitted: 2012-03-12 03:09 (UTC)
Last Updated: 2024-01-16 07:13 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

catwell commented on 2017-05-23 17:17 (UTC)

The code that adds the binary paths to $PATH is clearly broken: - You test if the code is in /etc/bash.bashrc but you append the line to ~/.bashrc. This results in a loop: the line is added every time the package is installed. - You do this in package() which is not here for this anyway. The clean way to do this is to add a file (per shell type, but just the .sh is probably enough here) to /etc/profile.d. For instance, check out how the Perl package does it: https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/perl#n211

dseg commented on 2017-05-19 05:46 (UTC)

>Fails to build - openssl 1.1.0 incompatibility? Yes, it's a upstream problem. I guess maybe you already know that OpenResty doesn't build with OpenSSL 1.1.0 (Work in progress) https://github.com/openresty/lua-nginx-module/pull/761

ryanswrt commented on 2017-05-17 15:34 (UTC) (edited on 2017-05-18 11:49 (UTC) by ryanswrt)

Fails to build - openssl 1.1.0 incompatibility? src/event/ngx_event_openssl.c: In function ‘ngx_ssl_connection_error’: src/event/ngx_event_openssl.c:2048:21: error: ‘SSL_R_NO_CIPHERS_PASSED’ undeclared (first use in this function) || n == SSL_R_NO_CIPHERS_PASSED /* 182 */ ^~~~~~~~~~~~~~~~~~~~~~~ src/event/ngx_event_openssl.c:2048:21: note: each undeclared identifier is reported only once for each function it appears in make[2]: *** [objs/Makefile:1206: objs/src/event/ngx_event_openssl.o] Error 1 make[2]: *** Waiting for unfinished jobs.... I made a custom PKGBUILD that pulls openssl1.0.2j to successfully build the project, as it looks like OpenResty won't upgrade. https://gist.github.com/TheAncientGoat/f29c47d0da2698c3338ab493499afba8

jseb commented on 2016-11-26 17:43 (UTC)

For some reasons, makepkg erases the pod files before building the package. pod files are used for documentation. For avoiding this, put in the PKGBUILD: options=(!purge)

bianjp commented on 2016-09-23 05:07 (UTC)

@daurnimator You have to import the pgp key manually: gpg --keyserver hkp://pgp.mit.edu --recv-keys A0E98066 What "validpgpkeys" does is just trusting keys with the specific fingerprints, not importing the key. @desg It's better to pin a comment in the top so users can find what to do easily.

daurnimator commented on 2016-09-22 12:40 (UTC) (edited on 2016-09-22 12:42 (UTC) by daurnimator)

@dseg, you added the wrong pgp key. I'm getting: ==> Verifying source file signatures with gpg... openresty-1.11.2.1.tar.gz ... FAILED (unknown public key B550E09EA0E98066) According to https://openresty.org/en/download.html the correct key is https://pgp.mit.edu/pks/lookup?op=get&search=0xB550E09EA0E98066

dseg commented on 2016-09-05 16:48 (UTC)

@daurnimator Thank you very much for the info, I didn't know that. Updated.

daurnimator commented on 2016-09-05 03:15 (UTC)

Please use 'validpgpkeys' so that users don't need to trust openresty's pgp key in their own gpg database. See http://allanmcrae.com/2015/01/two-pgp-keyrings-for-package-management-in-arch-linux/

lhjay1 commented on 2016-09-02 07:42 (UTC)

Why not clone https://github.com/openresty/openresty

dseg commented on 2016-06-15 11:31 (UTC) (edited on 2016-06-15 16:29 (UTC) by dseg)

I added the PGP signature of the release to the source list. Please import the pgp key of the author of the Openresty before doing the build. https://openresty.org/en/download.html $ gpg2 --recv A0E98066 $ gpg2 --edit-key A0E98066 gpg> trust gpg> 5 FYI) Found a discussion thread about PGP signature in here: https://bbs.archlinux.org/viewtopic.php?id=191629