Package Details: openresty 1.27.1.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.001233
First Submitted: 2012-03-12 03:09 (UTC)
Last Updated: 2025-01-08 11:40 (UTC)

Latest Comments

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

charlesdyfis commented on 2018-07-23 17:32 (UTC)

The version of openresty packaged here now works with OpenSSL 1.1, so the dependency on 1.0 (and compile-time options to use it) can be safely removed.

jijunliu commented on 2018-01-17 08:36 (UTC)

==> Verifying source file signatures with gpg... openresty-1.13.6.1.tar.gz ... FAILED (unknown public key B550E09EA0E98066) ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build openresty.

resolve it:

gpg --recv-key 25451EB088460026195BD62CB550E09EA0E98066

dseg commented on 2017-08-23 03:49 (UTC)

@chrko Fixed. thank you.

chrko commented on 2017-08-22 13:46 (UTC) (edited on 2017-08-22 14:17 (UTC) by chrko)

@dseg You misspelled validpgpkeys in the PKGBUILD. It is pgp and not gpg, as @daurnimator has correctly written. Please don't define your own openssl version. Depend on the package openssl-1.0 and make use of the following options for the configure statement: --with-cc-opt="-I/usr/include/openssl-1.0/" \ --with-ld-opt="-L/usr/lib/openssl-1.0/" Also "with-imap" is replaced by "with-mail". :)

dseg commented on 2017-07-23 08:02 (UTC)

@daurnimator Thanks! Updated.

daurnimator commented on 2017-06-28 06:55 (UTC) (edited on 2017-06-28 06:56 (UTC) by daurnimator)

@dseg, you're meant to put the fingerprint in the validpgpkeys. i.e. validpgpkeys=('25451EB088460026195BD62CB550E09EA0E98066') Users shouldn't have to trust manually. And also, *never* recommend a user trusts a gpg key at level 5.

eimis commented on 2017-06-24 18:34 (UTC)

After several hours of !@#$%^& and Distcc I manged to build this for raspberry pi 1 running Arch Linux ARM. Only change to this PKGBUILD - adding of https://github.com/arut/nginx-rtmp-module module. http://www.mediafire.com/file/t0lkp5v86020od6/openresty-1.11.2.3-4-armv6h.pkg.tar.xz

dseg commented on 2017-05-29 13:16 (UTC)

For short: $ gpg2 --edit-key A0E98066 gpg> trust gpg> 5

dseg commented on 2017-05-29 13:15 (UTC)

@aajjbb You need to trust the key by yourself before doing the build. $ gpg2 --edit-key A0E98066 gpg (GnuPG) 2.1.21; Copyright (C) 2017 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. pub rsa2048/B550E09EA0E98066 created: 2013-02-18 expires: never usage: SC trust: unknown validity: unknown sub rsa2048/9C86AC14130DD88B created: 2013-02-18 expires: never usage: E [ unknown] (1). Yichun Zhang (agentzh) <agentzh@gmail.com> gpg> trust pub rsa2048/B550E09EA0E98066 created: 2013-02-18 expires: never usage: SC trust: unknown validity: unknown sub rsa2048/9C86AC14130DD88B created: 2013-02-18 expires: never usage: E [ unknown] (1). Yichun Zhang (agentzh) <agentzh@gmail.com> Please decide how far you trust this user to correctly verify other users' keys (by looking at passports, checking fingerprints from different sources, etc.) 1 = I don't know or won't say 2 = I do NOT trust 3 = I trust marginally 4 = I trust fully 5 = I trust ultimately m = back to the main menu Your decision? 5 Do you really want to set this key to ultimate trust? (y/N) y pub rsa2048/B550E09EA0E98066 created: 2013-02-18 expires: never usage: SC trust: ultimate validity: unknown sub rsa2048/9C86AC14130DD88B created: 2013-02-18 expires: never usage: E [ unknown] (1). Yichun Zhang (agentzh) <agentzh@gmail.com> Please note that the shown key validity is not necessarily correct unless you restart the program.

aajjbb commented on 2017-05-29 02:55 (UTC)

Failing: openresty-1.11.2.3.tar.gz ... FAILED (the public key 25451EB088460026195BD62CB550E09EA0E98066 is not trusted) Any tips on how to verify this key (is this key correct) ?

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